From: James Almer <jamrial@gmail.com> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] [PATCH] avcodec/libsvtav1: add support for setting chroma sample location Date: Mon, 25 Apr 2022 18:15:51 -0300 Message-ID: <c7373d95-6d53-3247-aed1-4ec37bd2e1f6@gmail.com> (raw) In-Reply-To: <20220425210212.64448-1-jeebjp@gmail.com> On 4/25/2022 6:02 PM, Jan Ekström wrote: > Support for configuring this was added with version 1.0.0. > --- > libavcodec/libsvtav1.c | 22 ++++++++++++++++++++++ > 1 file changed, 22 insertions(+) > > diff --git a/libavcodec/libsvtav1.c b/libavcodec/libsvtav1.c > index 2e3d96ce37..a670dab822 100644 > --- a/libavcodec/libsvtav1.c > +++ b/libavcodec/libsvtav1.c > @@ -205,6 +205,28 @@ static int config_enc_params(EbSvtAv1EncConfiguration *param, > else > param->color_range = !!(desc->flags & AV_PIX_FMT_FLAG_RGB); > > +#if SVT_AV1_CHECK_VERSION(1, 0, 0) > + if (avctx->chroma_sample_location != AVCHROMA_LOC_UNSPECIFIED) { > + switch (avctx->chroma_sample_location) { > + case AVCHROMA_LOC_LEFT: > + param->chroma_sample_position = EB_CSP_VERTICAL; > + break; > + case AVCHROMA_LOC_TOPLEFT: > + param->chroma_sample_position = EB_CSP_COLOCATED; > + break; > + default: > + av_log(avctx, AV_LOG_INFO, > + "Specified chroma sample location %s (%d) is unsupported " > + "on the AV1 bit stream level. Usage of a container that " > + "allows passing this information - such as Matroska - " > + "is recommended.\n", > + av_chroma_location_name(avctx->chroma_sample_location), This can return NULL on invalid AVChromaLocation values, so better check for that and print a different log message. > + avctx->chroma_sample_location); > + break; > + } > + } > +#endif > + > if (avctx->profile != FF_PROFILE_UNKNOWN) > param->profile = avctx->profile; > _______________________________________________ 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-04-25 21:16 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-25 21:02 Jan Ekström 2022-04-25 21:15 ` James Almer [this message] 2022-04-25 21:59 ` [FFmpeg-devel] [PATCH v2] " Jan Ekström 2022-04-25 23:44 ` James Almer 2022-04-26 6:19 ` Jan Ekström
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=c7373d95-6d53-3247-aed1-4ec37bd2e1f6@gmail.com \ --to=jamrial@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