I currently want to target the old RPI 0 (and W) variants, but large animated gifs (30+ MB) sometimes fail to load. Honestly not sure if it's worth pursuing or just having some sort of file size limit in place.
Currently the gif loading works by loading the gif image data, and then the first time a frame is displayed compute what the new gif frame is. This keeps loading gifs somewhat fast.
Also, the current gif code uses too much memory. Not noticeable during development, but when you only have 1GB of RAM, it becomes very noticeable. Some thoughts:
Clear rawFrame data after gifData.ImagesData is populated
JarvyJ
commented
1 week ago
I currently want to target the old RPI 0 (and W) variants, but large animated gifs (30+ MB) sometimes fail to load. Honestly not sure if it's worth pursuing or just having some sort of file size limit in place.
Currently the gif loading works by loading the gif image data, and then the first time a frame is displayed compute what the new gif frame is. This keeps loading gifs somewhat fast.
Also, the current gif code uses too much memory. Not noticeable during development, but when you only have 1GB of RAM, it becomes very noticeable. Some thoughts:
rawFramedata aftergifData.ImagesDatais populated