Recent recording shows wrong length in timeline

[WayneD]

I have a recording from last night that is 2:01:59 in length. However, the new TS reader claims the video is only 1:41:35, and once it gets out to that length it will continue to play to the end as long as I don't attempt to skip forward (since any skipping goes back to the limit of the erroneous length). If I switch to the legacy TS reader, the length is displayed correctly.

I think that the time in ms from the log file is accurate (if I divided right):

2017-12-19 21:33:12.124 [DEBUG][1] Timing.info reports duration 7319282ms

Sub - let me know if you'd like a copy of the ts file -- it's 12G, but I could make it available to you if it would help. I've attached my recent log files.

[pBS]

i've also had these on occasion..always on long recordings of at least an hour or two, always plays to the end but no skipping past a certain point..
can't see any glitches in stream visibly, usually happens to me when another show is starting to record on another tuner..

[gEd]

i've also had these on occasion..always on long recordings of at least an hour or two, always plays to the end but no skipping past a certain point..
can't see any glitches in stream visibly, usually happens to me when another show is starting to record on another tuner..

Yep, I've had the same issue when watching formula1 races since 4.0.X was released but I've never managed to collect any meaningful logs so didn't report it. If I recall (on these 2+ hour recordings), I can't skip past the point when another recording started but the recording itself plays fine in VLC so I believe that it's an issue with the nPVR timinginfo data. Again, I know that without logs, this is just hearsay.

[HarryH3]

I've had this happen on a few 1-hour shows. I uploaded one for sub to look at recently. I don't know the status. Things can get quite busy this time of year.

[Bobins]

I also get this occasionally. If I run the file through VideoReDo (Quick Stream fix) the time displayed in NPVR becomes correct and the skip works again so it does look like a problem in the actual file upsets NPVR rather than just a file length thing.

[gEd]

Sub

I currently have this issue with a scheduled recording last friday. The latest TS reader shows recording length as 18 mins (but plays beyond that unless I attempt to skip) whilst the legacy reader (and VLC) correctly show recording length of 31mins and plays and skips fine. Both show same and correct timing.info in the log.

I ran the recording through TSDoctor which showed a few warnings in the audio stream but no errors, gave this new version the same name as the original and it then showed the correct length with the new TS reader. So it appears to be "something" in the recording that TS reader 4 doesn't like yet which the legacy version will play without complaint.

I also happen to notice that this problematic episode is at 23.9fps and yet the episode from the previous week was at 29.9fps which I thought was odd..

any thoughts on how we can isolate the problem?

[sub]

gEd how big is that file? Any chance you could supply the file for me to try improving the duration detection?

[gEd]

1.08gb

[sub]

That'd be ok for me. Any chance you could put it somewhere like dropbox or onedrive, and let me know the download link?

[sub]

Can you guys see if this one helps?