On 08/13/2018 03:47 PM, Carl Eugen Hoyos wrote: > 2018-08-14 0:36 GMT+02:00, Thomas Daede <bztdli...@gmail.com>: >> On 08/13/2018 03:30 PM, Carl Eugen Hoyos wrote: >>> Why isn't av1 added like the existing codecs? >> >> That would generate invalid AV1 files if -strict -1 or -2 specified > > That is the idea of -1 and -2.
The idea of -1 and -2 is to allow muxing in additional nonstandard ways. However, putting this particular check behind the compliance condition would change a working muxer to a broken one once you enabled experimental, which I don't think is desirable. Presumably the check for the other codecs is to allow proprietary fourccs to be used when muxing them. I'm not sure when this is desirable for those codecs, but it certainly isn't for AV1 as it doesn't have any proprietary fourccs. >Is the specification still unfinished? >Then what is the exact purpose of this patch? It is unfinished, but this patch ffmpeg's implementation closer to the current draft. _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
