Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Vittorio Giovara <vittorio.giovara@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 07/12] avcodec/hevcdec: check for DOVI configuration record in AVCodecContext side data
Date: Mon, 28 Aug 2023 15:00:47 +0200
Message-ID: <CABLWnS-JY-sPzJ6nM2BnGTB+uPkDbvi_GPd7Yi=p7mf2AJj_Fw@mail.gmail.com> (raw)
In-Reply-To: <20230828123617.57535-8-jamrial@gmail.com>

On Mon, Aug 28, 2023 at 2:38 PM James Almer <jamrial@gmail.com> wrote:

> Signed-off-by: James Almer <jamrial@gmail.com>
> ---
>  libavcodec/hevcdec.c | 15 ++++++++++++++-
>  1 file changed, 14 insertions(+), 1 deletion(-)
>
> diff --git a/libavcodec/hevcdec.c b/libavcodec/hevcdec.c
> index df40c91ba6..dabfe89d4a 100644
> --- a/libavcodec/hevcdec.c
> +++ b/libavcodec/hevcdec.c
> @@ -3337,8 +3337,15 @@ static int hevc_decode_frame(AVCodecContext *avctx,
> AVFrame *rframe,
>      }
>
>      sd = av_packet_get_side_data(avpkt, AV_PKT_DATA_DOVI_CONF, &sd_size);
> -    if (sd && sd_size > 0)
> +    if (sd && sd_size > 0) {
> +        int old = s->dovi_ctx.dv_profile;
> +
>          ff_dovi_update_cfg(&s->dovi_ctx,
> (AVDOVIDecoderConfigurationRecord *) sd);
> +        if (old)
> +            av_log(avctx, AV_LOG_DEBUG,
> +                   "New DOVI configuration record from input packet
> (profile %d -> %u).\n",
> +                   old, s->dovi_ctx.dv_profile);
> +    }
>

In general isn't the bitstream side data more important than the container
level one?
Unless specified with a flag, I'd expect that the bistream information is
preserved over the other ones since it's harder to misconfure, and (iirc)
it's what we do in many other places (for example on color properties
config).
-- 
Vittorio
_______________________________________________
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:[~2023-08-28 13:01 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-28 12:34 [FFmpeg-devel] [PATCH 00/12 v2] AVCodecContext and AVCodecParameters " James Almer
2023-08-28 12:34 ` [FFmpeg-devel] [PATCH 01/12] avcodec/avcodec: add side data to AVCodecContext James Almer
2023-08-28 12:34 ` [FFmpeg-devel] [PATCH 02/12] avcodec/codec_par: add side data to AVCodecParameters James Almer
2023-08-28 12:34 ` [FFmpeg-devel] [PATCH 03/12] avformat/avformat: use the side data from AVStream.codecpar James Almer
2023-08-28 12:34 ` [FFmpeg-devel] [PATCH 04/12] fftools/ffmpeg: stop using AVStream.side_data James Almer
2023-08-28 12:34 ` [FFmpeg-devel] [PATCH 05/12] fftools/ffplay: " James Almer
2023-08-28 12:34 ` [FFmpeg-devel] [PATCH 06/12] fftools/ffprobe: " James Almer
2023-08-28 12:34 ` [FFmpeg-devel] [PATCH 07/12] avcodec/hevcdec: check for DOVI configuration record in AVCodecContext side data James Almer
2023-08-28 13:00   ` Vittorio Giovara [this message]
2023-08-28 13:25     ` James Almer
2023-08-28 12:35 ` [FFmpeg-devel] [PATCH 08/12] avcodec/decode: check for global side data " James Almer
2023-08-29  6:24   ` Pavel Koshevoy
2023-08-29 21:13     ` James Almer
2023-08-28 12:35 ` [FFmpeg-devel] [PATCH 09/12] fftools/ffmpeg: stop injecting stream side data in packets James Almer
2023-08-28 12:35 ` [FFmpeg-devel] [PATCH 10/12] fftools/ffplay: " James Almer
2023-08-28 12:35 ` [FFmpeg-devel] [PATCH 11/12] avcodec/avcodec: deprecate coded_side_data James Almer
2023-08-28 12:35 ` [FFmpeg-devel] [PATCH 12/12] fftools: stop propagating the encoder's coded_side_data James Almer
2023-08-29  7:55 ` [FFmpeg-devel] [PATCH 00/12 v2] AVCodecContext and AVCodecParameters side data Anton Khirnov
2023-08-29 11:39   ` 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='CABLWnS-JY-sPzJ6nM2BnGTB+uPkDbvi_GPd7Yi=p7mf2AJj_Fw@mail.gmail.com' \
    --to=vittorio.giovara@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