You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It appears that a non-interlaced 64x64 GIF can be decoded by AnimatedGIFs set with a smaller max size (definitely 64x32, possibly 32x32). Interlaced GIFs have issues. Can the interlaced code be improved to throw out the extra pixels in a larger GIF?
The text was updated successfully, but these errors were encountered:
So, when I display on neomatrix, decoding of a gif bigger than my display area works fine, and then I have this offset to tell it what part of it to display: https://github.com/marcmerlin/AnimatedGIFs/blob/master/neomatrix_config.h#L87
Sure, a bit of CPU time is used to decode more GIF surface than can be displayed, but compared to the 36ms taken by a 1024 neopixel screen redraw, that CPU time doesn't seem that important.
It appears that a non-interlaced 64x64 GIF can be decoded by AnimatedGIFs set with a smaller max size (definitely 64x32, possibly 32x32). Interlaced GIFs have issues. Can the interlaced code be improved to throw out the extra pixels in a larger GIF?
The text was updated successfully, but these errors were encountered: