top | item 46599632

(no title)

out_of_protocol | 1 month ago

https://cloudinary.com/blog/jpeg-xl-and-the-pareto-front

Oldie goodie article with charts, comparing webp, jpegxl, avif, jpeg etc. avif is SLOW

discuss

order

xnx|1 month ago

> This consolidates JPEG XL’s position as the best image codec currently available, for both lossless and lossy compression, across the quality range but in particular for high quality to visually lossless quality. It is Pareto-optimal across a wide range of speed settings.

Wow. Nice. Big improvement if JPEG and PNG can be replaced by one codec.

lambdaone|1 month ago

And even better if someone can implement the whole massive spec securely...

adgjlsfhk1|1 month ago

The part I'm more excited for is all the image-like/bundle of image like data that until Jpeg-xl didn't have any good codecs (usually implemented as folders of images). One clear example of this is PBR in blender and friends. (e.g. a combo of normal map, roughness, color, metalness etc)

hulitu|1 month ago

> Big improvement if JPEG and PNG can be replaced by one codec.

By one ? Ten maybe: webp, avif, ...

smusamashah|1 month ago

JPEG at lowest quality looks much better here https://cloudinary.com/blog/jpeg-xl-and-the-pareto-front#wha...

cfreksen|1 month ago

That means that SSIMULACRA2 does not capture quality perfectly.

Note that in that figure the formats are compared at the same SSIMULACRA2 score, not at the same file size. In the "very low quality" category, JPEG uses ~0.4 bpp (bits per pixel), while JPEG-XL and AVIF use ~0.13 bpp and ~0.1 bpp, respectively, so JPEG is roughly given 4 times as much space to work with. In the "med-low quality" category, JPEG-XL and AVIF use around 0.4 bpp, so perhaps you should compare the "very low quality" JPEG with "med-low quality" JPEG-XL and AVIF.

After reading your comment, I assumed you had missed the bpp difference. Please excuse me if I assumed incorrectly.

daemonologist|1 month ago

Keep in mind that lowest JPEG is 3-4x the size of the lowest JXL and AVIF - similar to the size of their "med-low" (top row).

lern_too_spel|1 month ago

Chromium is not using libjxl, which is the decoder that is evaluated in this article. The SVT encoder is much faster than the AOM encoder for AVIF.

charcircuit|1 month ago

This doesn't use hardware accelerated decoders and encoders.