From: Stefano Sabatini <stefasab@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH] lavc: clarify color_range semantics Date: Sun, 26 Mar 2023 21:55:58 +0200 Message-ID: <20230326195558.GH26811@mariano> (raw) In-Reply-To: <20230125004425.GE12061@mariano> On date Wednesday 2023-01-25 01:44:25 +0100, Stefano Sabatini wrote: > 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 <stefasab@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; Ping. Will apply in a few days if I see no comments. _______________________________________________ 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".
next prev parent reply other threads:[~2023-03-26 19:56 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-15 17:41 Stefano Sabatini 2023-01-16 4:16 ` Gyan Doshi 2023-01-25 0:44 ` Stefano Sabatini 2023-03-26 19:55 ` Stefano Sabatini [this message] 2023-04-02 14:31 ` Stefano Sabatini
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=20230326195558.GH26811@mariano \ --to=stefasab@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