Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH v10 1/6] lavu/frame: Add Dolby Vision metadata side data type
Date: Mon, 3 Jan 2022 09:45:55 +0100
Message-ID: <AM7PR03MB6660BED4232331BD90D9063A8F499@AM7PR03MB6660.eurprd03.prod.outlook.com> (raw)
In-Reply-To: <20220103094009.GB67947@xor.haasn.dev>

Niklas Haas:
> On Mon, 03 Jan 2022 01:27:22 +0100 Niklas Haas <ffmpeg@haasn.xyz> wrote:
>> +/**
>> + * Dolby Vision RPU data mapping parameters.
>> + *
>> + * @note sizeof(AVDOVIDataMapping) is not part of the public ABI.
>> + */
>> +typedef struct AVDOVIDataMapping {
>> +    uint8_t vdr_rpu_id;
>> +    uint8_t mapping_color_space;
>> +    uint8_t mapping_chroma_format_idc;
>> +    AVDOVIReshapingCurve curves[3]; /* per component */
>> +
>> +    /* Non-linear inverse quantization */
>> +    enum AVDOVINLQMethod nlq_method_idc;
>> +    uint32_t num_x_partitions;
>> +    uint32_t num_y_partitions;
>> +    AVDOVINLQParams nlq[3]; /* per component */
>> +} AVDOVIDataMapping;
> 
> It just occurred to me that we also cannot make AVDOVIReshapingCurve or
> AVDOVINLQParams extensible if we're going to store them in an array.
> 
> So I think that locks us into making these structs fixed size, avoiding
> the issue altogether, but probably making future extensions to this API
> somewhat uglier.
> 
> Thoughts?

Future extensions are still possible by adding e.g.
"AVDOVIReshapingCurveExtension curves_ext[3]" (which is probably what
you meant by uglier), so I am ok with this approach.
(Hopefully we won't need multiple extensions...).

- 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".

  reply	other threads:[~2022-01-03  8:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-03  0:27 Niklas Haas
2022-01-03  0:27 ` [FFmpeg-devel] [PATCH v10 2/6] lavfi/showinfo: Support AV_FRAME_DATA_DOVI_METADATA Niklas Haas
2022-01-03  0:27 ` [FFmpeg-devel] [PATCH v10 3/6] ffprobe: " Niklas Haas
2022-01-03  0:27 ` [FFmpeg-devel] [PATCH v10 4/6] lavc: Implement Dolby Vision RPU parsing Niklas Haas
2022-01-04  9:13   ` Andreas Rheinhardt
2022-01-03  0:27 ` [FFmpeg-devel] [PATCH v10 5/6] fate: Limit Dolby Vision RPU test frame count Niklas Haas
2022-01-03  0:27 ` [FFmpeg-devel] [PATCH v10 6/6] lavc/hevcdec: Parse DOVI RPU NALs Niklas Haas
2022-01-04  9:17   ` Andreas Rheinhardt
2022-01-03  8:40 ` [FFmpeg-devel] [PATCH v10 1/6] lavu/frame: Add Dolby Vision metadata side data type Niklas Haas
2022-01-03  8:45   ` Andreas Rheinhardt [this message]
2022-01-03  8:55     ` [FFmpeg-devel] [PATCH v11] " Niklas Haas
2022-01-04  9:03       ` Andreas Rheinhardt

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=AM7PR03MB6660BED4232331BD90D9063A8F499@AM7PR03MB6660.eurprd03.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