Open ghost opened 7 years ago
Externally, FLIF animations have fully refreshed full frames only. Internally, there are some transformations to optimize that:
With these primitives you can probably do a more or less gapless conversion from WebP or APNG to FLIF (using only rectangular FrameShapes for example). The other way around will be harder since these transformations have no complete counterpart in those other formats.
I wonder how the animation itself is compressed, is each frame decoded individually? Because in most animations frames are similar to each other and therefore compression should be better if the difference between a frame and it's previous frame are encoded instead of encoding every frame individually, it's similar to what you suggest with FrameLoopback but there you only mention replacing pixels whole, not adding(/modifying) them..
I working on gapless (or less gaps) conversion of WebP to APNG. Blend is blend, dispose is dispose, RGB is RGB (in future), RGBA is RGBA, ICC is ICC (future)...
I want to know, FLIF supports blending and dispose, and what modes supported?