Opened 7 years ago

Closed 6 years ago

#10623 closed Bug Report - General (Fixed)

Incorrect duration during playback

Reported by: skd5aner <skd5aner@…> Owned by: Jim Stichnoth
Priority: minor Milestone: 0.27
Component: MythTV - Video Playback Version: 0.25-fixes
Severity: medium Keywords:
Cc: Ticket locked: no

Description

Recordings made via my analog mpeg2 encoders (PVR-250/PVR-500) prior to upgrading to 0.25 report a wildly inaccurate duration length when played back in 0.25. (i.e., 1 hour recording reported as 8+ hours in length). The current location of playback is accurately reflected on the progress bar, it's just the the total length is too long. This does not appear to impact recordings made after the upgrade from the same encoders, only ones made prior.

Running a mythcommflag --rebuild on the offending file will resolve the improper length, however it would take significant work to manually rebuild all existing recordings in the library impacted by this problem.

Attachments (1)

mythfrontend.20120417174005.21192.log (106.3 KB) - added by skd5aner <skd5aner@…> 7 years ago.
MFE log, -v playback, second file played back is 1hr long, but registers as 10+ hours

Download all attachments as: .zip

Change History (5)

Changed 7 years ago by skd5aner <skd5aner@…>

MFE log, -v playback, second file played back is 1hr long, but registers as 10+ hours

comment:1 Changed 7 years ago by skd5aner <skd5aner@…>

Attached log with -v playback --loglevel debug. There were two playback attempts. The first was playing back a file that initially exhibited the problem, but was "resolved" after running mythcommflag --rebuild. The second is one that exhibits the problem and has not been rebuilt. It's an hour long show, but reports as over 10 hours.

The reported length of time doesn't appear to be consistent across impacted recordings.

comment:2 Changed 7 years ago by skd5aner <skd5aner@…>

I should also mention this is happening basically for any MPEG2 recording (noticed on several QAM recordings as well), so not just limited to PVR-250/500 recordings.

comment:3 Changed 6 years ago by Jim Stichnoth

Milestone: unknown0.27
Owner: set to Jim Stichnoth
Status: newaccepted

comment:4 Changed 6 years ago by Jim Stichnoth

Resolution: Fixed
Status: acceptedclosed

This should be fixed in Master by 49dbed5be0729b04a5f0fd0426a32fceb2dd7935 and related commits.

In general, without a pre-built seek and duration table, we are at the mercy of the underlying ffmpeg libraries to get accurate position, duration, and seeking. This means it's most reliable to regenerate the seek tables for recordings made pre-0.27.

Note: See TracTickets for help on using tickets.