Calling all Hauppauge 350 users for satisfaction poll?

[pcuoco]

Carlgar,

If it seems to be working now, but CPU cycles are high, you should really try hardware decoding only. I'm running my Sage system on a PIII 650 with hardware decoding and my CPU doesn't go above 10% to 20% during normal Sage operations.

[carlgar]

I have a couple of reasons for not trying hardware decoding only. The first is because of the following statement for SageTV 1.4:
videoframe/disable_sw_decoding - true/fales to completely disable software decoding when using a hardware decoder for playback (may cause system to hand for PVR-350)

The second is the same reason I have not yet upgraded to SageTV 2.0. I do view shows on my monitor and in full screen mode. I am not yet willing to give up those features. Currently the main advantage for me to go with 2.0 is the UI on the TV, but once that is enabled I lose the resize (including full screen) ability in SageTV 2.0. Therefore, I am staying with 1.4 for the time being.

I don't think SageTV is the cause of the high usage, Sage seems to only be using about 30%. It seems to be some program "lsas" that causes the high usage. The high usage is not causing any problems it was just an observation by me. I do use this as a working computer and the only issue I encountered was the studdering which is now gone with SageTV running at the above normal priority. I believe when I was running with Hyper-threading SageTV only used about 10% of the CPU. At that time the only 100% usage I saw was when starting a new program such as quicken.

[Alex0230]

Is the general consensus that the 350 records fine....it's just that playing back sucks? My problems with playing back typically occur while recording another show on the 350.

I think I've stated this before somewhat..but fine tuned it: The two scenarios are typically if I'm watching the show that I'm recording and it finishes recording (sometimes goes to start another) while I'm watching...this will cause a lockup (soft and hard). Or if I'm watching a recording that is already complete and something I'm recording either starts or finishes, this will cause lockups both hard and soft. There is also the infamous FFWD/RWD lockup issue as well.

My workaround to fix a soft lockup is this. I first stop the file because it seems that it is still trying to play eventhough the 350 isn't outputting it. Then I go to setup, disable/enable the device, then start another recording. "Sometimes" this works, sometimes it results in a hard lockup, sometimes I get a graph draw error.

Anyone else experience the scenarios I seem to have....also has anyone actually submitted a bug report to Frey yet to see what they have to say? Just like with the Roslyn card....it may be something they can fix.

[laurenglenn]

Originally posted by Alex0230
Is the general consensus that the 350 records fine....it's just that playing back sucks? My problems with playing back typically occur while recording another show on the 350.

I think I've stated this before somewhat..but fine tuned it: The two scenarios are typically if I'm watching the show that I'm recording and it finishes recording (sometimes goes to start another) while I'm watching...this will cause a lockup (soft and hard). Or if I'm watching a recording that is already complete and something I'm recording either starts or finishes, this will cause lockups both hard and soft. There is also the infamous FFWD/RWD lockup issue as well.

My workaround to fix a soft lockup is this. I first stop the file because it seems that it is still trying to play eventhough the 350 isn't outputting it. Then I go to setup, disable/enable the device, then start another recording. "Sometimes" this works, sometimes it results in a hard lockup, sometimes I get a graph draw error.

Anyone else experience the scenarios I seem to have....also has anyone actually submitted a bug report to Frey yet to see what they have to say? Just like with the Roslyn card....it may be something they can fix.

Try my STV at this link:

http://forums.sage.tv/forums/showthr...0&pagenumber=1

I've been trying to work around the EOF bug, and think I may have found something. Let me know if it works for you.

It seems to be a problem with the STVs and possible SageTV, but the STV should allow for a work-around. Also, Custom1 will turn off and on the 350UI, and Custom2 should turn off/on the 350TV Out.

If the file stops playing, just open up a different file and it should go back to normal. You can use the Custom1 button to restart the 350UI if it doesn't do it automatically.

Lauren

[Alex0230]

I'm using that now....we'll see how it works. So far it's passed one test...but the issues are intermittent a few days should disclose some results.

I've also set "close_file_on_350_reset" to true. This may help with the soft lockups since Sage will attempt to immediately close the file. I had a soft lockup and sage detected it and closed the file...I was able to resume the recording immediately after it did this.

[spanky]

Carlgar,

Hopefully when M$ releases service pack 2 you'll be able to re-enable the hyper-threading. Anyone interested in trying the release candidate of SP2 can find it here:

http://www.microsoft.com/technet/pro.../sp2wuins.mspx

I think I'll wait a bit before installing it myself. My PIII 800 running on an Intel 815 doesn't run into this problem but I am looking at the D865GBFL as an upgrade soon.

[carlgar]

Spanky, Thanks for the info. While SageTV is now running like a champ, I think my system is starting to get bogged down. I may be forced to go hybrid, running hyper-thread during the day when no recordings and then non-hyper during prime time.

[carlgar]

Well so much for rock solid! After being up for almost exactly 2 days 9 hours my system crashed very bad. It rebooted itself and I did report the dump to MS. I suspect now I may be in same boat as zz5 with a 3 day up time limit.

BTW: The report from MS said it was a driver issue, my money is on the 350 driver being the problem driver.

[fidget]

Originally posted by carlgar
BTW: The report from MS said it was a driver issue, my money is on the 350 driver being the problem driver.

FWIW, the report from MS says that it is always a driver issue, but Hauppauge does need to improve the quality of their drivers.

[newschapmj1]

Great subject for a pole!

I'm one of those using TV out and having problems.

I'm in my 4th week of trialling with V2.0.19.

I'm focusing on Recording issues at the moment with my testing.

I have
"Enable UI on TV out" disabled
I have
"Enable TV out for PVR350" enabled

I schedule recording and leave the machine in sleep mode.

I have had examples where recording stops after a few minutes or does not start at all.

When I return to the machine Windows XP is fine but the application has closed.
There are no messages in the Application/System event logs.

I have been using remote desktop to control my PVR PC

Are there any steps I can take to generate debugging information?


=======================
I had earlier problems with XP locking and only coming up in safe mode.

An error message in the System log pointed me to a MS document which advised disabling hardware accelleration. This seems to have fixed the problem.

[carlgar]

newschapmj1 this seems like more than just 350 related issues. I think you should look at the SageTV V2.0.20 Maintenance Release thread. I think you are being hit by #5 on the list of problems solved.

[newschapmj1]

Thanks, I spotted this a few minutes after posting.

Which I'd checked a few days ago!

I let you know if this problem is not fixed by the new release.

[Catman]

I have been using the 350 card for about a month and I get soft and hard lockups via the S-Video out at least 2 or 3 times a day. I do have the nVidia chipset so that does not help.

It seems to get worse when I am pausing, F Fowarding or reversing. I shur would like to get this problem fixed. I might have to go out the VGA port.

By the way does anyone know how to installl a video decoder if I use the VGA port. Can I install WINDVD or PowerDVD software and have the decoder show up in the Sage Video Detail setup selection or is there something I need to do extra?

[Bathel]

Originally posted by Catman
I have been using the 350 card for about a month and I get soft and hard lockups via the S-Video out at least 2 or 3 times a day. I do have the nVidia chipset so that does not help.

It seems to get worse when I am pausing, F Fowarding or reversing. I shur would like to get this problem fixed. I might have to go out the VGA port.

By the way does anyone know how to installl a video decoder if I use the VGA port. Can I install WINDVD or PowerDVD software and have the decoder show up in the Sage Video Detail setup selection or is there something I need to do extra?

What drivers do you have installed for the 350 card? I had the same issues as you until I installed the drivers found in this thread:

http://forums.freytechnologies.com/f...&threadid=5879

Hope this helps out. I no longer have any issues with my 350 and the OSD. been over a week without any locks of any kind.

[carlgar]

Bathel what speed system are you running on? Since I did encounter 1 lockup with hyper-threading disabled. I really think this is a speed related issue.

Is there anyone who is satisfied with the 350 and think they have a fast system? Please post your speed. It would also be useful to know if you are using the Hauppauge remote with their software. Most of these problems do seem to be centered around the use of the skip buttons.

[Catman]

I don't know if I installed those. I will check it out and see if that helps. Thanks Bathel for that post link...

[Catman]

By the way Bathel, I did download a 1.8 driver, the latest on the Hauppauge website when I installed the board 3 weeks ago. What is the difference between that driver and the one in the link?

[jphhughes]

carlgar:

My systems spec below. Ever since I installed the SHS drivers posted on this site I have had no further problems with the 350 UI in Sage 2.019

[carlgar]

JPhhughes, are you using a hyper-threading CPU? The SHS drivers have fixed most of the problems except for the soft and hard freezes I am still having. One other difference we have is that I am still running 1.4 and you are running 2.0. I really don't think that makes a difference.

I hope that most of the users reporting problems are using those drivers. I mentioned them in the first post but I suppose I should have included a link to them. At this point with 50% still having problems I have to conclude that there are still problems with the drivers that only some people are encountering.

[jphhughes]

carlgar:

No Hyper-treading CPU.