From: James Zern via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: James Zern <jzern@google.com>
Subject: Re: [FFmpeg-devel] [RFC] webp decoding
Date: Thu, 26 Jun 2025 10:33:43 -0700
Message-ID: <mailman.4627.1750959243.1384.ffmpeg-devel@ffmpeg.org> (raw)
In-Reply-To: <CA+anqdzCPdA3z2g3zZS_eCU1niXmNf5q9B7bs09gTTLNa1bc5w@mail.gmail.com>
[-- Attachment #1: Type: message/rfc822, Size: 4337 bytes --]
From: James Zern <jzern@google.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [RFC] webp decoding
Date: Thu, 26 Jun 2025 10:33:43 -0700
Message-ID: <CABWgkX+SMJZvGsQez1RhnR_BUXyVfdSt=UURZEJCkEt_pyHBsA@mail.gmail.com>
On Thu, Jun 26, 2025 at 12:00 AM Hendrik Leppkes
<h.leppkes-at-gmail.com@ffmpeg.org> wrote:
>
> On Thu, Jun 26, 2025 at 2:58 AM Michael Niedermayer
> <michael@niedermayer.cc> wrote:
> >
> > Hi
> >
> > some people use webp apparently, and we have no decoder
> >
>
> libavcodec/webp.c is a decoder.
>
The missing piece is animated webp demuxing/decoding:
[webp @ 0x56227253be80] skipping unsupported chunk: ANIM
[webp @ 0x56227253be80] skipping unsupported chunk: ANMF
Last message repeated 30 times
[webp @ 0x56227253be80] skipping unsupported chunk: XMP
[webp @ 0x56227253be80] image data not found
Thilo's implementation worked pretty well from what I remember of my
earlier testing. There may be some corner cases that behaved
differently from libwebp's animated decoder, but I don't remember the
details. If nothing else, functionally speaking, it seemed like a good
place to start.
[-- Attachment #2: Type: text/plain, Size: 251 bytes --]
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2025-06-26 17:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-26 0:58 Michael Niedermayer
2025-06-26 7:00 ` Hendrik Leppkes
2025-06-26 17:33 ` James Zern via ffmpeg-devel [this message]
2025-06-26 17:37 ` Michael Niedermayer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=mailman.4627.1750959243.1384.ffmpeg-devel@ffmpeg.org \
--to=ffmpeg-devel@ffmpeg.org \
--cc=jzern@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git