IIRC, the risk is that, unless one successfully returns from WebPAnimEncoderAssemble(), the internal mux_ to be exposed is in an
unfinished state. In particular (anim_encode.c:1559), the final canvas size is not finalized. Surfacing this unfinished object could be
doable, but risky. Another option would be to add loop_count, EXIF/XMP/ICC to the anim_options, so that they can be used during
WebPAnimEncoderAssemble() without having to expose any internal object.
Note that re-muxing is not a heavy operation, just clutter code that could be avoided, agreed.
You received this message because you are subscribed to the Google Groups "WebP Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to webp-discuss...@webmproject.org.
To view this discussion on the web visit https://groups.google.com/a/webmproject.org/d/msgid/webp-discuss/701c5abd-a17f-4d77-8222-69649deaa57an%40webmproject.org.