- cross-posted to:
- firefox@lemmy.ml
- jpegxl@lemmy.world
- cross-posted to:
- firefox@lemmy.ml
- jpegxl@lemmy.world
JXL is based.
I took my existing JPEG file, compressed it using JXL, 15% smaller.
Then I decompressed it again into JPEG. The file was bit-for-bit identical to the original file (same hash). Blew my mind!
Directly using JXL is even better of course.
So it’s called xlarge… And it makes files smaller.
Why.
The same amount of JXL gives you more image than JPEG? Also, it supports ridiculous resolutions (terapixel).
Google’s involvement should always raise concerns but I guess it’s good Mozilla is trying to improve stuff.
Please let this happen!
I have a nagging doubt; jpeg-xl has a very extensive feature set (text overlays, etc). meanwhile, tech/media consortia want a basic spec for AV1 + OPUS on chip and push that to all media capable devices. we can expect av1, avif and opus to be ubiquitous in a few years. So i think they will prioritise AVIF.
I did some reading in AV1 and it’s derivative formats - are they any more accessible to Linux than HEVC/H265? Fedora IIRC removed support for them and a few other codecs out of the box over some patent concerns or something.
Google’s involvement is weird, not for any conspiracy reasons but because the chromium team previously cancelled JPEG-XL.