From: "Martin Storsjö" <martin@martin.st> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Cc: Limin Wang <lance.lmwang@gmail.com> Subject: Re: [FFmpeg-devel] [PATCH 1/3] avcodec/libopenh264enc: support for colorspace and range information Date: Thu, 13 Jan 2022 23:35:32 +0200 (EET) Message-ID: <5c311b5a-f762-12e-89df-c83373c8dbad@martin.st> (raw) In-Reply-To: <1642070709-3104-1-git-send-email-lance.lmwang@gmail.com> On Thu, 13 Jan 2022, lance.lmwang@gmail.com wrote: > From: Limin Wang <lance.lmwang@gmail.com> > > Signed-off-by: Limin Wang <lance.lmwang@gmail.com> > --- > libavcodec/libopenh264enc.c | 15 +++++++++++++++ > 1 file changed, 15 insertions(+) > > diff --git a/libavcodec/libopenh264enc.c b/libavcodec/libopenh264enc.c > index de4b85c..a55bef8 100644 > --- a/libavcodec/libopenh264enc.c > +++ b/libavcodec/libopenh264enc.c > @@ -330,6 +330,21 @@ static av_cold int svc_encode_init(AVCodecContext *avctx) > } > } > > +#if OPENH264_VER_AT_LEAST(1, 6) > + param.sSpatialLayers[0].uiVideoFormat = VF_UNDEF; > + param.sSpatialLayers[0].bVideoSignalTypePresent = true; What does this flag do, and why do we set it unconditionally while we didn't use to before? > + if (avctx->color_range != AVCOL_RANGE_UNSPECIFIED) > + param.sSpatialLayers[0].bFullRange = (avctx->color_range == AVCOL_RANGE_JPEG); > + > + param.sSpatialLayers[0].bColorDescriptionPresent = true; Ditto - what does this do and why do we set it even if we wouldn't set any of the other fields? // Martin _______________________________________________ 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:[~2022-01-13 21:35 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-13 10:45 lance.lmwang 2022-01-13 10:45 ` [FFmpeg-devel] [PATCH 2/3] avcodec/libopenh264enc: make the profile configuablable correctly lance.lmwang 2022-01-13 21:57 ` Martin Storsjö 2022-01-14 3:17 ` lance.lmwang 2022-01-13 10:45 ` [FFmpeg-devel] [PATCH 3/3] avcodec/libopenh264enc: set iEntropyCodingModeFlag by coder option lance.lmwang 2022-01-13 22:01 ` Martin Storsjö 2022-01-14 3:20 ` lance.lmwang 2022-01-13 21:35 ` Martin Storsjö [this message] 2022-01-14 2:59 ` [FFmpeg-devel] [PATCH 1/3] avcodec/libopenh264enc: support for colorspace and range information lance.lmwang 2022-01-14 9:00 ` [FFmpeg-devel] [PATCH v2 " lance.lmwang 2022-01-14 9:00 ` [FFmpeg-devel] [PATCH v2 2/3] avcodec/libopenh264enc: make the profile configuablable correctly lance.lmwang 2022-01-14 9:28 ` Martin Storsjö 2022-01-14 9:43 ` lance.lmwang 2022-01-14 9:00 ` [FFmpeg-devel] [PATCH v2 3/3] avcodec/libopenh264enc: set iEntropyCodingModeFlag by coder option lance.lmwang 2022-01-14 9:30 ` Martin Storsjö 2022-01-14 9:23 ` [FFmpeg-devel] [PATCH v2 1/3] avcodec/libopenh264enc: support for colorspace and range information Martin Storsjö 2022-01-14 9:55 ` [FFmpeg-devel] [PATCH v3 " lance.lmwang 2022-01-14 9:55 ` [FFmpeg-devel] [PATCH v3 2/3] avcodec/libopenh264enc: make the profile configuablable correctly lance.lmwang 2022-01-14 12:07 ` Martin Storsjö 2022-01-14 13:49 ` lance.lmwang 2022-01-14 9:55 ` [FFmpeg-devel] [PATCH v3 3/3] avcodec/libopenh264enc: set iEntropyCodingModeFlag by coder option lance.lmwang
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=5c311b5a-f762-12e-89df-c83373c8dbad@martin.st \ --to=martin@martin.st \ --cc=ffmpeg-devel@ffmpeg.org \ --cc=lance.lmwang@gmail.com \ /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