From: James Zern <jzern-at-google.com@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] avcodec/libvpxenc: enable dynamic max quantizer parameter reconfiguration
Date: Wed, 16 Mar 2022 16:53:14 -0700
Message-ID: <CABWgkX+4D5fPHTyYetTpr--5pLAHwwCobm9RCkT=6xC4FF_HYw@mail.gmail.com> (raw)
In-Reply-To: <MyHjQUm--3-2@lynne.ee>
Lynne,
On Wed, Mar 16, 2022 at 5:39 AM Lynne <dev@lynne.ee> wrote:
>
> 16 Mar 2022, 13:07 by danilchap-at-google.com@ffmpeg.org:
>
> > ---
> > libavcodec/libvpxenc.c | 7 +++++++
> > 1 file changed, 7 insertions(+)
> >
> > diff --git a/libavcodec/libvpxenc.c b/libavcodec/libvpxenc.c
> > index 8f94ba15dc..45baeed435 100644
> > --- a/libavcodec/libvpxenc.c
> > +++ b/libavcodec/libvpxenc.c
> > @@ -1658,6 +1658,13 @@ static int vpx_encode(AVCodecContext *avctx, AVPacket *pkt,
> > flags |= strtoul(en->value, NULL, 10);
> > }
> >
> > + en = av_dict_get(frame->metadata, "max-quantizer", NULL, 0);
> > + if (en) {
> > + struct vpx_codec_enc_cfg cfg = *enccfg;
> > + cfg.rc_max_quantizer = strtoul(en->value, NULL, 10);
> > + vpx_codec_enc_config_set(&ctx->encoder, &cfg);
> > + }
> >
>
> I was going to NAK the earlier patch, but forgot.
> Please think of a better way than stuffing random data in
> inappropriate fields, and fix the earlier patch that was mistakenly
> merged to not do that.
I agree this isn't great. Would you suggest updating the qmax setting
and checking it / all options on a per-frame basis or is there a
better way to reconfigure the codec on the fly?
_______________________________________________
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-16 23:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-16 12:07 Danil Chapovalov
2022-03-16 12:39 ` Lynne
2022-03-16 23:53 ` James Zern [this message]
2022-03-17 18:45 ` Jan Ekström
2022-03-17 19:07 ` Danil Chapovalov
2022-03-24 13:11 ` Danil Chapovalov
2022-03-24 18:27 ` James Zern
2022-03-28 14:04 ` Danil Chapovalov
2022-03-29 20:58 ` James Zern
2022-03-30 18:24 ` Danil Chapovalov
2022-03-31 17:31 ` James Zern
2022-04-06 1:04 ` James Zern
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='CABWgkX+4D5fPHTyYetTpr--5pLAHwwCobm9RCkT=6xC4FF_HYw@mail.gmail.com' \
--to=jzern-at-google.com@ffmpeg.org \
--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