|
SageTV United Kingdom SageTV and SageTV Recorder Users from the UK - This forum is for you to post about specific issues using SageTV software in the UK. |
|
Thread Tools | Search this Thread | Display Modes |
#41
|
|||
|
|||
Well jhh seems to have it working with the 150MCE cards, so do they have different drivers? Must you have MCE to use the 150MCE drivers?
I'm wondering if we all listed our setups and say if they work or not (and if not what happens when it goes wrong, errors seen etc) we may come to a config that works, or at least provide the Sage devs with enough info of various configs that it may either help them develop support for it or maybe even help point to where the problem lies. The following would most probably be helpful:
It would mostly be like a bug report but this thread may be helpful in the future for others, especially for people in the UK. Ill post my current setup which is crashing tonight (still in work ) |
#42
|
|||
|
|||
Hi,
Version of Card (150 or 150MCE): 150MCE (3x) Card driver version: 2.0.18.22316 (this is a driver for the 150 NOT the 150MCE) WinTV Version: not installed Sage Version: first 2.1 then 2.2 latest build (both work) Operating system: WinXP Home Error Codes seen: (-4,0x8007048f) Description of steps to recreate error: stop Sage and start it again - then try to record or watch livetv. You'll immediately get the error. You can avoid the error by rebooting after stopping Sage. I think when it exits it doesn't release the card as it should and then later on it cannot connect to it properly. - I don't have WinTV I used registry hack to program my channels so I get them in the order I want using XMLTV plugin - If you use non MCE version of windows then also use non MCE card drivers. Only with non MCE drivers you will be able to install Hauppauges MPEG decoder. - If you stop Sage to make a change in the properties file then reboot your machine (the error happened to me when I stopped/started Sage to edit my properties file to configure Nielm's plug-in so I thought that was the cause but it is not). -> In Europe you need to start Sage to get a properties file then you can stop it to edit te properties file for XML plug-in. At this point reboot instead of restarting Sage -> If you do a clean install and use the drivers listed in my previous posting it should work. Good luck, Jan |
#43
|
||||
|
||||
Totally non-functional 150MCE card with Sage:
Version of Card (150 or 150MCE): 150MCE Card driver version: 2.0.18.22316 (again, the driver for the 150 NOT the 150MCE) WinTV Version: 4.7.22355 Sage Version: 2.2.4 Operating system: WinXP Pro SP2 (AMD Athlon64/Nforce3 mobo) Errors seen: 0x8007048f on start of capture Completely clean XP Pro install, install drivers from SHS's CD WinTV captures. Sage always displays (-4,0x8007048f) error when it starts to record... No amount of rebooting, restarting helps Logfile also contains line: Code:
Thu 2/3 23:47:25.017 WIN32 FAILURE HR=0x80040207 FILE=.\Encoder.cpp LINE=533 Last edited by nielm; 02-03-2005 at 04:52 PM. |
#44
|
|||
|
|||
Nielm,
Does WinTV work for you? Jan |
#45
|
|||
|
|||
Version of Card (150 or 150MCE): 150
Card driver version: 2.0.18.22316 WinTV Version: 4.7.22355 Sage Version: 2.1 (Tried 2.2.4 as well) Operating system: WinXP Pro SP2 Errors seen: 0x8007048f Also I don't now whether it makes a difference but I am using S-video input not the tuner. Also with 2.2.4 I got a slightly different message than with 2.1 (It implied the same thing so i didn't actually notice until i went bac to 2.1) When i uninstalled the pvr 150 and reinstalled the usb2 with 2.2.4 I carried on getting the same error with the pvr usb. Going back to 2.1 fixed that as well. RD |
#46
|
||||
|
||||
JHH: yep (at least I get a recorded MPG -- I have not yet tuned WinTV... Still in the process of building this new server)
I also managed to get a capture using graphedit (attaching zipfile with .grf and .gif of capture graph -- last filter is Dshow: MPEG2DUMP)... However, If I disconnect/delete/recreate the capture filter and encoder filter, I cannot re-connect them and I get a .. guess what .. 0x8007048f .. error, which can only be recovered by restarting Graphedit (I believe that Sage regularly re-builds its capture graphs)... I am going to send this all to support once I get a coherent mail together |
#47
|
|||
|
|||
This is my setup which is not working:
Version of Card: 150 Card driver version: 2.0.18.22316 WinTV Version: 4.6.22278 (although ran the 22292 update exe) Sage Version: 2.1.10 Using the debug console enabled I had the followig errors and ouput When pressing TV so it goes to fullscreen mode (results in Sage lockup): Debug: Code:
FAILURE HR=0x80040207 FILE=Encoder.cpp LINE=541 First time -4,0x8007048f followed by -3,0x80040243 Subsequent time (whilst staying in channel setup) only the -3 error. Code:
WIN32 FAILURE HR=0x80040207 FILE=Encoder.cpp LINE=541 Encoding to file E:\Movies\PVR\HauppaugeWinTVPVRPCIIICaptureTVTunerChannel65-0.mpg startEncoding0 called for Hauppauge WinTV PVR PCI II Capture #1 DShowPlayer setVideoRendererFilter0({51B4ABF3-748F-4E3B-A276-C828330E926A}) called DShowPlayer setTimeshift=1 buffer=16777216 NATIVE Loading the source file VideFrame had an error loading the file. It must abort the file load. Tearing down playback graph NATIVE Deallocating the CPlayerData object NATIVE Finished destroying the playback graph |
#48
|
|||
|
|||
Nielm,
that is getting way above my head. Only thing I noticed that helped was don't use the 150 at all not even with WinTV to check if it is working before Sage is started. Boot PC start Sage and it works for me. Sorry you're not as lucky as I am. I do get exactly the same line in my log as you do with LINE = 533 when it does fail so that seems to be the same type of thing. Mobby, The 22292 update exe is for the drivers not for the Wintv application. Maybe you could list DirectX version as wel - I have 9.0c Guess we need to leave it to support I don't think Sage will be happy if larger extracts from log files are posted than we did up to now. Jan |
#49
|
|||
|
|||
Ok tried a few things, and if i am reiterating someone has already said then sorry Tried different drivers, ones from cd that came with card, ones I had downloaded, always the same error. I have not even installed WinTV to eliminate that as a possible cause. I have on the other hand been able to make it work sorta if i set sage as NTSC then it works but of course the picture doesn't look quite right because of the PAL signal from the cable box. But when sage is set to PAL then all the above errors occur. So it sounds like Sage's PAL support with this card (or hauppauges fault although WinTV does view the signal and display it fine) doesn't work.
I have DirectX 9.0c Hopefully the posts we have all made will give Sage devs some extra info but yeah I aggree that maybe posting any more logs may be against what they want (so ignore what I said earlier ) So if anyone does happen to have sage set to PAL and have it working, what driver version and the update version (e.g. pvr150_22_22292.exe) ar eyou using? thanks to everyones posts btw |
#50
|
||||
|
||||
After a bit of playing, Sage can now record from my -150MCE but only for the first time I run Sage after boot.
This seems to be what everyone else sees happening, and with the SageTV Service, this should not be too much of an issue as I can re-start the UI without restarting the service (and I can set up the service to reboot if it crashes). What I did: I first upated my nforce3 drivers... and re-re-reinstalled the Hauppauge driver (currently using v2.0.18.22316 with 2.2.22292 DLL update from the beta CD on SHS's site). I followed his instructions exactly (mutiple HWCLEAR and multiple reboots) I also did *not* install WinTV or any of the other apps -- just the HP drivers. It now works in sage If I stop + restart sage, it stops working (attempts to record produce a 0x8007048f, or just no message in service mode). If I use any other program to capture from the -150 before I start sage it does not work This seems to be the behaviour that a lot of other people are having, and is a driver issue that that Hauppauge are working on (apparently)... But at least I can use my -150 now... |
#51
|
||||
|
||||
Any reason you are not using the version 2.0.24.23025 available at http://www.shspvr.com/forum/viewtopic.php?t=7103
Maybe I'm missing something... |
#52
|
||||
|
||||
the comments about it not working in the forum put me off, and the version in SHS's CD s the same as the one available from Hauppauge benelux...
|
#53
|
|||
|
|||
Quote:
Although I don't like its behaviour I found it behaves consistently: after a reboot it works again. Jan |
#54
|
||||
|
||||
with the possibility of a driver update affecting your current problems, and your willingness to experiment, why would you not try the new driver out and see for yourself if it's better or worse. Plus I'm really curious myself. It's not like you can't go back to the previous driver really easily...
ftp://ftp.shspvr.com/download/wintv-...0.24.23025.zip |
#55
|
|||
|
|||
pvr 150 working
BUT unfortunatly with Beyond TV not SAGE.
Ive read all these posts and tried everything. each time i get the sage.playback exception error -4xxxxx etc etc. In desperation i tried beyond TV just to see if my actual card worked... and first time its fine. so thats BeyondTV and WinTV 2000 that work fine. I really think its poor that this thread started months ago about probs with the 150 card and they still bundle it with their software without a solution. Im using the Composite input and I can play back DVDs and recorded MPEGS within sage so its not a playback problem. I want to use Sage cos of the predictive recording, but I dont think Im alone in my frustration over it not working. if anyone agrees with me lets all make a big fuss here and hope this prob gets to the top of priorities pile!! Laurence. |
#56
|
|||
|
|||
Well for me its the last bit of the puzzle I can do all the other things I want to do like play divx's, mp3's, dvd's, etc. But the only thing left for me is the TV. I haven't yet tried the steps outlined by nielm...
Quote:
Is there any word on how the Sage devs are doing with looking at this problem? Its fair enough if they dont say and it is what I would expect as they would most probably not want to say anything until its fixed but I thought I'd ask just in case I dont think kicking up a fuss in this thread would potentially help as from other's posts it sounds like the problem is being looked into. Often problems take a while to fix and especially when work may need to take place with 3rd Party companies - in this case Hauppauge. They are also most probably working on a number of bugs/updates and most probably this fix along with the other bugfixes/updates would be released in a 2.1.x release, instead of just releasing some new dll's or replacement jar file as a semi-update to just fix this one issue. Maybe it could be raised with Frey that more people are now experiencing this problem as now more people are most probably buying the PVR-150 (over the older 250) but I am guessing that would be best done by an Admin. Other than that I think I will just sit back and wait for a bit mobby |
#57
|
||||
|
||||
Mobby:
I have only re-installed driver updates (in fact several times) -- following the SHS instructions, so the update method must work, otherwise I wouldn't be getting anything I don't know whether my initial problems were caused by the older Nforce3 drivers, or by simply having installed WinTV, but I know that my current setup with PVR driver-only installation works after reboot... once... consistantly... Mobby/hookla, If you have not already done so, log a bug report. This is the only way Sage knows the severity of the problem, and you may gain access to any pre-release fixes before they become public. Hookla, one of the issues with this problem is that if any other software tries to use the PVR-150 before Sage does, Sage itself cannot use it, and it needs a reboot to fix, therefore using BTV or WinTV will actually cause Sage not to work... |
#58
|
||||
|
||||
Quote:
As described on SHS's forums, its really blurry (almost as if the fields were out of order) and messy. Regard to the behaviour with SageTV, works after boot, does not work if you restart Sage, so same behaviour as before. |
#59
|
|||
|
|||
PVR 150 PAL does not work with SAGETV
i have PVR 150 bought from PC world in London.
I have just rebuilt the computer and installed nothing but the hauppage drivers and sage TV and still get the -4 error! i think its safe to say that SAGE TV simply does not work with PAL PVR-150. we should all stop wasting our time trying! Laurence. |
#60
|
|||
|
|||
PVR 150 Working in UK
IT WORKS IT WORKS!!!
i used the Sage 2.2 beta but im dont think that is the significant bit close sage delete the sage.properties file and any auto backup start sage again when prompted say you are in US and use NTSC. in setup --> detailed setup, change the Mpeg2 filter decoder to SAGE TV one. live TV will work with composite input but will look really bad probably cos the signal comming in is PAL still. Im using composite input so i didnt think that PAL / NTSC thing would make a difference. so the prob is a NTSC vs PAL Thing. hopefully this can help push the debugging forward again.... ???? |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|