3 ms·
First, Jpeg XL is not a Google thing, and neither is HEIC an Apple thing. Nor the AVIF part. AVIF is from Open Media which is indeed a Google Thing. Netflix j
by ksec 7y ago
First,
Jpeg XL is not a Google thing, and neither is HEIC an Apple thing. Nor the AVIF part.
AVIF is from Open Media which is indeed a Google Thing. Netflix just happen to take side with OM. JPEG XL is done by a Google Employees as well as other contributors put forward to the JPEG committee. i.e It is not a Google only format.
HEIC is really just HEVC Codec in an image format developed by Nokia and submitted to MPEG ( Not to be confused with MPEG-LA ).
So really JPEG XL isn't a walled garden. And support everything you described including HDR. The problem is Jpeg XL doesn't do so well in small image size as compared to HEIF or AVIF.
- jiggawatts 7y ago> Jpeg XL is not a Google thing, and neither is HEIC an Apple thing...<snip>...Employees as well as other contributors put forward to the JPEG committee. "Technically open" doesn't help much if each of those formats is primarily pushed by one mega-corp, optimised for their specific use-case, and no industry-wide effort materialises to establish widespread interoperability. Just last week I tried to convert raw photos to HEIF images on Windows so I could share my images in maximum quality with a bunch of iPhone users. It's basically impossible. The only tool I found was Gimp, but it doesn't properly understand colour spaces and the output looked totally wrong. I'd need OSX or IOS to author files in this format, making HEIC an "Apple thing" for all practical purposes. It's a safe bet that Google will embed JPEG XL support in Chromium, right? Will I be able to email a .JXL file to an IOS user? Will a Windows PC user with Outlook on their desktop be able to see the image embedded in their email without having to save it and open it again in Chrome? Can I paste a .JXL image into a Word document and have its various features be correctly preserved, or will this be restricted to Google Docs viewed exclusively via Chrome? Look, here's the thing: All of these post-JPEG formats are nice and all, but are worthless to me and a billion other people unless there's proper effort put into mass adoption. Real industry-wide cooperation, not just token openness. As I said, it is 2020, and nobody has a viable option for distributing still images in anything other than a handful of 20-30 year old formats. > The problem is Jpeg XL doesn't do so well in small image size as compared to HEIF or AVIF. So then why isn't NetFlix working with the JPEG XL group to add the AV1 codec as one of the encoding options? Why are they instead creating yet another standard with no adoption likely outside of their walled garden? Conversely, why are all the post-JPEG formats such utter failures? Take a look at the list: https://jpeg.org/jpeg/index.html https://jpeg.org/jpeg/index.html JPEG - The "popular one" JPEG XT - Never heard of it JPEG-LS - Never heard of it JPEG 2000 - Heard of it, never used it JPEG XR - Never heard of it AIC - Heard of it, never used it JPEG Systems - Never heard of it JPEG XS - Never heard of it JPEG Pleno - Never heard of it JPEG XL - Not yet useful, will likely never use it Clearly, whatever they JPEG group is doing, it's not working. They got lucky once, and in the 27 years since have failed to reproduce that success. This is the core point of what I'm saying: The reason that GIF, PNG, and JPG got widespread support has more to do with luck rather than the standardisation approach. The laundry list of failures and the sad current state are evidence that luck is not a strategy and something different must be tried. I put this in the same category of failure as IPv6. The IETF got lucky with IPv4 and figured that "more of the same" will work. They didn't get lucky the second time. I wish I had the "political clout" to bang some heads together at these megacorps, make them sit down together and fix this. Realistically, I foresee another decade of 8-bit, SDR, sRGB images stretched incorrectly to whatever random gamut the $150 monitor of the recipient is capable of displaying.
- ksec 7y ago>"Technically open" doesn't help much if each of those formats is primarily pushed by one mega-corp, Then no Format is Open by your standard. Apple or Google refuse to support anything would instantly make that format not Open by your standard. And if Apple drop Jpeg, would Jpeg not be an open standard ? What you are describing is politics, nothing to do with the standards itself. >The only tool I found was Gimp That is the problem with the tools. If Gimp Dev decide to take side in the format battle and not support it properly, then is that the fault of a standard? >So then why isn't NetFlix working with the JPEG XL group to add the AV1 codec as one of the encoding options? Because it doesn't work like that. >Clearly, whatever they JPEG group is doing, it's not working. They are used in space other than the Web.
- jiggawatts 7y ago> What you are describing is politics, nothing to do with the standards itself. Standards are about convincing a large group of people to do something for the common good, sometimes going against their most direct best interests. Nearly a textbook definition of the word "politics". > They are used in space other than the Web. Yeah, the tiny, borderline non-existent space that is outside of: desktops, phones, tablets, web, email, collaboration, digital cameras, desktop publishing, or just about any mass-market use of computing you care to name that involves imaging. The only usage of a JPEG standard other than the original JPEG I'm aware of is JPEG 2000. It has some niche uses for digital movie distribution to cinemas. Not streaming, not cable. Cinemas. Only. According to Wikipedia, I missed a few uses: https://en.wikipedia.org/wiki/JPEG_2000#Applications https://en.wikipedia.org/wiki/JPEG_2000#Applications I suspect a few of those uses are actually out-of-date now and have been superseded by more modern codecs. Flip through that very short list and explain to me how the current "politics" of imaging standards bodies has succeeded, because I just don't see it.
- JyrkiAlakuijala 7y agoJPEG XL does better for small images if we talk about small as 32x32 pixels. It's header overhead is far less than anything else. JPEG XL's current encoder is focused on qualities 0.5 BPP and upwards. Current internet image usage averages at 2 to 3 BPP based on Chrome stats from June 2019. See https://www.spiedigitallibrary.org/conference-proceedings-of-spie/11137/111370K/JPEG-XL-next-generation-image-compression-architecture-and-coding-tools/10.1117/12.2529237.full?SSO=1 https://www.spiedigitallibrary.org/conference-proceedings-of... Figure 1. When you go to 0.1 BPP, every codec will look unacceptable, but the current encoder of JPEG XL looks worse than video codecs. We will likely be able to extend the scale of handling bad quality down to 0.1 to 0.25 BPP, but it definitely has not been a priority since we don't anticipate that users actually would use it for photographs. (When an image has a low noise level or less features, then we naturally can compress it down to 0.00x BPP with JPEG XL, too. The 0.5 BPP rule of thumb is for normal vacation photographs and selfies :-)