Le duodi 2 thermidor, an CCXXV, Rostislav Pehlivanov a écrit : > Many image formats support embedding of ICC profiles directly in > their bitstreams. Add a new side data type to allow exposing them to > API users.
Why not make it a member of AVFrame directly? It looks to me very
similar in principle to color_range, color_primaries, colorspace, etc.
>
> Signed-off-by: Rostislav Pehlivanov <atomnu...@gmail.com>
> ---
> libavutil/frame.h | 6 ++++++
> libavutil/version.h | 2 +-
> 2 files changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/libavutil/frame.h b/libavutil/frame.h
> index 26261d7e40..ee899d844d 100644
> --- a/libavutil/frame.h
> +++ b/libavutil/frame.h
> @@ -134,6 +134,12 @@ enum AVFrameSideDataType {
> * the form of the AVContentLightMetadata struct.
> */
> AV_FRAME_DATA_CONTENT_LIGHT_LEVEL,
> +
> + /**
> + * The data contains an ICC profile with an optional name defined in the
> + * metadata entry.
Not being a specialist of ICC profiles, I have no idea what that means
in practice. What data structure is it?
> + */
> + AV_FRAME_DATA_ICC_PROFILE,
> };
>
> enum AVActiveFormatDescription {
> diff --git a/libavutil/version.h b/libavutil/version.h
> index d4f9335a2f..35987e7b50 100644
> --- a/libavutil/version.h
> +++ b/libavutil/version.h
> @@ -80,7 +80,7 @@
>
>
> #define LIBAVUTIL_VERSION_MAJOR 55
> -#define LIBAVUTIL_VERSION_MINOR 68
> +#define LIBAVUTIL_VERSION_MINOR 69
> #define LIBAVUTIL_VERSION_MICRO 100
>
> #define LIBAVUTIL_VERSION_INT AV_VERSION_INT(LIBAVUTIL_VERSION_MAJOR, \
Regards,
--
Nicolas George
signature.asc
Description: Digital signature
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
