Opened 15 years ago

Closed 14 years ago

Last modified 13 years ago

#10104 closed Developer Task (fixed)

Proper Duration and Position Support

Reported by: tralph Owned by: Jim Stichnoth
Priority: minor Milestone: 0.27
Component: MythTV - General Version: Master Head
Severity: medium Keywords:
Cc: Ticket locked: no

Description

Ticket to track development for proper duration and position support.

The object of this feature is to provide accurate duration and total frame count for the recorder and commercial flagger. This will address the long standing issues with incorrect duration/position for variable frame rate and frame repeats.

For videos with a position map we will use the generated duration/frame count to generate duration/position. If no position map exists we will use the timestamp and duration provided by libav.

Change History (8)

comment:1 by tralph, 15 years ago

Owner: set to tralph
Status: newassigned

comment:2 by Github, 15 years ago

dtvrecorder: update MPEG-2 parser to properly generate repeat_pict values

This is going to be used for generating correct video duration.

Refs #10104

Branch: master Changeset: be8919faf54b9c0384f44acbee3950c79e6230a8

comment:3 by tralph, 14 years ago

Resolution: Won't Fix
Status: assignedclosed

There isn't much left to do to support this. Just not enough time to work on it anymore.

comment:4 by Jim Stichnoth, 14 years ago

Resolution: Won't Fix
Status: closednew

comment:5 by Jim Stichnoth, 14 years ago

Milestone: 0.250.27
Owner: changed from tralph to Jim Stichnoth
Status: newaccepted
  1. Mythcommflag --rebuild produces MARK_DURATION_MS marks in recordedseek or filemarkup, mapping keyframes to time offsets relative to the beginning of the recording.
  1. Recorders produce this same information.
  1. New command added to myth protocol - "QUERY_RECORDER FILL_DURATION_MAP" - similar to FILL_POSITION_MAP, to send updated duration info for playback of an in-progress recording.
  1. Use the duration map during playback to provide more accurate display and seeking with durations and time offsets, by linear interpolation between close values in the duration map. Avoid using naive framerate based calculations, or inaccurate/noisy/discontinuous display timecodes from the recording. Also take the cutlist into account.

comment:6 by Jim Stichnoth <jstichnoth@…>, 14 years ago

Resolution: fixed
Status: acceptedclosed

In 49dbed5be0729b04a5f0fd0426a32fceb2dd7935/mythtv:

Error: Processor CommitTicketReference failed
GIT backend not available

comment:7 by Karl Dietz <dekarl@…>, 13 years ago

In 4995830547a1852ea46c42f3d9d5ff6a2fc490e5/mythtv:

Error: Processor CommitTicketReference failed
GIT backend not available

comment:8 by Karl Dietz <dekarl@…>, 13 years ago

In dd5a80dcbdfd0ce856a6743c2e6f89b3a11fb318/mythtv:

Error: Processor CommitTicketReference failed
GIT backend not available
Note: See TracTickets for help on using tickets.