av1-avif VS jpeg-xl

The article is about avif not webp. Note the editors for the AOM avif specification don't even include Google https://aomediacodec.github.io/av1-avif/

This reminds me of something similar from the guy who implemented AVIF in Firefox. He gives a talk about the implementation [1] where he talks about the CLAP privacy problem. Basically the spec adds a field that allows for cropping of the image, but the binary file would still contain the original. This would lead users to believe some image data was deleted when it really wasn't. I always thought he spent a lot of time and effort on this for little gain, but now I'm starting to think it was worth his effort.

[1]: https://youtu.be/BUkRlfkv2D8?t=2199

And the related GitHub issue: https://github.com/AOMediaCodec/av1-avif/issues/188

So actually the same images I linked above are in the AOMediaCodec repo as well, under Link-U: https://github.com/AOMediaCodec/av1-avif/tree/master/testFiles/Link-U And I see the same issue with the yuv422 images there as well. I'm guessing Apple's AVIF implementation must be incomplete?

Created by Alliance for Open Media and worked on by Netflix, Microsoft, and Google developers, AVIF is open source - you can even weigh in on image processing and spec issues.

I've been trying to find a way edit 14bit RAW files (.ARW) to an HDR capable format (HEIF/AVIF). In the process I found out there's an official AVIF encoder (1) by AOM that seems like it should be capable of creating HDR PQ stills.

Others samples are available here : https://github.com/AOMediaCodec/av1-avif/tree/master/testFiles/Netflix/avif

AVIF can do something that resembles hierarchical JPEG and that could be useful for progressive decoding: you can have multiple layers/scales, where e.g. first a 1:4 image is encoded, then residuals to get to 1:2, then residuals to get to 1:1. Examples of this were recently added to the AVIF spec: https://github.com/AOMediaCodec/av1-avif/pull/134

shit i did not know that.. does it also work well with wordpress etc? because the only downfall of avif is bunch of extra steps on a nginx to get it to work right.. Also, u/LITUATUI 's comment, do i just change avif to jpeg-xl? i found something but didnt fully finish reading yet https://github.com/ImageMagick/jpeg-xl

One of the most interesting things to me is that JPEG-XL is under an open Patent License, unlike the original JPEG.

https://en.wikipedia.org/wiki/JPEG_XL

Also, Google contributed quite a bit to it's development. As the patent grants show:

https://github.com/ImageMagick/jpeg-xl/blob/main/PATENTS

https://github.com/libjxl/libjxl/blob/main/PATENTS

Microsoft seemed to have gotten a patent on part of it's implementation (which Google also tried to get). Not sure if Google will pay to invalidate that patent, but I have a feeling they are more likely to defend AVIF.

https://www.theregister.com/2022/02/17/microsoft_ans_patent/

Google's control is a little concerning, but I do feel there are bigger fish to fry then choosing between two free formats. Like H.264 and H.265 patents.