Fill identical pixels with transparency in subsequent frames when saving GIF #7568
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
radarhere
force-pushed
the
gif_transparency
branch
from
7bfeb70 to
b47ad8f
Compare
radarhere
force-pushed
the
gif_transparency
branch
from
b47ad8f to
55c5587
Compare
This was referenced Dec 24, 2023
|
Could this be causing the |
|
Yes, this would be the cause - but rather than just undoing this change, it would be better to adjust it, to both reduce filesize and to fix your problem. The quickest way of understanding how to do that would be for you to post a self-contained example of your problem in that issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When saving multiple GIF frames, Pillow trims identical edges of each new frame. This PR goes further, setting the pixels that are not new in the next frame as transparent if Pillow is optimizing. If there is no transparency, try and allocate one.
I started work on this after seeing #6832 (comment). If I remove
optimize=Falsefrom that code, then without this change the file size is 21.5mb. With this change, the file size is 8.1mb.For a less dramatic example, the output of #617 (comment) is reduced from 408kb to 345kb
Because the only difference in output should be filesize, there are no new tests to demonstrate correctness. I have added a test to cover an exception caught if trying to add transparency when there is no room in the frame.