![]() |
|
|||||||
| 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 |
|
#1
|
||||
|
||||
|
Client Locks up when FFW or REW
Installed a new PC for my wife and it's running Sage Client 2.
Sage will playback a show fine, but if you bring upthe OSD, then click on the time bar to move in the show, Sage will lock up. Lock up so bad that the Close Window button (X) can't even be pressed. The only way to shut it down is to use CTL-ALT-DEL. Any ideas? I'm currently running neilm STV, but it does it on the original, mlbdude and malore's so I don't think it's an STV. Also, it does it whether or not using VMR9 or Overlay. Does it whether 3D accel is on or off. I'm out of ideas. Please help, if possible. Thanks! |
|
#2
|
||||
|
||||
|
Are you using the nvdvd audio decoder? I seem to recall people saying that could cause ff/rew problems.
- Andy
__________________
SageTV Open Source v9 is available. - Read the SageTV FAQ. Older PDF User's Guides mostly still apply: SageTV V7.0 & SageTV Studio v7.1. - Hauppauge remote help: 1) Basics/Extending it 2) Replace it 3) Use it w/o needing focus - HD Extenders: A) FAQs B) URC MX-700 remote setup Note: This is a users' forum; see the Rules. For official tech support fill out a Support Request. |
|
#3
|
||||
|
||||
|
This is also happening to me all too often. I recently lost a boot drive and took this opportunity to isolate sage on a clean system in an effort to track down and eliminate the problem with no success so far.
|
|
#4
|
|||
|
|||
|
Similar problems here. It seems to happen more often with longer-length recordings. I have tried both 64k block sizes and defragmented standard block sizes, but still see problems. This is happening on a non-nVidia system, wired to the server via 100Mbps CAT5.
I can't for the life of me figure out what the problem is. Server load is not an issue, and the client should be plenty powerful, too (2GHz P4 with 512MB RAM, Win2k). The connection isn't the issue, either - I never see problems when using VLC or even WMP to view the mpegs. Unfortunately for the Sage team, it's the worst kind of problem - very non-reproducible. |
|
#5
|
||||
|
||||
|
Both you guys, what are your motherboard chipsets?
Mine is an intel 865PE. |
|
#6
|
|||
|
|||
|
i also have this problem.
the work around i'm using at the moment until a fix comes out is to pause the program before fast forwarding. |
|
#7
|
|||
|
|||
|
Quote:
I've emailed back and forth to Frey and Hauppauge support on this a bit. The crux of the problem seems to be a Hauppauge PVR-350 tv-out issue with later Intel motherboard chipsets. Sheesh ... the reason I bought an Intel motherboard was exactly to avoid compatibility issues like this. I mean, how could you *possibly* go wrong with Intel, right? I'd have thought that Hauppauge would have done some robust testing with *all* motherboard manufacturers. I cannot believe they released their card with this enormous deficit. I am really regretting the decision to get the PVR-350. -Sheldon |
|
#8
|
|||
|
|||
|
Glad to hear you've got a workaround. But I don't think that the PVR-350 + Intel mobo is the whole story.
I am running my client on a computer without any PVR cards in it. I run the client on a Shuttle SilentX (ATI 9100IGP) computer. The server is running in a system with an ECS K7S5A motherboard. |
|
#9
|
|||
|
|||
|
Sheldon,
I too am seeing some problems with the pvr 350's tv-out. The things I've read indicate that it's a problem when outputting the OSD w/ the tv-out. I'm sure Hauppauge did do a bunch of testing w/ the 350, however, their software does not support OSD over the tv-out, nor does it seem like they ever had any intent of doing so. Now I'm not saying that this excuses them. It's a bug of course that Sage users seem to have uncovered - and it needs to be fixed by Hauppauge. However, I'm not sure I'd jump all over them for not knowing about/fixing a bug in a feature that their software wasn't written to support. Furthermore, I'm not sure how the OSD over tv-out is implemented in Sage, but, it may be more of a "hacked" feature, so to speak - a way to use the 350 that Hauppauge doesn't explicitly allow. If the specs for the 350 do not specifically say that this type of thing is allowed, then it's really a "use at your own risk" type of thing. They can make no guarantees as to it's stability. Now, I'm not saying it's excusable, or not annoying, b/c it is, I'm in the same boat as you. I just understand it from a programmers point of you. I think that it would behoove them to fix it as Sage + 350 is such a great combination. It would have great benefits for both Frey and Hauppauge. Justin |
![]() |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|