Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Lynne <dev@lynne.ee>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] Allow to modify max qp configuration parameter in libvpx without reseting the encoder
Date: Wed, 16 Mar 2022 13:37:55 +0100 (CET)
Message-ID: <MyHj0Uk--3-2@lynne.ee> (raw)
In-Reply-To: <CACQca=fuLsiTaOxX4xWwquwuo2KPpEPTYXWjAE3M5Y6SpzDkoA@mail.gmail.com>

16 Mar 2022, 13:13 by danilchap-at-google.com@ffmpeg.org:

> On Mon, Mar 14, 2022 at 4:28 PM Jan Ekström <jeebjp@gmail.com> wrote:
>
>>
>> On Mon, Mar 14, 2022 at 3:05 PM Danil Chapovalov
>> <danilchap-at-google.com@ffmpeg.org> wrote:
>> >
>> > ---
>>
>> Probably something a la
>>
>> avcodec/libvpxenc: enable dynamic quantizer reconfiguration
>>
>> ?
>>
>
> Thank you, resubmitted with new title
>
>>
>> >  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);
>> > +            }
>> > +
>>
>> There is side data already defined for quantizers, AVVideoEncParams /
>> AV_FRAME_DATA_VIDEO_ENC_PARAMS .
>>
>> In other words, this should be handled in a similar manner to ROI, not
>> as an ad-hoc metadata key in the AVFrame.
>>
>
> I've checked struct AVVideoEncParams, it doesn't look fitting: it
> contains exact qp (plus qp per plane), while my patch suggests
> changing max-qp limit for current and following frames.
> AVVideoEncParams also has some extra fields that I'm unsure how to
> handle (they are unrelated to what I'm trying to do),
> I haven't found any other struct that would contain something like max qp.
> What is ROI? What code can I use as an example of your suggestion?
>

If the encoder is operating under bitrate mode, then I think it would
be fine to interpret the qp field as a max qp field.
IIRC Youtube run libvpx and libaom under constant bitrate mode and
adjust the max quantizer per frame, because no one can fix the
rate control system of either library.
_______________________________________________
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".

  reply	other threads:[~2022-03-16 12:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-14 13:04 Danil Chapovalov
2022-03-14 15:27 ` Jan Ekström
2022-03-16 12:13   ` Danil Chapovalov
2022-03-16 12:37     ` Lynne [this message]
2022-03-19 14:25       ` Anton Khirnov
  -- strict thread matches above, loose matches on Subject: below --
2022-03-09 13:27 Danil Chapovalov

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=MyHj0Uk--3-2@lynne.ee \
    --to=dev@lynne.ee \
    --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