@fastidious@arrakis.netbros.com On the loss of quality on image processing / resizing… I think it might have something to do with the resampling that occurs during the resize operation. On the backend yarnd
we use the gift library for most processing (mostly just Resize()
and ResizetoFit()
). PNG itself is a lossless image format with selectable compression levels depending on output size and decode speed, so I think the culprit is the resampling…
yarnd
we use the gift library for most processing (mostly just Resize()
and ResizetoFit()
). PNG itself is a lossless image format with selectable compression levels depending on output size and decode speed, so I think the culprit is the resampling...
I’m not an expert though in resampling algorithms when it comes to resizing images. So I’m not really sure whether the Resampling we use gift.LanczosResampling
is the best choice here 🤔
yarnd
we use the gift library for most processing (mostly just Resize()
and ResizetoFit()
). PNG itself is a lossless image format with selectable compression levels depending on output size and decode speed, so I think the culprit is the resampling...
@fastidious@arrakis.netbros.com Sounda good đź‘Ś
yarnd
we use the gift library for most processing (mostly just Resize()
and ResizetoFit()
). PNG itself is a lossless image format with selectable compression levels depending on output size and decode speed, so I think the culprit is the resampling...
@fastidious@arrakis.netbros.com To be honest I’m not sure how even using an “original size” image and doing CSS size to fit or even on any app really doesn’t also suffer from loss of quality due to resampling. Resampling is a pretty common algorithm to apply to any image resizing I thought? 🤔
yarnd
we use the gift library for most processing (mostly just Resize()
and ResizetoFit()
). PNG itself is a lossless image format with selectable compression levels depending on output size and decode speed, so I think the culprit is the resampling...
@fastidious@arrakis.netbros.com Ok đź‘Ś