Recording Overruns (time left -600 minutes)

[djmuk]

Occasionally the recording service seems to forget to stop recording, so I come back to the machine & see the Tray icon reporting 'Recording show XYZ -604 minutes left'. Often the machine is at 100% CPU with recording service using it all!

The only cure is to 'Kill' the recording process via task manager which leaves the show as a 0 byte file. The machine is unusable so it is not easily possible to do any investigation prior to killing the process.

Surely the recording process checks that the end time is not in the past rather than just checking to see if end time = current time?

It is just possible that this is being caused by shutting the machine down (either off or standby) while the recording is running... but as I see the problem several hours afterwards I cannot be sure!

David

[sub]

Enable log flushing in the config app, then next time the problem occurs, zip and attach the logs. Include a description in the post of what times the recordings was supposed to run for.

[djmuk]

It did happen afterwards but I didn't get a chance to grab the log files before they got zapped...

I did have a quick a look at them and there seemed to be an entry in there which went as follows...

starting recording, file is too small, starting second chance recording

& that was it - the 2nd chance file was zero length as well....

this was on a back-back recording where the first recording had finished and the second one failed in this way, I don't know if that is significant...

I had been using slimmgbpvr which I have taken off for now as I don't think it happened before I put that on.... & I haven't had the problem so far but I have taken off a lot of scheduled / season recordings so there are fewer recordings being done as well..