Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Thilo Borgmann via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: Thilo Borgmann <thilo.borgmann@mail.de>
Subject: Re: [FFmpeg-devel] [PATCH v10 2/5] libavcodec/webp: add support for animated WebP
Date: Mon, 26 Feb 2024 16:54:31 +0100
Message-ID: <ecfa243a-b14f-4c89-906d-44c965a42e4f@mail.de> (raw)
In-Reply-To: <AS8P250MB07444D8F711C64F65661810C8F512@AS8P250MB0744.EURP250.PROD.OUTLOOK.COM>

Am 19.02.24 um 19:01 schrieb Andreas Rheinhardt:
> James Almer:
>> On 2/19/2024 1:50 PM, Andreas Rheinhardt wrote:
>>> a) Use the receive frame callback for this decoder. This will
>>> necessitate changes to pthread_frame.c (which currently can't handle
>>> receive_frame decoders)
>>
>> There's a patch for this that i think Anton wrote and then Timo
>> improved. It was posted sometime ago.
>>
>>> Notice that the BSF I have in mind would not be a public BSF, but a
>>> private one (given that the output of the BSF would be spec-incompliant
>>> due to the wrong ordering it should not be public), i.e. one not
>>> accessible via av_bsf_get_by_name() or av_bsf_iterate().
>>
>> How do you propose to do this? And would you be willing to write the
>> framework for it?
>> It certainly sounds useful, as existing bsfs like vp9_superframe_split
>> already generate spec non-compliant packets, and they ideally should not
>> be publicly available.
> 
> The way I envision is by using a const FFBitStreamFilter* instead of the
> name of the bsf in FFCodec.bsfs. (Of course, one can keep the
> open-by-string method (which also works for filterchains as long as they
> only use static arguments), too; it is also possible (by currently
> unneeded) to add bsfs during init with non-static arguments (based upon
> codec options etc.).)
> I'd be willing to write the code for this.

If that is useful for other codecs as well, let's do that.
Generating one packet per animation containing all frames+meta should be easy enough in the demuxer.

What do you expect the bsf to do exactly?
IIUC generate packets with one frame + meta for all frames in the animation from the big packet coming from the demuxer?

Thanks,
Thilo
_______________________________________________
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".

  reply	other threads:[~2024-02-26 15:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-05 19:41 [FFmpeg-devel] [PATCH v10 0/5] webp: add support for animated WebP decoding Thilo Borgmann via ffmpeg-devel
2024-02-05 19:41 ` [FFmpeg-devel] [PATCH v10 1/5] avcodec/webp: remove unused definitions Thilo Borgmann via ffmpeg-devel
2024-02-05 19:41 ` [FFmpeg-devel] [PATCH v10 2/5] libavcodec/webp: add support for animated WebP Thilo Borgmann via ffmpeg-devel
2024-02-19 16:50   ` Andreas Rheinhardt
2024-02-19 17:07     ` James Almer
2024-02-19 18:01       ` Andreas Rheinhardt
2024-02-26 15:54         ` Thilo Borgmann via ffmpeg-devel [this message]
2024-02-26 15:54     ` Thilo Borgmann via ffmpeg-devel
2024-02-05 19:41 ` [FFmpeg-devel] [PATCH v10 3/5] avcodec/webp: make init_canvas_frame static Thilo Borgmann via ffmpeg-devel
2024-02-05 19:41 ` [FFmpeg-devel] [PATCH v10 4/5] libavformat/webp: add WebP demuxer Thilo Borgmann via ffmpeg-devel
2024-02-19 17:40   ` Andreas Rheinhardt
2024-02-05 19:41 ` [FFmpeg-devel] [PATCH v10 5/5] fate: add test for animated WebP Thilo Borgmann via ffmpeg-devel

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=ecfa243a-b14f-4c89-906d-44c965a42e4f@mail.de \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=thilo.borgmann@mail.de \
    /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