Recording ended too soon

[WKleeven]

Sub? Anyone?

Next sunday I can test this again with F1 in Korea. Broadcast same length, about the same time, same channel, etc.
Any instructions?

Wim

[johnsonx42]

You know what it looks like? Start_time in db3-file (11.00, that's 13.00 local) is correct and in UTC, but end_time in db3-file (14.00) is in local time, not in UTC!

that bug was in the initial release of 2.5.9, but it was fixed and re-released a day later. Patch #1 fixes that issue (thread in my signature). However, it has nothing to do with your recording being short. That bug only affected the end time of recordings after they were already completed.

[WKleeven]

I'm still on 2.5.5, should I update before testing next sunday?

[Sykor]

I'm still on 2.5.5, should I update before testing next sunday?

Yes you should. It might be fixed already, and sub's current development stage probably makes it impossible to patch older releases.

[johnsonx42]

I'm still on 2.5.5, should I update before testing next sunday?

really? That end-time bug was a 2.5.9 bug... I don't understand how you could have that issue on 2.5.5. But yes, go ahead and update to 2.5.9. The version you'd download today doesn't have that bug.

[sub]

I understand now about UTC. In the db3-files start end endtime are in UTC and correct. I attached the logs, but there is not much info from yesterday anymore.
The filename suggests a recording from 13.00-16.00 which is correct (RTL GP Formule 1 - Japan (race)_20121007_13001600). In the db3-file you can see prepadding of 16 minutes and postpadding of 30 minutes. That's a total of 03:46:00.
But, in windows explorer you can see (see attachment) the length of the video is only 01:48:06 which is almost 2 hours short.

If you play it in NextPVR, does it also show a duration of 1:48:06? Explorer isn't the best at reporting durations on .ts files.

[johnsonx42]

if it happens again, make sure you capture your logs right away. None of your logs cover the time when the recording was made.

[WKleeven]

really? That end-time bug was a 2.5.9 bug... I don't understand how you could have that issue on 2.5.5. But yes, go ahead and update to 2.5.9. The version you'd download today doesn't have that bug.

I had that problem exactly a year ago too (so in a previous version), as you can see in the start of this thread.

If you play it in NextPVR, does it also show a duration of 1:48:06? Explorer isn't the best at reporting durations on .ts files.

Yes, it did.

[sub]

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

[sub]

It's not related to the end time bug johnsonx42 is referring to. That was purely a 2.5.9 bug, and was only cosmetic. It didn't effect the duration of the recording. It just involved the endtime in the database being set to the local time instead of UTC after stopping the completed recording - the recording still went for the correct period, but it showed the incorrect end time in the recording screen after the fact.