Recording ended too soon

[WKleeven]

Unfortunately your logs dont seem to cover that recording time, so there isn't much analysis I can do.

I understand. But I think you wouldn't find anything in those logs.

I thought maybe the logs from last year could help. In post #1 of this thread I wrote I attached the logs (of the incident 1 year ago), but I can't see those logs. But in post #14, you mention you saw something in the logs. Could these logs have been lost from the post??

Anyway. What next? Update to 2.5.9? I'll test again next sunday. Some preparations I need to do for that? What to post (logs, db3, ...??)?

[sub]

Log file attachments are deleted from time to time, usually after a year or so, to keep the backup size manageable. Even if they were there though, I probably wouldn't waste much time looking at logs from last year, from an older version you're not even running anymore.

Update to the current release, and if it happens again, post the logs.

[WKleeven]

Do I have to turn on a special logging or something? I remember I had to do that long ago with an issue I had then.

[sub]

No, the default logs should be enough. This would tell us when it's trying to start and stop recordings, which will be enough to see anything odd going on with timezones like you suspected earlier in the thread.

[WKleeven]

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.

In the log I saw parallelprocessing and postprocessing things. I don't think this caused the problems, I have been playing around with this recently (not last year when I had the same problem). But I attached the scripts to be complete.

Wim

EDIT:
It happened on recording from the digital card on an encrypted SD channel with a dvb-c epg source.
I think (but I'm not sure) the file-size was greater when a looked at 8.30 local time than in the end.

And now, I have problems with NTRAY, it doesn't work. Also the program freezes when trying to program a new recording. I manually stopped 3 services (ntray.exe, nextpvr.exe, nrecord.exe) and started the NPVR service again via windows, programs, npvr, etc. But problem still there. The show I programmed IS beging recorded at the moment. At the moment I can't reboot, but I expect this will resolve the problem with ntray.
The show I am recording now, is the same as I recorded this morning (being broadcasted 2x today), but I'm now recording with analogue card.

EDIT2:
The analog recording went fine!

[WKleeven]

Sub, did you have any time to look at the logs?

[sub]

In your logs it shows your recording starting at 7:00am

2012-10-14 07:00:00.274 [INFO][8] DigitalRecorder.StartStream(E:\Recordings\RTL GP Formule 1 - Korea (race)\RTL GP Formule 1 - Korea (race)_20121014_07151000.ts)
2012-10-14 07:00:00.274 [INFO][8] Creating BDA graph
2012-10-14 07:00:00.274 [DEBUG][8] Using tuner TechniSat Mantis DVBC BDA Receiver (1)

Then a few minutes later the epg update starts, killing the recording that was in progress:

2012-10-14 07:03:12.953 [DEBUG][9] No C:\Users\Public\NPVR\Scripts\UpdateEPG.bat file found
2012-10-14 07:03:12.953 [DEBUG][9] Checking for any DVB/ATSC listings
2012-10-14 07:03:12.963 [INFO][9] DigitalRecorder.StartStream(c:\devxxxxxx\null.ts)
2012-10-14 07:03:12.963 [INFO][9] Creating BDA graph
2012-10-14 07:03:12.963 [DEBUG][9] Using tuner TechniSat Mantis DVBC BDA Receiver (1)
2012-10-14 07:03:12.973 [DEBUG][9] About to auto detect capture filter...
2012-10-14 07:03:12.973 [DEBUG][9] Got capture filter: 'TechniSat Mantis DVBC Capture BDA Receiver'

It's a known bug that the EPG update can interfere with recordings. It's on my list to look into. For now, I'd suggest you move your EPG update to the middle of the night or sometime the tuner is unlikely to be inuse. I think if you'd had the 'out of process digital recording' option enabled, the EPG update would have failed and your recording would have run to completion.

[WKleeven]

I don't understand why last year I got a recording length of 54 mins, because it would mean the epg update would have taken place at 7:54. Maybe at that time, the epg update was later than nowadays. But I'm not sure about that.

Anyway, I'm glad you found the problem and it's so easy to solve. Thank you very much!

[sub]

I cant tell you anything about last year. I dont even know if it's the same problem.

[WKleeven]

I cant tell you anything about last year. I dont even know if it's the same problem.

True.

It looks like my problem has a workaround for now. I'm sorry I didn't know it was a known issue.

I'm not sure about the broadcast time (probably not 7.00 AM locally) , but 28-10 there's a new F1 broadcast. I will report then.

Thanks for the help.

EDIT: it's 10.30 AM locally, so unfortunately not exactly the same time (that would be best for testing; there are other broadcasts at about the 7.00 AM, but they are shorter).