Recording does not stop at end of show

[sub]

What time was the SBS recording supposed to start and stop?

[keith_leitch]

Both recordings were set to start at 7:00 AM and finish at 7:10 AM, with no buffer. The SBS recording was a short German newscast occupying those times in the guide. The other recording I set manually.

[terencedactyl]

I'd need to logs to have something to go on.

It didn't happen again when I tried last night. Will keep an eye out and post next time it occurs.

I don't know if it will help but when watching the film I recorded yesterday morning when the problem occurred (see my previous post) trying to skip forward resulted in skips of around 20 minutes instead of the usual 1 minute. Unfortunately i routinely delete things after watching them and forgot to save this one.

Regards
Terence

[sub]

Both recordings were set to start at 7:00 AM and finish at 7:10 AM, with no buffer. The SBS recording was a short German newscast occupying those times in the guide. The other recording I set manually.

Keith, those logs are full of messages about GraphRecorder, and nothing else (on the recording thread) once those messages start, so I'm assuming its related to that plugin. Are you able to reproduce the problem with only the built-in recording plugins?

[keith_leitch]

Keith, those logs are full of messages about GraphRecorder, and nothing else (on the recording thread) once those messages start, so I'm assuming its related to that plugin. Are you able to reproduce the problem with only the built-in recording plugins?

I will try. The problem is that I currently have only one DVB-T tuner, so simultaneous recordings are irrelevant unless I use the virtual tuner as well.

My instinct is that it is not being caused by the plugin, because SBS is the station that would not stop recording, and is one of the stations on the DVB-T tuner (meaning that it would be using the built-in recorder). In past trials it has been either source that keeps recording.

Could you have another look at the logs? I find it hard to believe that there are only messages about Graphrecorder, as the SBS station was not using it. Is it possible that the log entry for SBS did not occur because I had to stop it by restarting the recording service?

[sub]

My instinct is that it is not being caused by the plugin, because SBS is the station that would not stop recording, and is one of the stations on the DVB-T tuner (meaning that it would be using the built-in recorder). In past trials it has been either source that keeps recording.

Could you have another look at the logs? I find it hard to believe that there are only messages about Graphrecorder, as the SBS station was not using it. Is it possible that the log entry for SBS did not occur because I had to stop it by restarting the recording service?

I've just doubled checked this. It correctly starts the SBS recording at 7:00:00 in the logs. A few seconds later it starts the GraphRecorder recording. After that, zero messages coming out of the recording management thread other than GraphRecorder messages. It makes me think control was never returned to GB-PVR, so there is no chance for GB-PVR to tell the SBS recording to 'stop'.

[keith_leitch]

Both recordings were set to start at 7:00 AM and finish at 7:10 AM, with no buffer. The SBS recording was a short German newscast occupying those times in the guide. The other recording I set manually.

For what it's worth, I repeated exactly the same test today (using SBS from the DVB-T tuner and a streaming station from Graphrecoder, same start and end times, 7:15 AM to 7:25 AM, no buffer). Both recordings succeeded and behaved exactly as expected. Whatever is happening seems to be caused by some other undetermined factor.

Here are the logs containing today's test.

[keith_leitch]

I've just doubled checked this. It correctly starts the SBS recording at 7:00:00 in the logs. A few seconds later it starts the GraphRecorder recording. After that, zero messages coming out of the recording management thread other than GraphRecorder messages. It makes me think control was never returned to GB-PVR, so there is no chance for GB-PVR to tell the SBS recording to 'stop'.

OK. Very interesting theory. I will pass this long to Carpe to see what he has to say. Carpe, I know this is a busy time, but when you have a few minutes could you please check the last few entries of this thread: http://forums.gbpvr.com/newreply.php?do=...y&p=319533

The quick summary is that simultaneous recordings are SOMETIMES not ending until I restart the recording service. I have only one tuner, so these have always involved Graphrecorder, which may be the culprit.

The logs to which Sub refers are attached.

[keith_leitch]

I've just doubled checked this. It correctly starts the SBS recording at 7:00:00 in the logs. A few seconds later it starts the GraphRecorder recording. After that, zero messages coming out of the recording management thread other than GraphRecorder messages. It makes me think control was never returned to GB-PVR, so there is no chance for GB-PVR to tell the SBS recording to 'stop'.

I have a question for you about this. I am planning some batch-file workarounds to this problem as follows:

- A scheduled task to use GBPVRCLI to periodically check for negative numbers in the pending recordings or time remaining in active recordings. Recording service to restart when this occurs.
- Entries in the prerecording batch file to check if the file already exists (because it was interrupted by the restart), rename it and use addepisode.exe to place it in the database.
- Entries in the prerecording batch file to check whether another recording is starting simultaneously, and to pause for one extra minute if so.

The last point is preventative. My intention is to "Stagger" the recordings so that they do not start simultaneously (which seems to be causing the problem). My questions are:

1) Is delaying the actual recording likely to do any good, or do you think that the problem is caused by the two recordings being LAUNCHED simultaneously from within GBPVR?

2) Does the program consider a recording to have "started" as soon as the start time occurs, or only after the file starts to generate?

[sub]

1) Is delaying the actual recording likely to do any good, or do you think that the problem is caused by the two recordings being LAUNCHED simultaneously from within GBPVR?

To be honest, I have no idea what is caused by. I've only really had your one logs to go on, and can only see the symptoms, not the cause.

2) Does the program consider a recording to have "started" as soon as the start time occurs, or only after the file starts to generate?

It marks it as "recording" when it tries to start the recording. Before that its "pending".