[FFmpeg-trac] #2975(undetermined:new): h264 streams don't start with timestamp/timecode 0 when muxed with Matroska

FFmpeg trac at avcodec.org
Sat Sep 21 00:38:06 CEST 2013


#2975: h264 streams don't start with timestamp/timecode 0 when muxed with Matroska
-------------------------------------+-------------------------------------
             Reporter:  jamal        |                    Owner:
                 Type:  defect       |                   Status:  new
             Priority:  normal       |                Component:
              Version:  git-master   |  undetermined
             Keywords:               |               Resolution:
             Blocking:               |               Blocked By:
Analyzed by developer:  0            |  Reproduced by developer:  0
-------------------------------------+-------------------------------------

Comment (by jamal):

 Well, for starters it's making the final duration value wrong (Should be
 10 seconds, ends up being 10.08 seconds in the examples above).

 Aside from that, now that we're writing cues for subtitle packets, those
 extra milliseconds added during muxing are in many cases making a video
 keyframe cue have a higher timestamp than the timestamp from a subtitle
 cue that comes right after it, which should not happen and promptly
 triggers warnings in mkvalidator (Something that doesn't happen with other
 codecs, like vp8 or theora, that start at pts 0).

-- 
Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/2975#comment:2>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker


More information about the FFmpeg-trac mailing list