Recording won't stop

[Amused]

I've got a really weird bug. Recordings won't stop. I upgraded to the latest 4.2 Hauppauge Driver on Thursday and at the same time I upgraded to the newest GBPVR. That evening Most of my recordings didn't record because The Simpsons never stopped recording, despite having four tuners! Since then I've uninstalled & reinstalled every combination I can think of. Each time I seems to be fine until suddenly something triggers the bug and the recording service screws up. I'm currently back to the 4.0 version for Hauppauge and 1.1.5 of GBPVR after a system restore to before thus in the hope it would all be working again... it's not. My test recordings were fine the Simpsons recorded perfectly but now Fifth Gear and Numbers are still recording.. ergh 1 hour 17 and 17 mins after they respectively supposedly stopped! - Fifth Gear finialised as a recording. but numbers is still locked.


Symptoms of the bug seem to be:
The recording service freezes - shows don't stop recording, live TV never returns to sleep, attempts to restart or stop the service bring up an .NET Framework "Unhandled exception" error.

Once the rec service goes it's gone. Other shows never kick in to record despite tuners being free for them.

Some shows finished recording - the files are playable outside GBPVR but are still shown as recording while other show as still recording and indeed are - 4 hours AFTER the Simpson's had finished in one case!

A reinstall of GBPVR does nothing yet an complete reinstall of Hauppauge drivers the GBPVR fixes it for a while.

The logs seem to show the recordings as having finished...

Any suggestions/help? I've attached the logs.

Amused

[Koenie]

I had a similar problem some time ago. SUB thought me that the db was not OK. There were recordings pointing to a non-existing channel. I backed up the recordingsdump.xml, deleted the db, copied the empty.db3 to gbpvr.db3 recreated the recording sources and imported the recordingsdump.xml. That cured it for me.

[Amused]

Good idea, I'll give that a go, see if we get anywhere. Interestingly I tried a quick test this morning before work - having been powered down overnight - and the test finalized find which would seem to and everything was working again so maybe the lockup is triggered by a particular channel/mux. I'll do some more testing tonight.

Thanks for the suggestion Koen.