Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Leo Izen <leo.izen@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] avutil/csp: create public API for colorspace structs
Date: Mon, 16 May 2022 10:45:26 -0400
Message-ID: <45bca218-4344-133c-7adf-c8225baa9778@gmail.com> (raw)
In-Reply-To: <DB6PR0101MB22141EB2603504D516F606EB8FCC9@DB6PR0101MB2214.eurprd01.prod.exchangelabs.com>

On 5/15/22 12:32, Andreas Rheinhardt wrote:
> Leo Izen:
>> +/* Returns AVCOL_PRI_UNSPECIFIED if no clear match can be identified */
>> +enum AVColorPrimaries av_detect_color_primaries(const struct ColorPrimaries *prm);
>> +
>> +const struct ColorPrimaries *av_get_color_primaries(enum AVColorPrimaries prm);
>> +const struct LumaCoefficients *av_get_luma_coefficients(enum AVColorSpace csp);
>> +
>> +#endif /* AVUTIL_CSP_H */
> 
> Is there any scenario in which these structs might need to be extended?
> This is something that we could no longer easily do if these structs
> were public.
> 

I don't believe these will need to be extended since they're somewhat 
simple structs that are meant to contain a very specific set of data, 
not general data about a more abstract object.

- Leo Izen (thebombzen)
_______________________________________________
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-05-16 14:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-13 15:42 Leo Izen
2022-05-13 19:14 ` Ronald S. Bultje
2022-05-13 19:18 ` James Almer
2022-05-14  2:43   ` Leo Izen
2022-05-13 21:22 ` Michael Niedermayer
2022-05-14  2:41   ` Leo Izen
2022-05-14 12:15     ` Niklas Haas
2022-05-15 16:49   ` Ronald S. Bultje
2022-05-15 18:10     ` Niklas Haas
2022-05-15 18:55     ` Michael Niedermayer
2022-05-15 19:19       ` Michael Niedermayer
2022-05-15 16:32 ` Andreas Rheinhardt
2022-05-16 14:45   ` Leo Izen [this message]
2022-05-18 12:21   ` Niklas Haas
2022-05-18 12:29     ` Niklas Haas

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=45bca218-4344-133c-7adf-c8225baa9778@gmail.com \
    --to=leo.izen@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