Repository navigation
Do not clip I;16 values when comparing APNG frames - #10336
Merged
radarhere merged 7 commits intoOct 28, 2026
Merged
Conversation
Contributor
Author
|
The Benchmark and debian-13-trixie-x86 failures also happen on main, so my change does not cause them. |
Member
|
I've created lazerg#9 with a suggestion. |
Contributor
Author
|
Thanks, I merged it. I also added |
This file contains hidden or 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
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.
Fixes #10329
When saving an I;16 APNG, frames were compared after converting to RGBA, which clips everything above 255. So frames that only differed above 255 were merged, or had their changed region cropped too small. For I;16 and I;16B, the raw pixel bytes are now compared as well.