![]() |
|
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
|
|||
|
|||
Hi Utica,
Yes, I am having that same ( or similar )problem with the PVR-350 TV-out. I haven't enough data re. the intel chipset theory to say whether my problem stems from that or not . I will cool the hauppauge anyways, just to see if that helps at all. Worst case scenario is to output via the graphics card; the quality is not as good, but I can upgrade and tweak if necessary. Can you tell me where the info on the chipset incompatibility problem can be found. Also is this incompatibility generally regarded as a hauppauge or sagetv problem ? regards ad. |
#22
|
|||
|
|||
aidandunne,
Maybe cooling your pvr-350 will work for you, but I'm betting you have the same problem as I. While the beta version of 2.0 was out, a thread in the beta area was discussing this problem. Some had over heating problems, some of us assume that it was a chipset problem. see: http://forums.freytechnologies.com/f...&threadid=5024 I haven't seen anything offical from Frey acknowledging this problem. However a forum "power-user" (mlbdude) earlier in this thread mentioned that it is a problem with Hauppauge's windows drivers and Frey is working with them to try to resolve the problem. |
#23
|
|||
|
|||
Thanks Utica,
I suspect that what you say is true. If so then I guess I'll just take TV-out over my video card and tweak it as best I can. I sent in a support request just now to Frey. I'm sure they're aware of the problem but if it's a hauppauge problem then they'll have to wait with the rest of us for new drivers. I'll take all this info back with me when I retest my system tonight.. I'll let you know what I find. Thanks Aidan. |
#24
|
|||
|
|||
Here's another thread on this subject:
http://forums.freytechnologies.com/f...&threadid=5254 Would indicate people know about it and are working on the problem.... ad |
#25
|
|||
|
|||
During the time when I had issues with 350 lockups I was adding this cooling solution:
http://www.antec-inc.com/us/pro_deta...p?ProdID=77094 However it wasn't the solution at the time. Since then I added a speedcontrol to the fan. |
#26
|
|||
|
|||
What is the prefered Hauppauge driver for Sage 2.0?
|
#27
|
||||
|
||||
The latest one you can get XXX37
__________________
Mike Janer SageTV HD300 Extender X2 Sage Server: AMD X4 620,2048MB RAM,SageTV 7.x ,2X HDHR Primes, 2x HDHomerun(original). 80GB OS Drive, Video Drives: Local 2TB Drive GB RAID5 |
#28
|
|||
|
|||
Hi,
here's an update. I switched off the OSD on the 350 o/p and it works fine. Flawlessly, in fact. I had it recording one show while I was watching a show that was already recorded ( via my graphics card ) , while I was playing a dvd image from the harddrive via powerdvd and nothing bad happened. Earlier I quickly tested the OSD and, yes, the o/p n the 250 froze almost instantly; switching the OSD off fixed the problem. I still have a card cooler on order and I'll install it, but I don't think this is an overheating problem, I just don't think modding the o/p would cause an almost instantanious disabling of the 350; I mean, if it really had caused a spike in temp, surely the temp would not dissipate immediately( ie. I switched off the OSD and the problem went away without any delay )? My ( tentative) theory now is that running the hauppauge very hot is probably a separate ( albeit destabilizing ) scenario , compounding and obscuring any chipset/driver problems.. I've got a pile of shows set to record this weekend. I'll let the system go with that and tell people how it goes.. regards, Aidan |
#29
|
|||
|
|||
Thinking about the Hauppauge driver.
Do I get any benefit from upgrading to the latest driver? |
#30
|
||||
|
||||
I have been dealing with this 350 OSD problem for a while now. It only occurs when you enable OSD out on the 350. It only seems to affect newer Intel chipsets (845,850,865,875) and maybe some of the VIA and SIS chipsets. I switched over to an older MB with a 440bx chipset and all is well. I know of others who are having the same success with both the 440BX and 815 chipset. Some people have chosen to buy different MB just to avoid this problem. Some of the chipsets for Athlons are doing well and Mike Janer swears by his Asus MB with an ATI chipset.
I hope this helps.
__________________
Christopher Kron MCP, CNA ATI 9100 chipset P4 2.4GHz PVR-350 PVR-150 ATI Radeon 9100 512MB DDR RAM 2 x 80GB HDD MediaMVP |
#31
|
|||
|
|||
I upgraded to 2.0. Looks and works really great!
However I encountered a lockup. What is strange that it seems to lockup differently than when I had issues with 1.4 and Hauppauge drivers. Now I will get back to the TV-out test pattern. Is that consistent with others? |
#32
|
||||
|
||||
Quote:
__________________
Christopher Kron MCP, CNA ATI 9100 chipset P4 2.4GHz PVR-350 PVR-150 ATI Radeon 9100 512MB DDR RAM 2 x 80GB HDD MediaMVP |
![]() |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|