[FFmpeg-trac] #4774(ffmpeg:new): Incompatibilities between XBMC/Kodi & mkvalidator relating to how FFmpeg muxes MKVs

FFmpeg trac at avcodec.org
Sun Aug 16 16:55:15 CEST 2015


#4774: Incompatibilities between XBMC/Kodi & mkvalidator relating to how FFmpeg
muxes MKVs
-------------------------------------+-------------------------------------
             Reporter:  Drag0nFly    |                    Owner:
                 Type:  defect       |                   Status:  new
             Priority:  normal       |                Component:  ffmpeg
              Version:  git-master   |               Resolution:
             Keywords:  mkv muxer    |               Blocked By:
  timecode chapter                   |  Reproduced by developer:  0
             Blocking:               |
Analyzed by developer:  0            |
-------------------------------------+-------------------------------------

Comment (by gjdfgh):

 > I think we are venturing a little outside of what the issue is here, as
 it should not be that difficult to make sure FFmpeg muxes the files
 correctly; if there is a willingness to do it that is.

 Sure. It's not like we want to refuse fixing bug, or even just producing
 "nicer" files. But we don't know the exact cause of this behavior yet.

 > So although mkvalidator reports issues only with FFmpeg-generated MKVs,
 this is somehow not related?

 Even if it points out "invalid" things, mkvalidator can have bugs too, or
 not be updated to latest mkv de-facto standards. (The keyframe thing still
 seems strange - it might be a legitimate issue, but it doesn't seem to
 happen in your sample file.)

 > Also, if there is no spec, how can one design players to play back this
 material?

 You try what works. Maybe this sounds cynical, but this is normal in
 multimedia.

--
Ticket URL: <https://trac.ffmpeg.org/ticket/4774#comment:15>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker


More information about the FFmpeg-trac mailing list