From: James Almer <jamrial@gmail.com> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] [PATCH 2/2] avcodec/libsvtav1: clean up unconditional override of avctx bit rate Date: Tue, 29 Mar 2022 23:20:50 -0300 Message-ID: <507280f6-9915-8256-6e58-a967956e79d3@gmail.com> (raw) In-Reply-To: <20220327180211.12038-2-jeebjp@gmail.com> On 3/27/2022 3:02 PM, Jan Ekström wrote: > This value is only documented to be utilized if rate control is > set to one of the bit rate based modes. These modes are not the > default and thus the wrapper itself configures a bit rate according > to the avctx if bit rate based encoding is requested, making the > relevant value already be set when relevant. You can pass about anything with svtav1-params, which can change param->target_bit_rate. It's better to reflect that in the AVCodecContext. > --- > libavcodec/libsvtav1.c | 1 - > 1 file changed, 1 deletion(-) > > diff --git a/libavcodec/libsvtav1.c b/libavcodec/libsvtav1.c > index d89fefdf4c..fe0d100beb 100644 > --- a/libavcodec/libsvtav1.c > +++ b/libavcodec/libsvtav1.c > @@ -271,7 +271,6 @@ static int config_enc_params(EbSvtAv1EncConfiguration *param, > param->frame_rate_denominator = avctx->time_base.num * avctx->ticks_per_frame; > } > > - avctx->bit_rate = param->target_bit_rate; > if (avctx->bit_rate) { > param->max_qp_allowed = avctx->qmax; > param->min_qp_allowed = avctx->qmin; _______________________________________________ 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-03-30 2:21 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-27 18:02 [FFmpeg-devel] [PATCH 1/2] avcodec/libsvtav1: signal CPB properties through side data Jan Ekström 2022-03-27 18:02 ` [FFmpeg-devel] [PATCH 2/2] avcodec/libsvtav1: clean up unconditional override of avctx bit rate Jan Ekström 2022-03-29 13:09 ` lance.lmwang 2022-03-30 2:20 ` James Almer [this message] 2022-03-30 9:36 ` 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=507280f6-9915-8256-6e58-a967956e79d3@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