5 ms·
> unbelievably better I don't know that this qualifies as unbelievable. This is just good marketing and spin. The image in that link is exploiting the fact t
by ajross 7y ago
> unbelievably better
I don't know that this qualifies as unbelievable. This is just good marketing and spin. The image in that link is exploiting the fact that modern codecs specify upsampling filters, so the HEVC half looks smoothly varying while JPEG can, per spec, only look pixelated when blown up like that.
There's absolutely no reason that thing couldn't have shown you a jpeg image rendered with bilinear filtering, which of course is what you'll see if you put that JPEG on a texture and scale it up using the GPU.
But it didn't, because it wanted to convince you how much "unbelievably" better HEVC is. Meh.
I mean, to be clear: HEVC is absolutely better, to the tune of almost a factor of two in byte size for the same subjective quality. Just not like this. If you've got a site where still images are a significant fraction of your bandwidth budget (and your bandwidth budget is a significant fraction of your budget budget) then this could help you. In practice... static content bandwidth is mostly a solved problem and no one cares, which is why we aren't using BPG.
- deleted 7y ago[deleted]
- kevin_thibedeau 7y agoFine detail is still better preserved where JPEG blows it away on low Q settings. A filter can't reconstruct that information.
- ajross 7y agoProbably, but that effect is subtle and not the "OMG THIS IS PIXELATED" nonsense the linked page is showing. I'm not saying BPG isn't better, I'm saying that link is ridiculous and doesn't capture the much more modest gains that it actually offers.
- PaulHoule 7y agoA few times I have looked at the possibility of switching from JPEG to another format for photo web sites and every time I have I've come to the conclusion that you can't really win. There are three benefits that one could get from reducing the file size: 1. Reduced storage cost 2. Reduced bandwidth cost 3. Better user experience In my models, storage cost matters a lot. You can't come out ahead here, however, if you still have to keep JPEG copies of all the images. Benefits in terms of 2 are real. Benefits in terms of 3 are hard to realize. Part of it is that adding any more parts to the system will cause problems for somebody somewhere. For instance, you can decompress a new image format with a Javascript polyfill, but is download+decompress really going to be faster for all users? Another problem is that much of the source material is already overcompressed JPEG so simply recompressing it with another format doesn't lead to a really improved experience. When I've done my own trials, and when I've looked closely at other people's trials, I don't see a revolutionary improvement. A scenario that I am interested in now is making desktop backgrounds from (often overcompressed) photos I find on the web. In these cases, JPEG artifacts look like hell when images are blown up, particularly when images have the sharp-cornered bokeh that you get when people take pictures with the kit lens. In that case I can accept a slow and expensive process to blow the image up and make a PNG, something like https://www.mathworks.com/help/images/jpeg-image-deblocking-using-deep-learning.html https://www.mathworks.com/help/images/jpeg-image-deblocking-... or https://github.com/nagadomi/waifu2x https://github.com/nagadomi/waifu2x The other approach I imagine is some kind of maximum entropy approach that minimizes the blocking artifacts.
- ebg13 7y ago> I don't know that this qualifies as unbelievable. This is just good marketing and spin. The image in that link is exploiting the fact that modern codecs specify upsampling filters, so the HEVC half looks smoothly varying while JPEG can, per spec, only look pixelated when blown up like that. I think you're focusing on the background? I agree that they should have masked the background out, but if you look instead at the first yellow segment of the rear wing near the body, there is clearly more available detail in the HEVC side.
- sp332 7y agoMaybe using https://github.com/google/knusperli https://github.com/google/knusperli as the JPEG decoder would give a fairer comparison?
- earenndil 7y agoHow come all of google's size-related software ends in 'li'? Zopfli, brotli, knusperli...
- trias 7y agoThey are developed in switzerland
- spider-mario 7y agoIt’s the Swiss German suffix for forming diminutives (as “booklet” is to “book” in English): https://en.wiktionary.org/wiki/-li#Alemannic_German https://en.wiktionary.org/wiki/-li#Alemannic_German And that’s because those codecs are developed at Google Zürich. Knusperli, Brotli, Brunsli… those are all pastries (Brot means “bread” in German).
- dahart 7y ago> There’s absolutely no reason that thing couldn’t have shown you a jpeg image rendered with bilinear filtering, which of course is what you’ll see if you put that JPEG on a texture and scale it up using the GPU. That’s not true, this particular JPEG will not look smooth on a GPU. The visible blocks are 8x8 pixels, not 1 pixel. The blocks would still be blocky because the compression has reduced them to only the DC component. This means the JPEG decode would still decode large blocks into texture memory and the GPU would still render large blocks with a slight blur between the 1 pixel borders of the 8 pixel blocks. > In practice... static content bandwidth is a mostly solved problem and no one cares, which is why we aren’t using BPG. I don’t believe that’s true either. I don’t know what you mean about bandwidth being “solved”, but more data is more data. If everyone could reduce their static images today by 2x without thinking, I’m pretty sure they would. I would on my sites if I could. The reason that BPG (or any other format!) isn’t yet being used is lack of browser support and tools and licensing and consensus, not because nobody cares about bandwidth. If what you said is true, then JPEG & PNG would never be replaced, but it’s already starting to happen.
- ajross 7y agoThe point was that, to first approximation, the internet is YouTube and Netflix. Static images are noise. And I'm sorry, but if that JPEG is showing artifacts like that it was simply miscompressed, likely deliberately. I repeat, there is absolutely no reason an image of there same byte count cannot look just fine on that screen. For goodness sake, just reduce the resolution if nothing else.
- naikrovek 7y agoThat picture at those dimensions and at that file size will show those artifacts. That's what the demonstration page is trying to show.
- ajross 7y agoBut that's completely artificial (and in the circumstances, outrageously spun!), because no one sane would compress a JPEG to a level where the macroblocks become flat blocks. You compress it at a resolution that captures the relevant detail, then display it with a filter that upsamples linearly. Nowhere on the internet is there an image that actually looks like this, because the "problem" being "solved" here doesn't exist in practice. I mean, it's true that IF you do that, that h.265 will save you by having control over filtering. But that's not a fair comparison, at all.