Re:Making Photos Smaller Without Quality Loss
by ge96 on Saturday June 10, 2017 @05:53PM
(#14529395)
Sorry I wasn't implying blur was a part of progressive loading. I kept hearing about progressive loading but didn't understand what it was.
I used the blur-up method, low res small file blurred, replace with high res full version without blur.
Thanks for the info. Is it right to assume any photo with a .jpg extension does this by default? I'll go hit the links.
Re:Making Photos Smaller Without Quality Loss
by WhiteOwlLion on Monday June 05, 2017 @05:42PM
(#14492416)
If we had progressive JPEG for all JPEGs, low bandwidth networks could request a percentage of the file and save on total data needed to render a page. This could be useful for areas where 2G may be the norm.
Re:Making Photos Smaller Without Quality Loss
by Negitivefrags on Monday June 05, 2017 @11:05PM
(#14494404)
In this age of devices with different DPI and pinch-to-zoom it would be nice if the browser would only get as many progressive levels as required for the current display resolution of the image.
Re:Making Photos Smaller Without Quality Loss
by jharger on Monday June 05, 2017 @06:43PM
(#14492955)
I remember some dial-up ISPs doing almost this a few years ago. A friend of mine lived in a rural area, and his dialup provider would show a low-res version of the image. If he clicked on the image, it would load the full version. I think that they would hijack the webpage and do their special image cache thing on a proxy server. It was a really weird experience, but also kind of cool.
A Python library for manipulating image, like ImageMagick and the like.
> so loading a small version spread out to full size with blur, then in the background loading full size copy to replace blurred small image, that is not progressive loading…?
Progressive JPEG is closer to refinement of previous blocks, it doesn't "add blur", it starts with smaller less precise blocks then refines them. Progressive jpeg actually tends to be smaller than non-progressive (as opposed to e.g. progressive PNG)
> Edit: also is progressive loading something that happens once or does a script have to do that every time the photo is pulled?
There is no script, progressive JPEG is part of the core spec.