5 ms·
> 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 t
by 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.
- jacobolus 7y agoI think you are missing the point of the comparison. Nobody says that JPEG images like this are common. The point is rather that you could make a passable image of this bitrate using the better codec. It opens up a new level of compression not possible with JPEG. If you downsampled the JPEG enough to get the same bitrate without blocking artifacts, it would look like a blurry smear, which is better than a bunch of 8x8 flat blocks but not that much better. Maybe it would be worth including an additional JPEG downsampled-compressed-decompressed-upsampled view. You’d be able to see that jumping through those hoops doesn’t really give satisfactory results.
- ajross 7y ago> The point is rather that you could make a passable image of this bitrate using the better codec. It opens up a new level of compression not possible with JPEG. This is simply not correct. Anyone can get a passable image with that bit size. You're trying to stipulate "image pixel size" as some kind of inviolate thing, when it's not in reality. In reality, web content authors don't do insane things with their compression settings (I mean seriously: how would you even produce this? Standard conversion tools, for obvious reasons, will never emit an image like this). This isn't a real argument. This is cheating. > it would look like a blurry smear, Assuming facts not in evidence. The image in h.265 is plenty smeary already, FWIW. I think we both know that if this were true, the spin in the link would have done that instead of cheating with macroblock resolution. But in fact the blurry smear looks just fine, so they had to cheat.
- dahart 7y agoThe JPEG was compressed to death deliberately, yes. That's the point of the comparison; for the same (tiny) data size BPG gives you a clearly better result. BPG is workable in situations where JPEG isn't. > For goodness sake, just reduce the resolution if nothing else. Reducing the resolution would not work and is not the same thing. You would still get 8x8 DC blocks in a smaller JPEG at the same compression rate, and higher detail in the BPG. The BPG is provably better than the JPEG, and since you already know that and talked about it above, I'm a little confused by your argument.
- ZeroGravitas 7y agoI think there often is a point when reducing the bitrate further while keeping the same resolution is a worse choice than dropping the resolution. I believe one of the tricks of AV1 is to internalise this trade-off. More generally, doing visual comparisons of codecs is full of traps. Since quality often falls off rapidly at a certain point it's possible to show your codec off by choosing the exact point to compare to maximise the difference. This is almost certainly the case if you're comparing against jpeg and it's starting to totally fall apart. It's not that it doesn't correctly show that one is worse than the other but it's probably not a good visual reflection of the true scale of the difference any more than ramping up the bitrate until everyone would think they are indistinguishable.
- dahart 7y agoSure, yes, but the comparison in question isn't the only comparison, it's just one of many. Letting people see the difference visually for themselves is more tangible and less questionable that putting up two file size numbers and claiming they're equal quality. And if you think about it, it similarly wouldn't completely be fair to BPG to turn up the quality so that the JPEG looked reasonably good, because the BPG file would be in the range of diminishing returns per byte. It is fair to point out that JPEG falls apart below a certain compression threshold while BPG doesn't, even if it's a little bit apples to oranges. I prefer the way @enriquito said it https://news.ycombinator.com/item?id=20419900 https://news.ycombinator.com/item?id=20419900 but I disagree with the hyperbolic claims in this thread that this comparison is outrageous or complete spin or cheating. It's a data point that has some actual merit, and BTW happens to agree with the other data points we have.