Almost everyove knows that JPEG files can be encoded to enable several progressive steps of rendering, so that the incomplete file on its early stages of downloading is seen as blurry.When the information of luminosity comes before the colors, such early image can also be decoded as gray or greenish (see the attached PNG; see also https://cloudinary.com/blog/progressive_jpegs_and_green_martians for the explanation). Modern versions of web browsers actually avoid this weird colours by suppressing decoding until both colour components arrive from the Web.When a JPEG is not progressive, it is designed to render from top to bottom.All that makes me think once again about the AVIF files.There are experiments of making them progressive (you can run “avifenc” with “--progressive”), but by default an AVIF is so much non-progressive that it does not render (even from top to bottom) until fully downloaded.But what if an incomplete AVIF were, in fact, rendered? What would we see then?Would the pixels come in the same “from top to bottom” order, but in blocks of different sizes?Would the pixels come in weird colours because the chroma comes after the luma?Or is that 100% not possible because some crucial information (like some dictionary for the decoder) is intentionally put near the ending of the file and all of the earlier pixels are just random data noise without it?
>>106872911>All that makes me think once again about the AVIF files.Are you, by chance, a femboy?
>>106872911Interpolating frames would be million times heavier and would require external application. Encoded stream is compressed and why it's efficient - it's the same as an archive. If you mess up something in between it'll corrupt.
>>106872911Boomer, these days we have thumbnails and then use AI to upscale it as a preview.
>>106872911It would depend on image tiling implementation. If 100KB 4K res AVIF images are too brutal of a payload for our curry friends then it's possible that websites would reduce tile sizes and break up that 4K 100KB AVIF beast into 30 ~3KB 512x512 individual images and load those. I assume these would then load from top to bottom in a 56kbps internet connection.Other than that AVIF's unusually good perceptual quality at 0.1 to 0.2 BPP makes progressive rendering obsolete even at 1Mbps especially if the image res is more reasonable like 720p which most blogs would want to use anyway.
