From: Anton Khirnov <anton@khirnov.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Timo Rothenpieler <timo@rothenpieler.org>
Subject: Re: [FFmpeg-devel] [PATCH 1/2] avcodec/thread: add support for frame threading receive_frame based decoders
Date: Tue, 06 Dec 2022 15:37:07 +0100
Message-ID: <167033742725.26119.15040760416331150943@lain.khirnov.net> (raw)
In-Reply-To: <20221205133938.505-1-timo@rothenpieler.org>
Quoting Timo Rothenpieler (2022-12-05 14:39:37)
> This is fairly basic and makes a lot of assumptions, but it works
> for the most simple cases.
>
> For one, it only ever fetches exactly one packet per call to receive_frame.
> Right now it's impossible for there to ever be more than one, but the API
> allows for more, which might need handled in the future.
>
> It also basically translates the new API back to the old, since that's how
> the frame threading code operates. Which feels backwards in regards to
> the new API, but it was the path with least resistance in implementing this.
If it only supports one packet to one frame, then it goes against the
whole point of using the receive_frame API.
--
Anton Khirnov
_______________________________________________
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 prev parent reply other threads:[~2022-12-06 14:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 13:39 Timo Rothenpieler
2022-12-05 13:39 ` [FFmpeg-devel] [PATCH 2/2] avcodec/mjpegdec: add support for frame threading Timo Rothenpieler
2022-12-05 14:15 ` Andreas Rheinhardt
2022-12-05 14:28 ` Paul B Mahol
2022-12-05 23:02 ` Timo Rothenpieler
2023-09-07 17:17 ` Paul B Mahol
2023-09-07 17:28 ` Paul B Mahol
2022-12-06 14:37 ` Anton Khirnov [this message]
2022-12-06 14:39 ` [FFmpeg-devel] [PATCH 1/2] avcodec/thread: add support for frame threading receive_frame based decoders Timo Rothenpieler
2022-12-06 14:43 ` Anton Khirnov
2022-12-06 15:08 ` Timo Rothenpieler
2022-12-06 16:00 ` Anton Khirnov
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=167033742725.26119.15040760416331150943@lain.khirnov.net \
--to=anton@khirnov.net \
--cc=ffmpeg-devel@ffmpeg.org \
--cc=timo@rothenpieler.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