end of file bug

[Maladin]

I'm still seeing the end of file bug. My system locks up hard on the hour after a recording finishes. Are others seeing this too, or is there a fix and I missed it? Running 2.0 beta 15 and pvr 350 drivers 1.8.22020 from shspvr.

I'm also seeing the pvr 350 output hang up sometimes but without hanging the system. Putting SageTV into sleep mode and restoring it allows video playback on the pvr 350 but the UI is gone until I reboot.

I'm so frustrated by this long standing bug I am actually considering switching to a competing product.

[falchulk]

Long standing bug???? This is a beta. Once sagetv is in production, then you can be frustrated. Dont worry, its almost there.

[AJ Bertelson]

I am seeing it to, the end of file bug.

[stanger89]

Have you tried enabling the "never_stop_encoding" or whatever, property in the properites file?

[Maladin]

Originally posted by falchulk
Long standing bug???? This is a beta. Once sagetv is in production, then you can be frustrated. Dont worry, its almost there.

Long standing beta bug, which makes the product frustrating to use (lost recordings because the system is hung, etc.)

In my business this is a top priority kind of bug, system crash / data loss. Its been known for 2 months and not fixed. If I left such a bug in the product for so long, my boss would tear me a new one, beta or not.

Jeff does great work and I'm not trying to slam him here, but if you're suggesting that I should not be frustrated, I will respectfully disagree!

[falchulk]

Volunteer Beta testers dont have the right to be frustrated. They did not make you test for them. They asked for VOLUNTEERS. I dont know why you would go to a competing product just becasue a feature is not 100% working in a beta. Thats my only point.

[Maladin]

Well I see your point falchulk. Mine is that this late in the beta cycle, such a severe bug needs to be prioritized. If it cannot be fixed (and we all hope it can be), I won't be able to continue using this product.

The beta test agreement goes two ways. We use software which is known to have issues (even this isn't quite right; see earlier threads about alpha vs beta). The implicit agreement is that the vendor will attempt to fix the bugs we report which make the product unusable. In order to test the software I have to run it. If its crashing my system, I don't wish to continue running it.

Anyway we're off topic. The purpose of this thread was to see if others are still seeing the bug or if its specific to my system. It sounds like others are still seeing it.

[mlbdude]

It might help to know what products you use where this does work. Others could confirm that for themselves as well.

[Maladin]

You mean where my system doesn't crash at the end of a recording? BTV, gbpvr and JovePlayer don't crash. Of course my configs are different for each. For example neither BTV nor JovePlayer use the pvr 350. I think I read once that this only affects people using the pvr 350 TV out, but I don't know if that's true.

[mlbdude]

Yeah, I mean specifically apps that use the TV out of the 350 that don't crash since that seems to be the problem here. Those of us not using the 350 out definitely don't have this issue.

Maybe we can get some people having issues with the 350 to try out gbpvr to see if it also works for them. If it does Frey may be able to to learn something from it.

[Maladin]

I haven't used gbpvr extensively since SageTV is my main PVR software these days. But I have tried it with the pvr 350 and don't see crashes with the latest version. (And earlier version definitely crashed a lot.) I suppose I really should set it up with my favorites and let it run for a few days and gauge the stability.

gbpvr supports XCard too, including OSD. but that's a different thread...

I recognize that its quite possibly a driver bug and not a SageTV bug at all. But Frey has been pretty quiet about this. I'm going to load SoftICE on my htpc and see where the crash occurs, for my own curiousity.

[falchulk]

I think your last post is appropriate attitude to take. Keep reporting it as a bug with every beta release (there is a rumor that there will not be many more). It will get fixed. Threating to leave helps no one. It just means you wasted money.

[Maladin]

Since I already paid for the software, I don't see how my "threat" to leave is really a threat. I only mentioned that I would consider switching to emphasis how serious a problem it is for me. Now, back on topic...

At one time I believe Jeff said we should be using the latest Hauppauge driver from shspvr.com. Since that time there has been a new driver posted to the Hauppauge web site. I am confused as to the relationship between these two drivers, and why SHS releases a driver.

1) SHS, do you have driver source and maintain your own builds that somehow differ from the official Hauppauge release?

2) Is the SHS driver still the one to use?

3) Is anyone successfully using the pvr 350 TV out with the latest Hauppauge driver?

4) Is everyone having this problem using the SHS driver?

5) Jeff / Dan, if you are listening, can you please give an update about this bug? From my perspective its far and away the most serious remaining in the beta. The number one reason I bought SageTV instead of BTV is for pvr 350 support, and this makes it unusable.

Thanks!

[kny3twalker]

OK SHS does not write his own drivers
He has a friend at hauppauge and usually get the beta released drivers out before hauppauge post them
If you look now at the hauppauge website, you will see that the lastest drivers are the same ones that SHS has posted
Basicly we are testing and if no problems with them they go official at hauppauge's site or thats what I think
The older stuff at hauppauge website is the other stuff like hauppauge decoder, scheduler, and remote driver (and just to let you know the newest versions of everything at SHS's forum work fine)
Try using WinTV and see if the problem exists if not it is a problem with SageTV
and report the bug
this is still beta and version 2 will be out soon
be patience
furthermore Maladin
why do not you see if it is a problem with your hardware
what OS are you running and what kind of hardware
Have you made sure that the 350 is not IRQ sharing
there many things that could be happening if the problem still exists when V2 comes out then make a big deal since you have already asked more than once

[Maladin]

kny3twalker
I have no reason to believe I'm having a problem specific to my system, since Im seeing a problem others are hitting and my system works fine 99% of the time except when it occasionally hangs, on fairly common events within the application (end of file conditions on recording or playback).

I have no device conflicts, I have checked.

As promised I have been running SoftICE in an attempt to isolate the crash. The system hasn't hung yet but the application itself has. I can get no useful information since the application, although apparently hung, is simpy idle - its not using CPU and its not responding but the date it renders at the menu screen updates occasionally. One interesting thing to note is that its loading and unloading 3 DLL's about once every second: oledb32, msdart, and comdlg32. Perhaps its stuck in a loop trying to display a MessageBox.

I'll keep trying to catch the system hang and see what I can learn.

The problem does not occur with WinTV, as I've stated before. Anyway WinTV does not support an OSD on the PVR 350, it simply displays the video stream and apparently people who dont use the OSD aren't seeing the bug.

I see that Jeff did comment on the issue on a different thread so I retract my statement that Frey has been silent on this matter. I missed his post, which was prior to the beta 15 release.

After I repro the problem I'm going to try never_stop_encoding, which may make it happen less often but will not really fix it.