On Tue, Apr 21, 2026 at 5:24 AM Timo Rothenpieler via ffmpeg-devel <[email protected]> wrote: > > > > On 21/04/2026 06:39, Peter Xia via ffmpeg-devel wrote: > > > > > >> On Apr 16, 2026, at 7:40 PM, Peter Xia <[email protected]> wrote: > >> > >> > >> > >>> On Apr 16, 2026, at 11:05 AM, James Zern <[email protected]> wrote: > >>> > >>> On Thu, Apr 16, 2026 at 3:36 AM Peter Xia via ffmpeg-devel > >>> <[email protected]> wrote: > >>>> > >>>> Adds support for extended file format specified in > >>>> https://developers.google.com/speed/webp/docs/riff_container > >>>> which animated webp uses. > >>>> > >>>> Fixes: #4907 > >>>> > >>>> Signed-off-by: Peter Xia <[email protected]> > >>>> --- > >>>> libavcodec/webp.c | 764 +++++++++++++++++++++++++++++++++++++++++----- > >>>> 1 file changed, 692 insertions(+), 72 deletions(-) > >>>> > >>> > >>> There have been a few attempts at this. I think most recently: > >>> - https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20568 > >>> - https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20565 > >>> > >>> There has been debate in earlier threads about which approach is best. > >> > >> > >> This is actually my 2nd attempt as well. Last year I sent one using > >> libwebp and I got the impression that a non-libwebp implementation is > >> preferred. > > > > Friendly ping on this. Would love to see this in ffmpeg - it’s been long > > overdue. > > You might want to submit it as PR on code.ffmpeg.org for more attention. > Though the few people who can properly review this are quite busy > already either way. >
Note that an updated alternative is here: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/22975 _______________________________________________ ffmpeg-devel mailing list -- [email protected] To unsubscribe send an email to [email protected]
