@wb@RL_Dane Does JXL not have any directional prediction or shared data between blocks? How does it handle generation loss so well?
I assumed the VarDCT built on every coding technique that previous DCT variants used, although I’m not well versed in what those were & I may be off base
@wb
Considering smartphone photos are generally smoothed out oversharpened crap, I'm willing to write the entire sector's decisions off as nonsensical when it comes to image encoding. At least in the Android world, JPEG still largely reigns supreme. @RL_Dane
"... Interop 2024 omits JPEG XL, the most popular proposal as measured by community reactions (emojis added to proposal discussion threads). JPEG XL garnered 646 reactions, more than four times more than the second place finisher, which also wasn't included."
An unfortunate conclusion from a clearly biased group that is supposed to be unbiased. Unfortunate, unclear decision making from Interop this year.
I never said JXL is feature creep. I said the implementation of random codecs regardless of whether any are already in development is feature creep, thats a big difference.
> that's what the video-based codecs are.
How comes that implementing video-based image codecs is feature creep? Ok look, i never had something against JXL, thats your imagination playing you.
In fact, I am of the opinion that every halfway reasonable codec should be built into browsers, but only one after the other and not together in a random order for every browser.
> You're thinking from a purely web-based standpoint here.
Sure i do, the topic is literally codecs in browsers :blobcatgoogly:
> JXL would be the only promising image codec to hopefully not need to look at another one for a very long time.
I doupt it, the past has shown that new algorithms are built which are faster or make things smaller... All the time. But yes, currently JXL is a proper codec to store images.
> I can tell you right now that professional photography, medical imaging, astrophotography, etc are simply not interested in AVIF, while JXL has the features to make everyone happy across the Web and beyond
Since i like stuff to read, source please.
In my experience, codecs are used which are established in the broad masses. So here are my predictions: I have the feeling that the HEIF container will spread due to its support in common OSes, and because the operating systems do not support all codecs of the HEIF container, I think that HEIC will prevail for the time being.
But we will see
@Jain Implementing too many codecs at once can get messy, which is why a new video-based codec every couple of years is an unfortunate sight to see, in my opinion. Especially considering WebP's failure (except the lossless part).
The AVIF spec was actually submitted as a proposal for JXL, but was rejected. That should have been the sign to relinquish AVIF development, if implementing things "together in a random order" is bad for the Web since it was known it would overlap with JXL which was always supposed to be a superset of AVIF or something better.
Regarding interest from professional use cases, I've seen JPEG XL discussed for these use cases in the JXL Discord. The JPEG XL project itself touts features like wide dynamic range support, layers, excellent lossless compression, and an incredible number of possible channels. Aside from HDR, the above are missing from AVIF. So, while adoption is still early, there is excitement about having a modern codec that can handle specialized needs beyond what JPEG and PNG currently offer. More info on JXL: https://wiki.x266.mov/docs/images/JXL
HEIC is not supported pretty much at all on the Web due to licensing restrictions, which make it very difficult to ship HEIC images. I would say AVIF has the most momentum now, even moreso than HEIC, but JPEG-XL and other future formats could gain traction once native browser support spreads.
@boilingsteam I have a Sony a5000 - I’m inclined to agree based on what I’ve seen come out of that APS-C class sensor compared to the Pixel’s 1/1.3” type sensor
Geekerwan sets the bar so high for tech journalism. Testing gaming on Linux on ARM with WINE, Box64, & DXVK & getting actual results on a Nintendo switch is insane
@Jae Everything these guys do is awesome. Highlights are their smartphone chip evaluations (the Dimensity 9200+ vid is up on their Chinese channel) & the MacBook Air M2 deep dive
It looks like #GNOME is ready to embrace #jpegxl into its ecosystem! Wallpapers are being switched to JXL from WebP, & GNOME Web will adopt JXL support through WebKitGTK. The GNOME SDK is also going to be built with libjxl from now on!
@gianni what's the benefits of jpegxl over webp? I saw jpegxl being talked a lot recently but I didn't find any straight answer apart from maybe better compression?
Apparently the #samsung Galaxy S24's "downloadable" Gallery app (not sure what this means) supports JPEG-XL compression in RAW images!
> Downlodable App
> 1. Expert RAW
> The basic resolution has been improved from 12MP to 24MP, and image quality and tone in low light have been improved through nightography technology collaboration.
> In addition, Digital ND filter, which was supported as beta in previous S23, is officially provided and Auto mode is provided for user convenience.
> Additionally, storage capacity has been reduced while maintaining image quality by providing JPEG XL format.
I must say, I really like the QOI image codec despite its shortcomings for coding efficiency and flexibility - it is dead simple, easy to implement, and super effective for what it is! I'd be happy in a world where we used QOI instead of PNG for a lot of stuff. And I've already fallen in love with Zig, which I think is very easy :)
"When you uninstall a Flatpak, it can leave some files behind on your computer. Flatsweep helps you easily get rid of the residue left on your system by uninstalled Flatpaks."
Check out Flatsweep by Giant Pink Robots on #flathub!
Alt: "If you need some help with the math, let me know, but that should be enough to get you started! Huh? No, I don't need to read your thesis, I can imagine roughly what it says."
In #WWDC, it looks like Apple may have secretly dropped a hint about a new feature in Safari. Hopefully this is legit and we can welcome #jpegxl to Safari & the Apple ecosystem soon!!
"During our security research we found that smart phones with Qualcomm chip secretly send personal data to Qualcomm. This data is sent without user consent, unencrypted, and even when using a Google-free Android distribution."