From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: [FFmpeg-devel] [RFC] webp decoding
Date: Thu, 26 Jun 2025 02:58:44 +0200
Message-ID: <20250626005844.GD29660@pb2> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1105 bytes --]
Hi
some people use webp apparently, and we have no decoder
There are 2 patchsets
Thilos v13 (native decoder)
Peters libwebp based one
I tested both and thilos code decodes the files from the 4709 ticket
i was not able to decode anything with peters patch. Iam not sure it
needs some demuxer changes that are missing it also didnt work with
the demuxer chanegs from thilos pacthset.
What i suggest is ... can we just apply thilos patchset ?
what do people think about that idea ?
It does have a review comment about use of nested decoders and direct
rendering not working. But honestly. That decoder (maybe marked as
experimental?) seems better than having no decoder
Do we have someone willing to work on webp ?
(Iam pretty sure we can fund that work someehow if interrest is conditional on US$)
Or is someone even already working on it ?
thx
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
No human being will ever know the Truth, for even if they happen to say it
by chance, they would not even known they had done so. -- Xenophanes
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- 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 reply other threads:[~2025-06-26 0:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-26 0:58 Michael Niedermayer [this message]
2025-06-26 7:00 ` Hendrik Leppkes
2025-06-26 17:33 ` James Zern via ffmpeg-devel
2025-06-26 17:37 ` Michael Niedermayer
2025-06-27 23:54 ` compn
2025-06-28 14:18 ` 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=20250626005844.GD29660@pb2 \
--to=michael@niedermayer.cc \
--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