Rendered at 07:04:02 GMT+0000 (Coordinated Universal Time) with Cloudflare Workers.
ksec 4 days ago [-]
Considering Apple's support and product cycle. You are looking at a Billion devices supporting JPEG XL between now and end of next year. It might be low in percentage, but it is still a substantial number.
y2244 4 days ago [-]
As an aside - My Firefox updated the other day and now has no sign up VPN built in with multiple countries available to choose. Very welcome feature.
jadecarter68 4 days ago [-]
I've been testing JPEG-XL on nightly, it's a lifesaver for high-res photos. Half the size of PNG with no quality loss.
nateb2022 4 days ago [-]
What sites already are using JPEG-XL en masse?
intelkishan 4 days ago [-]
How is the support for JPEG-XL across other browsers and local photo viewer applications?
Waiting for enabled by default in Firefox (already in nightly 153) and Chrome (hopefully this year).
nextaccountic 4 days ago [-]
Is there any hardware accelerated jpeg xl implementation? Like VA-API's VAProfileJPEGBaseline for jpeg
throawayonthe 4 days ago [-]
could you tell more/point to resources about hw-accel jpegs? does it make a difference for some sort of pipeline/batch operations or 'normal' use too? are there issues with some jpeg features being unsupported? i haven't heard almost anything about this
nextaccountic 3 days ago [-]
it's a throughput thing yes, or in my case it's also a desire to not hog the cpu with bulk image processing
features like progressive jpegs and some color spaces aren't supported. I think it could be but it isn't and not sure why
jpegs found in the wild will typically not make use of hardware acceleration or use just it for a subset of the decoding (not sure about the details). browsers didn't bother using hardware acceleration for jpegs just for the images that can be processed fine
so it is meant for jpegs you control rather than jpegs you find on the web. unless you convert them yourself
From your link.
huh, yeah, says 14.12%... i could have sworn it's on by default in chromium now? it worked in my browser!
nevermind, i had the flag enabled previously :/
https://jpegxl.info/resources/jpeg-xl-test-page.html
Doesn't look very good.
features like progressive jpegs and some color spaces aren't supported. I think it could be but it isn't and not sure why
jpegs found in the wild will typically not make use of hardware acceleration or use just it for a subset of the decoding (not sure about the details). browsers didn't bother using hardware acceleration for jpegs just for the images that can be processed fine
so it is meant for jpegs you control rather than jpegs you find on the web. unless you convert them yourself