09-17-2020, 03:40 AM
(This post was last modified: 09-17-2020, 03:42 AM by Miss Sissy Princess.)
(09-17-2020, 02:39 AM)Tim Curtis Wrote: I could see where the "bypass" option would prolly be better than offering "high res" sizes that would likely result in worse image quality and performance due to downsampling via PHP routines, and mislead users into thinking that the higher resolutions would improve thumb qual.
Maybe there is a misunderstanding about what happens when an image is downsampled to a lower resolution. This operation removes a lot of pixels and to compensate for the pixel loss the algorithms that perform downsampling perform tricks to make the resulting smaller image look decent to-the-eye. It works to a point.
The "bypass" option would leave the image resampling up to the Browser which prolly does a pretty good job considering that Browser image handling is super ultra optimized.
If most all of my artwork is 1000x1000 or better, how will I get worse image quality with 800 pixel thumbnails than with 400?
At some point, I'd let dumb users do dumb things rather than tying the hands of users who understand that it's a bad thing to go from 320x320 album art upsampled to 1000x1000 and then downsampled to 400x400 for display on a laptop screen.
My concern with a bypass option is that it might move massively more data than necessary when someone has really large album artwork.
How about an option to set the maximum thumbnail size (in pixels)? The album art goes in at the native size if it is smaller than the selected maximum; otherwise it gets downsampled to the maximum size.
Cheers,
Miss Sissy Princess
Miss Sissy Princess