On Tue, Mar 03, 2015 at 06:17:22PM +0100, Robert Krüger wrote: > This is based on an earlier patch by Derek
please mention this in the commit message > that never went in because it > was argumented earlier that api breakage is not acceptable. However, that > was more or less relaxed after Michael noted that the replaced flag had > never been part of a release and since a number of people seem to agree, > this is the better default, I am submitting this patch now, to have it in > before the upcoming release. > > Let me know if that will be accepted and I will modify the respective fate > tests as well. have you tested the generated mov and mp4 files with some common software packages ? checking random files on my disk it seems more than half the mov files contain a colr atom but i found just a single mp4 with a colr atom, so especially testing the compatibility of the mp4 files would be optimal before this is changed [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB During times of universal deceit, telling the truth becomes a revolutionary act. -- George Orwell
signature.asc
Description: Digital signature
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
