Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: James Almer <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH v6] lavc: convert frame threading to the receive_frame() pattern
Date: Tue, 20 Dec 2022 13:15:24 -0300
Message-ID: <b56e0f94-e4e4-1af1-5dd7-ed32f4778bf1@gmail.com> (raw)
In-Reply-To: <e04ccad8-c56d-6f54-2221-e40ff87e0de2@rothenpieler.org>

On 12/20/2022 1:06 PM, Timo Rothenpieler wrote:
>>
>> Generally, I don't see the advantage of this. The only decoder that
>> would benefit from it is SMVJPEG, yet for all other codecs it will just
>> involve more allocs+frees.
> 
> Being unable to support newer encoders because only the old (and I 
> thought deprecated, but apprently not, given encoders are getting ported 
> back to it??) is a pretty bad situation, and could hold back some progress.

Decoders. And what was deprecated and removed was the public API, not 
the internal callback.
For 1:1 decoders, or decoders with no delay or buffering, the decoupled 
input/output callback is overkill, so you'll keep seeing new decoders 
added using the old one in the future.
But similarly, new decoders can and will be added using the decoupled IO 
callback, so this change is necessary so any future decoder that intends 
to have frame threading isn't forced to use the old callback when it 
could benefit from the new. An obvious case would be the (hopefully) 
eventual native AV1 decoder.

> 
> So adding the ability for frame threading to work for everything seems 
> natural and neccesary to me.

Yes.
_______________________________________________
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:[~2022-12-20 16:15 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-07 11:43 [FFmpeg-devel] [PATCH 1/2] " Timo Rothenpieler
2022-12-07 11:43 ` [FFmpeg-devel] [PATCH 2/2] avcodec/mjpegdec: add support for frame threading Timo Rothenpieler
2022-12-07 13:14 ` [FFmpeg-devel] [PATCH v2] lavc: convert frame threading to the receive_frame() pattern Timo Rothenpieler
2022-12-07 13:20 ` [FFmpeg-devel] [PATCH v3] " Timo Rothenpieler
2022-12-07 22:22   ` Michael Niedermayer
2022-12-09 13:09     ` Timo Rothenpieler
2022-12-09 13:11       ` James Almer
2022-12-09 16:17       ` Michael Niedermayer
2022-12-09 13:37     ` [FFmpeg-devel] [PATCH v4] " Timo Rothenpieler
2022-12-09 23:46       ` Michael Niedermayer
2022-12-10 20:10         ` Timo Rothenpieler
2022-12-11 16:29           ` Michael Niedermayer
2022-12-12 21:42         ` [FFmpeg-devel] [PATCH v5 1/2] " Timo Rothenpieler
2022-12-12 21:42           ` [FFmpeg-devel] [PATCH v5 2/2] avcodec/mjpegdec: add support for frame threading Timo Rothenpieler
2022-12-13 18:17           ` [FFmpeg-devel] [PATCH v5 1/2] lavc: convert frame threading to the receive_frame() pattern Michael Niedermayer
2022-12-14  1:50             ` [FFmpeg-devel] [PATCH v6] " Timo Rothenpieler
2022-12-15 22:10               ` Michael Niedermayer
2022-12-19 11:37               ` Timo Rothenpieler
2022-12-20 11:45               ` Andreas Rheinhardt
2022-12-20 16:06                 ` Timo Rothenpieler
2022-12-20 16:15                   ` James Almer [this message]
2022-12-21 14:22                 ` [FFmpeg-devel] [PATCH v7 1/2] " Timo Rothenpieler
2022-12-21 14:22                   ` [FFmpeg-devel] [PATCH v7 2/2] avcodec/mjpegdec: add support for frame threading Timo Rothenpieler
2022-12-21 21:35                     ` 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=b56e0f94-e4e4-1af1-5dd7-ed32f4778bf1@gmail.com \
    --to=jamrial@gmail.com \
    --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