Closed IcedQuinn closed 1 year ago
Thanks, feel free to test https://github.com/void-linux/void-packages/pull/42438 Let me know if you run any issues.
Issues become stale 90 days after last activity and are closed 14 days after that. If this issue is still relevant bump it or assign it.
libavif
is built in such a way that its companion programavifenc
is included within system-wide PATH but is unable to encode. No encoders are bundled with it. It only includes a decoder (dav1d
.)You can verify the availability of encoders and decoders as in:
avifenc
is able to be built with other encoding libraries such aslibaom
(which is the absolute slowest but preserves the most image detail per byte.) A custom build depending onlibaom
shows a different result:Now this part is tricky because the dependencies are build-time optional but not auto detected at run time. As I recall it supports SVT-AV1 (the fastest),
rav1e
, andlibaom
, with an additional subdependency that iflibaom
is built with JPEG-XL it will allow use of the butteraugli metric which further preserves image fidelity.In ideal cases:
libaom
would include its optional JPEG-XL dependency for access to the butteraugli metric. Otherwise you are stuck with SSIM which is good and usable but is still somewhat worse. (SSIM is only concerned about preserving edges while butteraugli is a full psychovisual metric.)libavif
would also have its optionalrav1e
, SVT-AV1, andlibaom
dependencies--or at leastlibaom
and one other to allow for fast and slow options.FFMPEG already depends on most/all of this so they will already be in the repository for that. This would likely just be some tweaks to build flags and dependencies. However those are foundational libraries so there is very likely to be a high amount of resistance to making these simple tweaks.
Currently you need to do a custom build of some of these libraries to actually encode AVIF. However, binaries are provided that are intended to do this but are misconfigured so as to be present but worthless.