|
SageTV Software Discussion related to the SageTV application produced by SageTV. Questions, issues, problems, suggestions, etc. relating to the SageTV software application should be posted here. (Check the descriptions of the other forums; all hardware related questions go in the Hardware Support forum, etc. And, post in the customizations forum instead if any customizations are active.) |
|
Thread Tools | Search this Thread | Display Modes |
#21
|
||||
|
||||
Any updates with the SAP issue? Is anyone out there running the new 21199 drivers and not having the SAP issue?
|
#22
|
||||
|
||||
hey,
I'm still sticking with the 1.3.8 sageTV & the 1.16A PVR 250 CD drivers. No SAP. No channel change crackle/pop. -Cab |
#23
|
|||
|
|||
I emailed Jeffey (who does tech support) and he told me that he would work on it if we all figured out what hardware and software and drivers we all have in common.
My setup: Intel P4 2.4 533m fsb; Intel D845PEBT2 mobo, using onboard Integrated AC’97 Audio w/SoundMAX software; 512m RAM, ATi 9500 Pro, Windows XP Home; Norton Systemworks w/ GoBack; Hauppauge WinPVR 250 with latest drivers, not using remote; SageTV v1.4, Actisys IR200-L set up per SageTV instructions. In the meantime, I think I'll have to try using an earlier driver for the Hauppauge card, but I can't figure out how to do it. If have checked out shspvr.com but the instructions on removing the old drivers are not clear at all, and involve going into the registry. Would anyone be kind enough to give me a step-by-step? Pete Last edited by Phoner; 09-14-2003 at 09:20 AM. |
#24
|
||||
|
||||
If you follow the instructions on the Hauppauge site for the new drivers (just stop shor of installing the actual driver) you should be clear and ready to go.
I know the SAP issue is not a Sage issue, but I do have one question, does the Hauppauge supplied WInTV jump to SAP? If it does not, then there must be something that Sage can do. If it does, then it is hopeless and we just wait for the next driver release. |
#25
|
|||
|
|||
Thanks mlbdude. I installed the 1.6A driver for the Hauppauge 250 that came on the CD, and now SageTV v1.41 can't find the card in setup.
Is this normal? Anyone know how to fix this, or specifically which older Hauppauge drivers (version and build) work with SageTV 1.41 and don't have the SAP problem? I have repeatedly uninstalled and reinstalled both the Hauppauge drivers and SageTV, without success. Last edited by Phoner; 09-14-2003 at 12:42 PM. |
#26
|
||||
|
||||
So far the only drivers that work without SAP other than some beta are the 1.6 drivers.
Try this to get your sources back... http://www.freytechnologies.com/foru...age.properties I am running 1.17.21128 and don't get SAP, but they are beta. These seem to be the only drivers that I have without SAP that work when combining a IVAC15 and IVAC16 card as well. Good luck. |
#27
|
|||
|
|||
Thanks again mlbdude! That worked. SAP is off now. I'm not so sure the picture is as good, but oh well.
|
#28
|
||||
|
||||
I would say that the picture is not as good with 1.6. I hope something is resolved with this soon
|
#29
|
|||
|
|||
I think there is a fix now. Jeff sent me a new sage.dll file that seems to be working.
|
#30
|
||||
|
||||
I've been reading this thread, and it describes my problem exactly. I had been using Sage 1.3.x with the Hauppage CD drivers (1.6B I think) and everything was fine. Then I upgraded to Sage 1.4.x and shortly thereafter upgraded my hauppage drivers to 1.7 from their website, and immediately started encountering SAP problems on certain channels at certain times. I am going to revert my drivers back to the Hauppage CD-supplied drivers, but I would appreciate hearing about any official fix for this.
-Dan |
#31
|
||||
|
||||
I also have this problem in 1.4.10. I had used Hauppague drivers 1.17.21177 and 1.17.21199 since betas 1.4.3 and hadn't seen this issue until now. I didn't realize how bad it was because I hadn't been watching the local channels. often. I had only noticed it on CBS CSI. I would get the voice over describing every action that was going on. Last night on FOX, ABC I was getting the echo chamber effect with spanish coming through on ABC. If a new sage.dll cures that, the sooner it's available, the better. I don't want to roll back to any other previous version because the picture is worse. I also saw out on SHSPVR website there is a newer Hauppague beta available and another dll that improves that beta. Don't really want to go that route either. I have moved my HTPC into production so it's in the living room and being QA'd by the Wife.
Gerry
__________________
Big Gerr _______ Server - WHS 2011: Sage 7.1.9 - 1 x HD Prime and 2 x HDHomeRun - Intel Atom D525 1.6 GHz, Acer Easystore, RAM 4 GB, 4 x 2TB hotswap drives, 1 x 2TB USB ext Clients: 2 x PC Clients, 1 x HD300, 2 x HD-200, 1 x HD-100 DEV Client: Win 7 Ultimate 64 bit - AMD 64 x2 6000+, Gigabyte GA-MA790GP-DS4H MB, RAM 4GB, HD OS:500GB, DATA:1 x 500GB, Pace RGN STB. |
#32
|
|||
|
|||
Quote:
|
#33
|
|||
|
|||
I'm still using Sage 1.3.8. I'm using the latest release driver from Hauppauge (21199) and the SAP is still kicking in.
The SAP did not kick in with the previous driver (the one on the Hauppauge CD) but I can't go back to that version because I had the 'chirping' problem with that driver (the chirping problem is discussed in another thread). Has anyone found a driver that defeats this problem when running 1.3.8? Will Jeff's fix work for me, or is it only for version 1.4? |
#34
|
|||
|
|||
Here is what Jeff sent me, and it has been working. I don't know why he hasn't posted it himself, so use it at your own risk!
The procedure: First shut down SageTV. Before I applied the patch, I also made these changes to sage.properties; they may or may not have made a difference: mmc/feature_mask_disable=8 seeker/fast_mux_switch=false always_autotune=false Then apply the sage.dll patch. Unzip the sage.zip file and replace your old sage.dll file with this new one. Then: 1. Select something to record that's on now that'll have SAP. 2. Select that same thing to watch. 3. Put SageTV to sleep. 4. Wakeup SageTV and select it to watch again. EDIT: There is one other thing I did that might make a difference. When I upgraded to the Hauppauge WinTV drivers version 1.17, first I used their program to completely uninstall their drivers and related programs; then I just installed the driver and I DID NOT install WinTV2000 and the Hauppauge Video Decoder. This may or may not have made a difference; the first time I tried the patch it didn't work and this may have been why. Last edited by Phoner; 09-18-2003 at 02:29 PM. |
#35
|
|||
|
|||
Thanks Phoner,
Which version of Sage are you running? I'm running 1.3.8, so I just want to be sure the patch is compatible with that version. Also, I'm not sure I know what putting Sage 'to sleep' means - is that just minimizing it to the taskbar, or is there more to it than that? BB |
#36
|
||||
|
||||
There's a sleep button on the Home menu. When you click this you send Sage to the system tray. (Lower right hand corner of your screen). This is NOT the same as minimizing to your task bar.
Gerry
__________________
Big Gerr _______ Server - WHS 2011: Sage 7.1.9 - 1 x HD Prime and 2 x HDHomeRun - Intel Atom D525 1.6 GHz, Acer Easystore, RAM 4 GB, 4 x 2TB hotswap drives, 1 x 2TB USB ext Clients: 2 x PC Clients, 1 x HD300, 2 x HD-200, 1 x HD-100 DEV Client: Win 7 Ultimate 64 bit - AMD 64 x2 6000+, Gigabyte GA-MA790GP-DS4H MB, RAM 4GB, HD OS:500GB, DATA:1 x 500GB, Pace RGN STB. |
#37
|
|||
|
|||
Quote:
I forgot to mention in an earlier post that I when I successfully used the patch, I didn't install any of the related WinTV software along with the driver. I have changed that post as well. Last edited by Phoner; 09-18-2003 at 02:32 PM. |
#38
|
||||
|
||||
If the patch works for anybody else, please let me know.
__________________
Jeffrey Kardatzke Founder of SageTV |
#39
|
||||
|
||||
No luck here. Replaced the dll. Edited the properties as described above. Went through the rest of the procedure. On FOX I was getting the dual sound with the one being normal and the other being the verbal description of what was going on. Tried this with the following audio decoders: Sonic, NVDVD and the Hauppague Intervideo audio codecs. Audio renderers: Default, Default DirectSound Defaul WaveOut, nVidia nForce and DirectSound nVidia nForce. I was hoping this was the fix. SageTV 1.4.10 and Hauppague 1.17.21199 drivers.
Gerry
__________________
Big Gerr _______ Server - WHS 2011: Sage 7.1.9 - 1 x HD Prime and 2 x HDHomeRun - Intel Atom D525 1.6 GHz, Acer Easystore, RAM 4 GB, 4 x 2TB hotswap drives, 1 x 2TB USB ext Clients: 2 x PC Clients, 1 x HD300, 2 x HD-200, 1 x HD-100 DEV Client: Win 7 Ultimate 64 bit - AMD 64 x2 6000+, Gigabyte GA-MA790GP-DS4H MB, RAM 4GB, HD OS:500GB, DATA:1 x 500GB, Pace RGN STB. |
#40
|
|||
|
|||
gplasky, the patch didn't work for me the first time I tried it. That's why I tried to be so explicit about the instructions, in hopes that it could be replicated. Did you first fully uninstall your Hauppauge drivers using the Hauppauge uninstall utility? Then did you only install the Hauppauge drivers without any other software? Another thing is that I not only fully uninstalled the Hauppauge drivers but I also uninstalled SageTV and started from scratch the second (and successful) time. After installation, I ran the test for SAP (flunked), then I made the sage.properties changes and ran the test (flunked), then I replaced the .dll file and ran the test again (may have flunked but then worked fine). Good luck!
|
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|