[FFmpeg-devel] [PATCH] avformat: Outputting DNxHD into .mov containers 'corrupts' following atoms until end of stsd

Michael Niedermayer michaelni at gmx.at
Fri Feb 20 12:36:13 CET 2015

On Mon, Feb 16, 2015 at 10:49:52AM +0000, Kevin Wheatley wrote:
> ffmpeg and qtdump could not decode pasp/colr atoms in the files made by ffmpeg,
> when outputting DNxHD due to the incorrect padding placement. Now we add the
> padding in the correct place, we also always add padding for Final Cut
> compatibility.
> Tidy up FATE changes due to padding changes.

applied the case for DNxHD, for the more general case, please
explain which case(s) and software need them, and how to reproduce
I dont see where the text would allow one to add such padding by
ones own choice. I just see a note that says that parsers need to
cope with it. Thats not the same as saying its ok to add it in all
But maybe iam missing something, i didnt read the whole document


Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

In fact, the RIAA has been known to suggest that students drop out
of college or go to community college in order to be able to afford
settlements. -- The RIAA
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <https://ffmpeg.org/pipermail/ffmpeg-devel/attachments/20150220/ed0178fc/attachment.asc>

More information about the ffmpeg-devel mailing list