On Mon, Jun 8, 2020 at 2:56 AM Moritz Barsnick <barsn...@gmx.net> wrote: > > On Sun, May 10, 2020 at 00:59:25 +0900, Ryo Hirafuji wrote: > > I can create and send a new patch without these workaround lines, but of > > course, it will crash if the ffmpeg will be built with older versions of > > libaom. > > Actually, it depends on the runtime version of the library, not which > version it was built against. (They can differ.) > > You could encapsulate the code into a check of aom_codec_version() > > (1<<16|0<<8|0). Assuming 1.0.0 is the current, buggy release. > > > How should I resolve this backward compatibility issue? or I don't have to > > consider it? > > Having a workaround for a known issue does not hurt, IMO, especially > since a fixed version is not available yet (or is it?). >
2.0.0 is out. libaomenc.c just got an update to remove the experimental flag when it's present: https://git.ffmpeg.org/gitweb/ffmpeg.git/commitdiff/49d37b4b618b20669bbd7081e6af2aecf9c09745?hp=4bc5eb27a74e3eb1805f21a33d4ef08f8f7026e4 _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
