From: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH 1/2] avcodec/decode: inject missing global side data to output frames
Date: Wed, 26 Feb 2025 17:57:18 +0100
Message-ID: <AS8P250MB07446687B1F06657D2F627D78FC22@AS8P250MB0744.EURP250.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20250226164150.5461-1-jamrial@gmail.com>
James Almer:
> ff_decode_frame_props() injects global side data passed by the caller (Usually
> coming from the container) but ignores the global side data the decoder
> gathered from the bitstream itself.
> This commit amends this.
>
> Signed-off-by: James Almer <jamrial@gmail.com>
> ---
> libavcodec/decode.c | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/libavcodec/decode.c b/libavcodec/decode.c
> index cac7e620d2..c5a577f4f1 100644
> --- a/libavcodec/decode.c
> +++ b/libavcodec/decode.c
> @@ -1570,6 +1570,15 @@ int ff_decode_frame_props(AVCodecContext *avctx, AVFrame *frame)
> if (ret < 0)
> return ret;
>
> + for (int i = 0; i < avctx->nb_decoded_side_data; i++) {
> + const AVFrameSideData *src = avctx->decoded_side_data[i];
> + if (av_frame_get_side_data(frame, src->type))
> + continue;
> + ret = av_frame_side_data_clone(&frame->side_data, &frame->nb_side_data, src, 0);
> + if (ret < 0)
> + return ret;
> + }
> +
> if (!(ffcodec(avctx->codec)->caps_internal & FF_CODEC_CAP_SETS_FRAME_PROPS)) {
> const AVPacket *pkt = avctx->internal->last_pkt_props;
>
Why is this attached to every frame instead of just the first one?
If I read this correctly, it will be possible for there to be
decoded_side_data propagated to the output, then in-stream side-data of
the same type (not overridden) and in the next frame, the decoder adds
the decoded_side_data again, presuming that the side data from the
earlier frame was meant to be non-persistent.
- Andreas
_______________________________________________
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:[~2025-02-26 16:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 16:41 James Almer
2025-02-26 16:41 ` [FFmpeg-devel] [PATCH 2/2] fftools/ffmpeg_dec: remove side data copy block James Almer
2025-02-26 16:57 ` Andreas Rheinhardt [this message]
2025-02-26 18:33 ` [FFmpeg-devel] [PATCH 1/2] avcodec/decode: inject missing global side data to output frames James Almer
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=AS8P250MB07446687B1F06657D2F627D78FC22@AS8P250MB0744.EURP250.PROD.OUTLOOK.COM \
--to=andreas.rheinhardt@outlook.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