3 ms·
From libjpeg to libjpeg-turbo, then mozjpeg, and now jpegli, is this another great leap forward in coding efficiency? Jpegli compared to mozjpeg, WebP, AVIF & J
by computerbuster 3y ago
From libjpeg to libjpeg-turbo, then mozjpeg, and now jpegli, is this another great leap forward in coding efficiency? Jpegli compared to mozjpeg, WebP, AVIF & JXL.
- JyrkiAlakuijala 3y agoJpegli has three main deficiencies against true modern formats. First is entropy coding having no context modeling, no arithmetic coding. Second is no large integral transforms. Third is no blur-filtering, aka loop filtering. The first deficiency can be mitigated by packing jpegli into jpeg xl, giving a ~20 % improvement. The second and third deficiencies are not a big issues at high quality (libjpeg q85+), but reduces Jpegli's ability to compete in the lowest quality class, like q75-. Overall I believe jpegli is in its own class of jpeg codecs, combining the quality of guetzli while being faster than mozjpeg and allowing 10+ bits of dynamics for "8 bit" jpegs. I believe Jpegli and jpeg xl lead in the highest quality category (5 BPP). In mid quality (1.5 BPP) jpeg xl and AVIF are the leaders, Jpegli likely better than WebP. In low quality (0.5 BPP) AVIF will be great for graphics and indoor photos while JPEG XL can still outperform AVIF in nature photos. In low quality WebP can be better than jpegli. Disclaimer: I participated in development of all four formats/codecs.