Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: compn <ff@hawaiiantel.net>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [RFC] webp decoding
Date: Fri, 27 Jun 2025 13:54:04 -1000
Message-ID: <20250627135404.00003dbd@hawaiiantel.net> (raw)
In-Reply-To: <20250626005844.GD29660@pb2>

On Thu, 26 Jun 2025 02:58:44 +0200, Michael Niedermayer wrote:

> 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

i say go for it. +experimental.

once its in , we can see if web browsers use it, then maybe they'll
take up the mantle.

-compn
_______________________________________________
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".

      parent reply	other threads:[~2025-06-27 23:54 UTC|newest]

Thread overview: 5+ 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
2025-06-26 17:37     ` Michael Niedermayer
2025-06-27 23:54 ` compn [this message]

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=20250627135404.00003dbd@hawaiiantel.net \
    --to=ff@hawaiiantel.net \
    --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