Recording ended too soon

[WKleeven]

Everything okay now, so it must have been the EPG update problem. Thanks.

[WKleeven]

This afternoon, the problem occurred again. Definitely not an EPG problem this time (epg-update hour 6:45, show 13.15-16.00 with 5 mins. pre and 45 mins. postpadding).
This evening, when I saw that the recording was too short, I checked the logs and saw no error. After having watched (part of) the show, I now wanted to post the logs and saw that the old logs were already overwritten (I didn't know that would happen so fast).

Sub, I'm posting the logs and db3-file anyway hoping you can help anyway. I couldn't stop the recording service because a show is recording now so I copied the logs to another directory and zipped them there. I don't know if this is okay.
Recorded length 1:36:13 (in NPVR, 1:36:14 in wmp)
Programmed: 13.15-16.00 with 5 mins. pre and 45 mins. postpadding.
Last part of the filename correct (the part that indicates the time: 13151600).
Normal info in db3-file.

[sub]

I cant see that recording in your logs, so I don't have much to go on. The logs just full with messages about streaming to a client.

[WKleeven]

I cant see that recording in your logs, so I don't have much to go on. The logs just full with messages about streaming to a client.

Yes, that's a new recording taking place and being watched timeshifted by my wife via the MVP.


In the beginning of the evening, I saw something like "Stopping recording..... Past end time of recording" in the logs so I think the recording ended normal, like the db-3 file suggests and the "changed on" info in windows explorer (16:45). I don't know what happens to the file after NPVR stops recording but I think that's when things go wrong. I think the file is being cut off at that moment for whatever reason.

One of the other times this same problem happened, while the recording was going on I saw a recorded length (1.5 hours) greater than the end result (00:03:09) which suggests the same (post #35):

Well, the recording started normal. After an 1.5 hours or so (that is after 8.30 local time, 6.30 UTC) I checked and it was still recording. I played the recording and it did, stopped the playback. Still recording. Thought everything was going normal.

When recording finished, I checked. SAME problem. Length (in NextPVR) 00:03:09 instead of 2 hours, 45 mins and 15 mins pre en 30 mins postpad (165 mins.+45 mins. padding=210mins. total).
db3-file looks normal. File-name normal. File-size 174.083 kB.

Is there a way to keep the logs from being overwritten? There are 2 more F1 shows in the next weeks to test (today's problem happened with a F1 show too).

Could it be related to the length of the broadcast? All the broadcasts that I have these problems with are F1 which last 3 hours or so.

[mvallevand]

Yes, that's a new recording taking place and being watched timeshifted by my wife via the MVP.

What fills up the logs is the server side of laptop client streaming playback of the race. The playback position table does show that it only recorded 5773 seconds but there are logs going back that far.

Martin

[johnsonx42]

Some devices just sometimes mysteriously stop delivering data for reasons unknown.

Maybe try enabling out-of-process digital recording? I've found it to be more reliable, and at least that way some info about the recording processes would be in a separate log file (NDigitalHost-xx.log) that doesn't get overrun by other messages.

[WKleeven]

What fills up the logs is the server side of laptop client streaming playback of the race. The playback position table does show that it only recorded 5773 seconds but there are logs going back that far.

Martin

I assumed it was the other show, but I watched the recorded part of the race indeed via the laptop. And good to see there's something in the logs that confirms not the entire show had been recorded.

Some devices just sometimes mysteriously stop delivering data for reasons unknown.

Maybe try enabling out-of-process digital recording? I've found it to be more reliable, and at least that way some info about the recording processes would be in a separate log file (NDigitalHost-xx.log) that doesn't get overrun by other messages.

I'll try this. In the next weeks there are 2 more F1's to test with.

[johnsonx42]

As you have Windows 7 Ultimate, that means you also have Windows Media Center installed. If you ever configured it, even once just for testing, it may occaisionally grab the tuner to do a channel scan which might disrupt a recording in-progress.

discussion here: http://forums.nextpvr.com/showthread.php...uot-folder

[WKleeven]

Thanks for the tip, but I've never started WMC on the desktop which is the server, I did on the laptop but that's the client. I added the registry key anyway.
Oktober 18th is the next F1, I'll post then. Is there no way to keep the logs from being overwritten?

[WKleeven]

Recorded F1 and got the same problem again. Show started at 19.00, 10 mins. prepadding so recording started at 18.50 local time.
At about 19.30 I logged in and wanted to watch the show, but there was only 6:49 mins. recorded. I tried to watch the broadcast live and tried to get the recording started again (had problems with newcs at that time).

I think there's no entry in the logs of the time the problem occurred, here's a fragment of ndigitalhost-21.log.1:
2012-11-18 18:50:01.197 [DEBUG][5] Temp at 18-11-2012 18:50:11
2012-11-18 19:34:15.871 [INFO][5] DigitalRecorder.StartStream(LIVE&C:\Temp\live-RTL 7 HD-6933.ts)

Added the logs.

Wim