6 ms·
You know, I don't really personally care if the successor to JPEG is AVIF (based on AV1), HEIF (based on h.265, pushed by Apple), or WebP (based on V8). I just
by crazygringo 6y ago
You know, I don't really personally care if the successor to JPEG is AVIF (based on AV1), HEIF (based on h.265, pushed by Apple), or WebP (based on V8).
I just wish we could standardize on one. Trying to figure out which browsers support which, which way the winds are blowing, etc. keeps me sticking to JPEG.
It seems like h.265 "won" as the most widely supported new video codec with hardware acceleration. Yet confusingly, HEIF has not ridden on its coattails.
Where is this all going? And will we even have settled on a single successor before next-gen codecs like h.266 disrupt it all again?
- freeone3000 6y agoHEIF has the problem of being patent-encumbered. Cisco has graciously given out decoding licenses, but encoding is murkier. Luckily, hardware acceleration usually isn't required for still images, so you can encode to whatever, as browsers can decode them all just fine.
- CharlesW 6y agoWebP and AV1 are patent-encumbered as well. Google provides a royalty-free patent license, which can be revoked. https://github.com/ImageMagick/webp/blob/main/PATENTS https://github.com/ImageMagick/webp/blob/main/PATENTS AOMedia has a "royalty-free patent licensing commitment from all AOMedia members", but that doesn't mean that AV1 users won't have to pay to license patents from non-members. http://aomedia.org/press%20releases/the-alliance-for-open-media-statement/ http://aomedia.org/press%20releases/the-alliance-for-open-me...
- gruez 6y ago>which can be revoked. or more precisely, irrevocable except if you try to sue google for patent infringement.
- ampdepolymerase 6y agoAh, the good ole' React license trick. Where is the mob outrage? Or are web developers so fickle to not care outside of JavaScript frameworks? Video encoding standards are much lower on the stack and the potential for damage is much greater compared to a website.
- kmeisthax 6y agoReciprocal patent grants are not an uncommon or bad licensing practice. The only problem was that Facebook was doing it, which raises suspicion purely because Facebook is Facebook and Facebook is bad.
- TD-Linux 6y agoThe difference between the AOM license and React license is that the React license terminates if you sue Facebook for any patent infringement, whereas the AOM license only terminates if you sue an AOM user for an AV1-related patent.
- deleted 6y ago[deleted]
- alex_young 6y agohttp://aomedia.org/membership/members/ http://aomedia.org/membership/members/ Are you suggesting that the members (including many tech giants) are overlooking some patents held by others which will then be used to extract a price ruining the format they have all been pushing? This seems somewhat unlikely right?
- CharlesW 6y ago> Are you suggesting that the members (including many tech giants) are overlooking some patents held by others which will then be used to extract a price ruining the format they have all been pushing? They're definitely not overlooking it — the AOMedia statement I linked to above was a direct response to the collected patent claims by non-members, which number over 1,000 so far.
- kmeisthax 6y agoRoyalty-free blanket patent licensing is compatible with Free Software and should be considered the same as being unpatented. Even if it's conditioned on a grant of reciprocality. It's only when patent holders start demanding money (or worse, withholding licenses altogether) that it becomes a problem for us.
- ksec 6y ago>Royalty-free blanket patent licensing is compatible with Free Software and should be considered the same as being unpatented. If I remember correctly, Firefox at one point refuse to include h.264 decoder even if they granted royalty free usage because the codec is considered patent encumbered.
- kmeisthax 6y agoThat's why the word "blanket" is included there - if you just give Firefox and Firefox alone a royalty-free H.264 license, that's not compatible with Free Software, you can't legally fork it without getting another patent license that will almost certainly cost money. AFAIK the thing Firefox refused to accept wound up happening anyway. Cisco released a nominally BSD-licensed H.264 decoder and agreed to pay the maximum royalty possible to MPEG-LA. If you use their specific codec binaries, then you're covered under the patent license. So Mozilla wound up writing a new plugin framework specifically to host OpenH264 so that WebRTC could have a standard codec.
- CharlesW 6y ago> Royalty-free blanket patent licensing is compatible with Free Software and should be considered the same as being unpatented. I agree 100%, and am not the person arguing that patent-encumbered technology is incompatible with free software or bad in any way. The point of my unpopular post is simply that making a decision based on whether a technology is patent-encumbered makes zero sense in this case since all of them are.
- freeone3000 6y agoThe terms of the patent grant matter. AV1 and WebP are free-to-use. H.265 has a fee per encoder and decoder.
- pezezin 6y agoI really hope that the single successor will be JPEG-XL. It's much better format for still pictures (faster encoding and decoding, higher quality, almost unlimited picture size, layers, color channels, etc), and the ability to losslessly recompress existing JPEGs is huge.
- xeeeeeeeeeeenu 6y ago>You know, I don't really personally care if the successor to JPEG is AVIF (based on AV1), HEIF (based on h.265, pushed by Apple), or WebP (based on V8). You should care because those formats aren't equivalent. In many important cases, WebP performs worse than the good old JPEG[1]. It's popular mainly because of Google's brand and cargo culting. HEIF is doomed because it isn't royalty-free. In my opinion, JPEG XL is the most interesting new format. Cloudinary published many blogposts comparing JPEG XL to the other formats, for example: [2][3]. I really recommend reading them. BTW, Chromium has recently added support for JPEG XL decoding[4]. It's currently hidden behind a feature flag. [1] - In medium to high BPP photographic images (which, I believe, is the most common use of lossy image compression) and in generation loss tests. [2] - https://cloudinary.com/blog/time_for_next_gen_codecs_to_dethrone_jpeg https://cloudinary.com/blog/time_for_next_gen_codecs_to_deth... [3] - https://cloudinary.com/blog/how_jpeg_xl_compares_to_other_image_codecs https://cloudinary.com/blog/how_jpeg_xl_compares_to_other_im... [4] - https://chromium.googlesource.com/chromium/src/+/043d32542213b601bf5852f6cd5950c949f411fa https://chromium.googlesource.com/chromium/src/+/043d3254221...
- jaffathecake 6y agoWe added a preview of the JPEG-XL encoder to https://squoosh.app https://squoosh.app (and WebPv2) so you can try it with your own images. In my experience, AVIF tends to outperform JXL in most web use-cases. However, for cases where the image should be really high quality (where the image is core content, like Flickr or Unsplash), the winner is less clear. Also, at those kinds of sizes, JPEG-XL's progressive rendering becomes an important factor. But seriously, there's so much hype around these image formats, the best thing to do is to test it with your own images and your own eyes.
- bscphil 6y ago> AVIF tends to outperform JXL in most web use-cases Matches my experience pretty well. AVIF can look quite good (for web purposes) at very low bitrates, while JXL falls apart. (JXL actually has two different modes of operation - modular mode is better at lower bitrates, but it's not considered to be JXL's main mode of operation.) JPEG-XL seems to be designed to replace JPEG for high quality photographic images, and in my experience it's fantastic at this. I see much better results at higher bitrates (compared to AVIF), and JXL can also losslessly compress JPEGs to a smaller size. There's a comparison between AVIF and JPEG-XL here https://afontenot.github.io/image-formats-comparison https://afontenot.github.io/image-formats-comparison although JPEG-XL is rather fast moving target at the moment and the comparison hasn't been updated in quite a few months.
- jaffathecake 6y agoVideo hardware acceleration tends to be optimised for one stream, one frame at a time. It doesn't often translate well to loading multiple images of different dimensions & settings in parallel.
- zokier 6y ago> And will we even have settled on a single successor before next-gen codecs like h.266 disrupt it all again? I don't think there is great risk of getting disrupted by next-gen codecs because the gen-to-gen improvements for stills will be so marginal, especially compared to the improvement from jpeg to avif/heif. So there is little motivation to iterate there, especially considering the computational costs. I see whatever we settle on will probably last next 20 years. So taking few years to settle feels fine in my books
- Goz3rr 6y ago> It seems like h.265 "won" as the most widely supported new video codec with hardware acceleration. Unless I'm missing something, AV1 is supported in Chrome, Edge, and Firefox while h.265 is only supported in Safari? How is that winning? https://caniuse.com/hevc https://caniuse.com/hevc https://caniuse.com/av1 https://caniuse.com/av1
- afavour 6y agoThe "with hardware acceleration" part is what's missing there. Very important for mobile devices.
- tootie 6y agoA general approach to content type negotiation and transcoding would be nice too.
- eplanit 6y agoExactly. The sample image in TFA won't display in FF on my android phone. A new road to hoe for avif
- XCSme 6y agoI think that by the time we decide on the next image compression format the ML super-resolution will become so popular and easy to use that browsers and other devices will have an "upscaler" implemented in them.