From: James Almer <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [FFmpeg-cvslog] ffmpeg: pass first video AVFrame's side data to encoder
Date: Fri, 22 Mar 2024 16:38:38 -0300
Message-ID: <3a966dd3-ee38-442e-ad43-108f849c4556@gmail.com> (raw)
In-Reply-To: <171110112517.7287.14787984561092623515@lain.khirnov.net>
On 3/22/2024 6:52 AM, Anton Khirnov wrote:
> Quoting Jan Ekström (2024-03-20 18:31:49)
>> ffmpeg | branch: master | Jan Ekström <jeebjp@gmail.com> | Mon Jan 9 20:52:30 2023 +0200| [8f4b173029aa9ecefb1370c954ef769664920d08] | committer: Jan Ekström
>>
>> ffmpeg: pass first video AVFrame's side data to encoder
>>
>> This enables further configuration of output based on the results
>> of input decoding and filtering in a similar manner as the color
>> information.
>>
>>> http://git.videolan.org/gitweb.cgi/ffmpeg.git/?a=commit;h=8f4b173029aa9ecefb1370c954ef769664920d08
>> ---
>>
>> fftools/ffmpeg_enc.c | 15 +++++++++++++++
>> 1 file changed, 15 insertions(+)
>>
>> diff --git a/fftools/ffmpeg_enc.c b/fftools/ffmpeg_enc.c
>> index c9a12af139..f01be1c22f 100644
>> --- a/fftools/ffmpeg_enc.c
>> +++ b/fftools/ffmpeg_enc.c
>> @@ -246,6 +246,21 @@ int enc_open(void *opaque, const AVFrame *frame)
>> enc_ctx->colorspace = frame->colorspace;
>> enc_ctx->chroma_sample_location = frame->chroma_location;
>>
>> + for (int i = 0; i < frame->nb_side_data; i++) {
>> + ret = av_frame_side_data_clone(
>> + &enc_ctx->decoded_side_data, &enc_ctx->nb_decoded_side_data,
>> + frame->side_data[i], AV_FRAME_SIDE_DATA_FLAG_UNIQUE);
>
> I objected to this indiscriminate copying in a previous review.
>
> There is no reason to expect side data to apply to the whole stream just
> because it happens to apply to the first frame. For many side data types
> it does not even make sense, as they are fundamentally per-frame.
So this would need to be handled by having decoders export global side
data in decoded_side_data directly, so there's no need to take them from
frames here (which would include per frame side data, like hdr10 and
closed captions), right?
_______________________________________________
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:[~2024-03-22 19:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240320173150.6A520412633@natalya.videolan.org>
2024-03-22 9:52 ` Anton Khirnov
2024-03-22 19:38 ` James Almer [this message]
2024-03-22 21:11 ` 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=3a966dd3-ee38-442e-ad43-108f849c4556@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