From: Osmo Hyttinen <osmo.hyttinen-at-gmail.com@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Subject: [FFmpeg-devel] Status of animated WebP decoding support (ticket #4907; patches from 2024/2025)
Date: Mon, 16 Jun 2025 13:39:35 +0300
Message-ID: <CAPHZS6n=g-UJAF5fXLh6PqMkVo7aZG0C=nfMnJP5M8qWyOoEDA@mail.gmail.com> (raw)
Hello FFmpeg developers!
Does anyone know the status of the animated WebP decoding support?
I found two independent efforts tackling this issue:
Of what I perceive as the main effort, the last thread I was able
to find from the archives was [PATCH 0/8..8/8 v13 WIP] on June 2024,
https://ffmpeg.org/pipermail/ffmpeg-devel/2024-June/330023.html
Separately, the long-standing encode-only asymmetry ticket (#4907,
opened October 2015) has in its comments a newer, simpler patch that
makes libwebp also able to decode instead of just encoding.
The latest activity of that is this [PATCH v2] on April 4th 2025:
https://ffmpeg.org/pipermail/ffmpeg-devel/2025-April/341866.html
I suspect the latter isn't being considered [directly because] of the
former, but I also remember reading a reply on some libwebp-based
approach to this, that because it would add an additional dependency
to decoding, it was highly discouraged, also leading me to believe
that the former is the more likely alternative to be used.
However, from an outsider's perspective both appear inactive.
Animated WebPs appear to be getting more and more common, and as
tons of other projects rely on FFmpeg as the back-end, they're also
"suddenly not working on a seemingly established format". FFmpeg was
the last thing I would have blamed since it has always worked for me
before, and I only found this because I use FFmpeg as the (until
this) invincible manual on-the-fly transcoder when something else
fails first. I was quite taken aback by this!
--
Osmo Hyttinen
_______________________________________________
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 reply other threads:[~2025-06-16 10:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-16 10:39 Osmo Hyttinen [this message]
2025-06-16 14:07 ` 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='CAPHZS6n=g-UJAF5fXLh6PqMkVo7aZG0C=nfMnJP5M8qWyOoEDA@mail.gmail.com' \
--to=osmo.hyttinen-at-gmail.com@ffmpeg.org \
--cc=ffmpeg-devel@ffmpeg.org \
/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