Recordings getting stuck after end time

[keith_leitch]

I have a recording (logs attached) that continued for about 36 minutes after the end buffer. I had to reset the recording service to stop it. The recording itself looks to be a reasonable length, but the recording service was convinced that it was still in progress. The Slimm-GBPVR tray app (which reports details on recordings in progress) claimed that Shortland Street was recording, and would end in "-36 minutes".

This problem used to plague me, but I thought I'd found the solution about a year ago. I can't even remember what I did, now. I hope someone has a simple suggestion.

[johnsonx42]

I had this problem as much as several times a week with GB-PVR. The problem even continued in NPVR, until one of the patches after 1.5.31 apparently fixed it. NPVR now does what it calls an 'async device stop' which seems to prevent this from occurring. To my knowledge it was never determined exactly why this would happen, only that one of the calls to stop the device would simply never return, and thus that thread of the recording service would simply go into a coma waiting forever.

[keith_leitch]

I had this problem as much as several times a week with GB-PVR. The problem even continued in NPVR, until one of the patches after 1.5.31 apparently fixed it. NPVR now does what it calls an 'async device stop' which seems to prevent this from occurring. To my knowledge it was never determined exactly why this would happen, only that one of the calls to stop the device would simply never return, and thus that thread of the recording service would simply go into a coma waiting forever.

Well, that is very bad news if so, as I can't upgrade to NPVR without breaking several plugins that are necessary to achieve my purposes. As I said, it hasn't happened to me for nearly a year, so I will hold out hope that either a) someone else has additional insights, or, b) this ia a one-off that won't occur again for another year.

[johnsonx42]

the thought was that it was something in the driver that would sometimes cause this problem, so you could try a driver update, or maybe even try an older driver if you can get one. I'm just guessing at this point, but sub seemed to feel it was some sort of driver hang.

By the way, the indication that you have the same problem as I and others did is the end of your GBPVR Recording service-native log:

Code:

2010-12-07 05:24:00.022    VERBOSE    BDARecorder::StopRecording()
2010-12-07 05:24:00.022    VERBOSE    StopRecording()@1

There should be six checkpoints in the StopRecording sequence, but it gets to only the first one and then the log ends. You could let it sit for days like that and nothing else will ever get written to the native log. Initially it happened the same way in NPVR, it would only get to part-way though stopping a graph (recording) then just go to sleep. At one point for three weeks in a row this happened every Thursday evening, causing all the prime-time shows to be missed... naturally my wife's shows were all on Thursday, casting further wifely ire at me and my "stupid tv computer project".
If you like you can read here: http://forums.gbpvr.com//showthread.php?...ed-all-day
and here: http://forums.gbpvr.com//showthread.php?...ole-system
and here: http://forums.gbpvr.com//showthread.php?...op-a-graph

[keith_leitch]

the thought was that it was something in the driver that would sometimes cause this problem, so you could try a driver update, or maybe even try an older driver if you can get one. I'm just guessing at this point, but sub seemed to feel it was some sort of driver hang.

Thanks very much; this is useful information.

Do you mean the driver for the DVB-T tuner?

I have a process that polls every five minutes to see if it should put the computer into standby. At one stage, I was playing with having it detect whether any recordings were waiting with a "negative" time until they end, at which point I intended to restart the recording service. I may get back to this.

I will also try restoring from a recent backup to see if the problem just occurred.

I have the same wifely problems, by the way. She won't even touch the remote.

[johnsonx42]

Do you mean the driver for the DVB-T tuner?

Yep.

I have the same wifely problems, by the way. She won't even touch the remote.

Just think, without wives we'd all manually schedule recordings by direct binary input into the database using toggle switches on the front of the computer.