-
Notifications
You must be signed in to change notification settings - Fork 125
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature-complete APNG optimization #551
Comments
renamed in light of #551; now supports APNG but the support is nearly useless :( [thanks for it anywy tho] |
@ctrlcctrlv I think you meant #79 → #511 |
Groundwork has been done to support APNGs (see #511), but the changes were not yet published in a release, so you have to build OxiPNG from source to use them. Do those changes satisfy your needs, @ctrlcctrlv? If not, why do you find that support "nearly useless"? |
fdAT is likewise compressible via the same way* IDAT is compressed so no, probably why @andrews05 wrote they were “not sure if it's something that should actually be added” :-) * sort of. |
@AlexTMjugador Even in #511, @andrews05 says average savings is <1%, so much room for improvement. I think the idea here is to meet/best |
Alright, that's fair. I'm renaming this issue to more clearly state what it asks for 😄 |
exactly. i started thinking about how to do it as well. in theory—
in order to make a well-supported APNG, it's quite important to alternate fcTL and fdAT, as earlier versions of the spec said no chunk may come between an fcTL and its fdAT. what i think this means is we can use the same code as does the main loop just with &fdat[4:]. likely |
The text was updated successfully, but these errors were encountered: