On date Monday 2023-01-16 09:46:35 +0530, Gyan Doshi wrote: > On 2023-01-15 11:11 pm, Stefano Sabatini wrote: > > Mark this option as encode-only and extend description. > > There are scripts which set this (and other color props) on the input, and > then those streams can be sent to multiple filters with the props set, > instead of having to use setparams in each chain.
Good point, amended with this considerations in mind.
>From bcddce6d1ea802638770dcfd8e7ecb6d798f63c6 Mon Sep 17 00:00:00 2001 From: Stefano Sabatini <stefa...@gmail.com> Date: Sun, 15 Jan 2023 18:16:45 +0100 Subject: [PATCH] lavc: clarify color_range semantics Extend description for decoding and encoding use cases. Address issue: http://trac.ffmpeg.org/ticket/443 --- libavcodec/avcodec.h | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/libavcodec/avcodec.h b/libavcodec/avcodec.h index 0ac581d660..85bb95144d 100644 --- a/libavcodec/avcodec.h +++ b/libavcodec/avcodec.h @@ -976,8 +976,11 @@ typedef struct AVCodecContext { /** * MPEG vs JPEG YUV range. - * - encoding: Set by user - * - decoding: Set by libavcodec + * - encoding: Set by user to override the default output color range value, + * If not specified, libavcodec sets the color range depending on the + * output format. + * - decoding: Set by libavcodec, can be set by the user to propagate the + * color range to components reading from the decoder context. */ enum AVColorRange color_range; -- 2.25.1
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
