Re:BPG Image Format
by jjcm on Friday October 02, 2020 @07:52PM
(#24668230)
Bellard is obviously a technical genius. I have no doubt that BPG is competitive on a technical aspect. Politically though AV1 is looking like it has the best chance of unseating jpg. Near universal buy-in by browsers/OSes/hardware makers, hardware acceleration starting to roll out, and patent free.
Re:BPG Image Format
by yarg on Friday October 02, 2020 @09:24PM
(#24668712)
Will it necessarily matter though?
In a WASM context format starts to matter less since content in arbitrary codecs can be downloaded and decoded.
There are some concerns:
Non-native support requires non-static pages - even for something that will always appear to be the same, things like noscript will kill the page;
Hardware acceleration will need to be done in general terms - something like WebGPU will help, but it will still be less efficient than hardware acceleration (and that could be a problem for mobile).
Re:BPG Image Format
by gigel82 on Friday October 02, 2020 @09:35PM
(#24668764)
Also CORS: you can hotlink images from everywhere, but if you try to actually put those bits in a Buffer (as you'd need with BPG) the browser won't let you unless CORS is properly set up for the specific source-target URLs (affects things like image CDNs and so on).
Re:BPG Image Format
by mumblerino on Friday October 02, 2020 @11:23PM
(#24669256)
The point of using a format over another, given the availability, is to gain performance.
You're suggesting to load a whole new parser, parse images at a higher level than browsers can (i.e. slower and with less concurrency), and make `<img>` a whole lot harder to manage.
That's not worth it at all unless the savings are substantial (say BMP vs JPEG)
Re:BPG Image Format
by mumblerino on Saturday October 03, 2020 @08:27PM
(#24675751)
> Performance is not a factor in this.
What a completely ridiculous statement. Why else would anyone choose BGP if not for performance (i.e. download speed)? The choice to use BGP over a plain old JPG would be made specifically by people who do care.
Re:BPG Image Format
by tjoff on Saturday October 03, 2020 @04:41AM
(#24670558)
If that is true then the web does not care about SEO. And quite obviously it isn't weighted particularly hard at all (probably because there wouldn't be anything left).
edit:
Case in point, except for google.com (which itself has a terrible score of 62) I can't even find out a single google service that isn't in the reds on the pagespeed index.
Re:BPG Image Format
by yarg on Saturday October 03, 2020 @08:35PM
(#24675782)
No, not for every page - it will very much be use case dependent.
However, it does present a viable path to the introduction of new codecs independent of the bogged up process that still has us using GIF and JPEG despite the fact that they've been known for years to be shite.
Also, WASM supports a binary form, so you can skip parsing.
Re:BPG Image Format
by pornel on Saturday October 03, 2020 @12:59PM
(#24673253)
Yes. BPG (and H.265 it uses) may be technically excellent, but H.265 is a commercial patent-encumbered codec. Patents cover any implementation, even free and open-source ones, so in countries that allow software patents BPG is illegal to use without a patent license for H.265.
"Hope you're not worth suing" may be an OK strategy for many people using BPG on their websites, but it's a blocker for wide adoption of the format. The licensing situation is so bad, that the industry went all behind the AV1 alternative, and the AVIF format rides that wave.
Re:BPG Image Format
by masklinn on Saturday October 03, 2020 @03:19AM
(#24670256)
BPG has never been very popular, though the “official” variant (heif which is the same idea by the MPEG) is supported by windows, macOS, iOS and Android.
Re:BPG Image Format
by viraptor on Friday October 02, 2020 @07:55PM
(#24668247)
> 14bit (...) It gives a higher dynamic range (which is important for cameras and new displays) and a slightly better compression ratio (because there are less rounding errors in the decoder).
Re:BPG Image Format
by m45t3r on Friday October 02, 2020 @10:41PM
(#24669050)
Yeah, I remember reading years ago a paper explaining the same for H.264 and why 10-bit encoding matters (even for 8-bit content). It was fascinating reason, btw.
AFAIK, there is also less banding issues even in 8-bit content, and the filesize is generally smaller too. The biggest reason against its usage is more computational power, though.
Re:BPG Image Format
by touchpadder on Friday October 02, 2020 @08:31PM
(#24668433)
to wait until BPG becomes an open format would take a lifetime. I've been waiting for years now. Fortunately webp is now widely adopted so no need for waiting for bpg anymore
Re:BPG Image Format
by rootw0rm on Saturday October 03, 2020 @02:57AM
(#24670167)
once upon a time i designed an automated framework to attempt to brute force optimal x264 encoder settings for a small library of sample clips. i used lossless BPG for storing select keyframes from various test runs before analysis. i soon learned that having software try to decide the quality of one image versus another is not a terribly easy problem to solve. thanks for the trip down memory lane =)
> According to Bellard's site BPG may be covered by some of the patents on HEVC, but any device licensed to support HEVC will also be covered for BPG. Patent issues may prevent JPEG replacement by BPG despite BPG's better technical performance.
Re:BPG Image Format
by kernelbugs on Saturday October 03, 2020 @08:13AM
(#24671448)
FLIF was superseded by FUIF and then by JPEG XL, but it hasn't been fully integrated. JPEG XL has parallel decode and uses MAANS entropy encoding instead of MANIAC, which results is slightly less compression for some situations (but faster decode). That said, I certainly agree that JPEG XL is already very impressive and hopefully the next majorly supported image format.
Lots of other discussion on this though: https://hn.algolia.com/?q=bpg+bellard
Royalty Free.
Purely from a Web Image usage perspective, Jpeg XL is very competitive in terms of features and performance. Also Royalty free.
There are some concerns:
Non-native support requires non-static pages - even for something that will always appear to be the same, things like noscript will kill the page;
Hardware acceleration will need to be done in general terms - something like WebGPU will help, but it will still be less efficient than hardware acceleration (and that could be a problem for mobile).
You're suggesting to load a whole new parser, parse images at a higher level than browsers can (i.e. slower and with less concurrency), and make `<img>` a whole lot harder to manage.
That's not worth it at all unless the savings are substantial (say BMP vs JPEG)
Performance is not a factor in this.
What a completely ridiculous statement. Why else would anyone choose BGP if not for performance (i.e. download speed)? The choice to use BGP over a plain old JPG would be made specifically by people who do care.
> Performance is not a factor in this.
If you care about SEO, it does. Check Google's pagespeed test.
edit: Case in point, except for google.com (which itself has a terrible score of 62) I can't even find out a single google service that isn't in the reds on the pagespeed index.
Even when it decided to load the mobile version.
Besides, do you really want to download and parse a codec for every page?
However, it does present a viable path to the introduction of new codecs independent of the bogged up process that still has us using GIF and JPEG despite the fact that they've been known for years to be shite.
Also, WASM supports a binary form, so you can skip parsing.
https://jpeg.org/jpegxl/
https://gitlab.com/wg1/jpeg-xl
https://aomediacodec.github.io/av1-avif/
https://github.com/AOMediaCodec/libavif
https://caniuse.com/avif
"Hope you're not worth suing" may be an OK strategy for many people using BPG on their websites, but it's a blocker for wide adoption of the format. The licensing situation is so bad, that the industry went all behind the AV1 alternative, and the AVIF format rides that wave.
https://aomedia.org/
Discussion 2 years ago: https://news.ycombinator.com/item?id=17587684
Discussion 6 years ago: https://news.ycombinator.com/item?id=8704629
Those who can be called genius are few in the world, but Facrice Bellard is certainly among them.
That's clever and a bit counterintuitive.
AFAIK, there is also less banding issues even in 8-bit content, and the filesize is generally smaller too. The biggest reason against its usage is more computational power, though.
> According to Bellard's site BPG may be covered by some of the patents on HEVC, but any device licensed to support HEVC will also be covered for BPG. Patent issues may prevent JPEG replacement by BPG despite BPG's better technical performance.
So it sounds like you’re ultimately correct.
http://flif.info/index.html