(Optional) Can you provide a link to the item, model, or project in question?
N/A
(Optional) Do you have any sample code you can provide?
I am loading assets via datocmst React package and Image component. I donāt think itās a problem in the image component, as the above URL doesnāt open directly as wellā¦
Are you saying that these animated GIFs were working correctly and then stopped? With the same params?
I see your point and it makes sense to me, I was just checking if you could fix quickly your problem. Meanwhile Iām going to contact Imgix as I think it should work with auto=format.
@mat_jack1 just for your reference, the mentioned GIF file (original file in assets) is not that big ā 389.76KB. If it helps here is direct link to this asset inside DatoCMS.
@primoz.rome, for these images, should they ever exceed dpr > 1 ? Youāre just enlarging them past their native size at that point, which causes pixelation or upsampling artifacts anyway. Might be better to export them at a higher native resolution and downsample to DPRs < 1 instead?
Yes, the dpr is the way that we use to manage responsive images, so itās automatically added.
A couple of ideas for you to try out:
can you consider using w: 1280 ? The original GIF looks 1280px wide, this might be enough to prevent the dpr=4 to kick in.
you can try using auto: format, compress, it might help reduce the size and avoid the timeout.
From Imgix they say that the problem is the rendering of the GIF with dpr=4 which makes a big image that times out. The compress can help and also avoid the dpr=4 to kick in. Let me know if these two options work for you.
@mat_jack1 This almost seems like a bug on our part to me. I wonder if we should add that to our own image component/default Imgix queries too? DPR makes sense when an image is scaled down from its native size to fit a container, in which case DPR > 1 can improve clarity on retina devices. But when we accidentally use it to scale an image past beyond its native size, at best it will look bad (upscaled), at worst it will cause an Imgix timeout like here. Itās what Imgix suggests in their responsive images tutorial too. I think Iāve seen similar situations with other customers too, but at the time I didnāt realize we were the ones doing the DPR calculations for them. My mistake!