rav1e VS qt-avif-image-plugin

Sure. You'll see it very often in codec implementations. From rav1e, a fast AV1 encoder mostly written in Rust: https://github.com/xiph/rav1e/tree/master/src/x86

Large portions of the algorithm have been translated into assembly for ARM and x86. Shaving even a couple percent off something like motion compensation search will add up to meaningful gains.

Or the current reference implementation of JPEG: https://github.com/libjpeg-turbo/libjpeg-turbo/tree/main/sim...

Again, if anything AOM would be the one restricting licenses to AV1 (if they chose to) except AOM has stated and also published AV1 in a way to allow license free access to development (which allows people to make forks of the official build like it's open source) and usage. (1)(2) I don't see why they would suddenly change this.

You can speed up the sampling process with --vmaf n_subsample=5, which in my experience works more accurately than either 2 or 4, possibly due to this bug/feature present in multiple encoders. You might also need to manually set the number of threads used for VMAF calculation with --vmaf n_threads=16, but YMMV.

That remember me of https://github.com/xiph/rav1e which is an AV1 encoder

I put in the request for ffmpeg passthrough mastering-display data a few years ago and haven't heard of any support yet.

It's getting there.. Initial steps for FFmepg: https://patchwork.ffmpeg.org/project/ffmpeg/list/?series=8444 rav1e: https://github.com/xiph/rav1e/pull/3000

It's entirely possible to re-use bits of other HW encoders for the first pass (motion estimation, etc).

Download qjpegxl.dll and qavif.dll and copy the DLL files into imageformats folder.

libavif supports building selected dependencies locally. I have a script which builds static libaom to be bundled into libavif together with libyuv. It was necessary to add -DCONFIG_PIC=1 https://github.com/novomesk/qt-avif-image-plugin/blob/master/ext/build_local_libaom_libavif.sh Does Debian allow bundled dependencies? Because that would be a possibility how to build feature complete libavif.

KDE apps (for example gwenview) are able to open AVIF when new versions of the following packages are installed: shared-mime-info, libavif, kimageformats When you have old packages, you can still register image/avif mime-type manually and to build/install the Qt plug-in manually. If you want to try it, read manual How to install AVIF support in KDE https://github.com/novomesk/qt-avif-image-plugin

Thanks to Daniel Novomeský https://github.com/novomesk/qt-avif-image-plugin