On Fri, Feb 20, 2015 at 11:36 AM, Michael Niedermayer <michae...@gmx.at> wrote: > applied the case for DNxHD, for the more general case, please > explain which case(s) and software need them, and how to reproduce > that
My experience and by the looks of things other people using libquicktime have seen issues with Final Cut having problems reading the files if the stds http://libquicktime.cvs.sourceforge.net/viewvc/libquicktime/libquicktime/src/stsdtable.c?view=markup quicktime_write_stsd_video() line 643 is where they sometimes pad. http://comments.gmane.org/gmane.comp.video.libquicktime.devel/1348 appears to be the discussion around why they do it > 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 > cases. > But maybe iam missing something, i didnt read the whole document no I would agree it only indicates it is optional Kevin _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel