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] avcodec/aacenc: add strict bit rate control mode
Date: Mon, 24 Apr 2023 14:26:09 +0200 (CEST)
Message-ID: <NTnDc8v--3-9@lynne.ee> (raw)
In-Reply-To: <20230424092634.1012785-1-jrwu@chromium.org>

Apr 24, 2023, 11:27 by jrwu@chromium.org:

> From: Jeremy Wu <jrwu@google.com>
>
> In certain use cases, controlling the maximum frame size is critical. An
> example is when transmitting AAC packets over Bluetooth A2DP.
>
> While the spec allows the packets be fragmented (though UNRECOMMENDED),
> in practice most headsets do not recognize nor reassemble such packets.
>
> In this patch, we add a new mode to specify that the configured bit rate
> should be followed strictly up to frame level.
>
> Signed-off-by: Jeremy Wu <jrwu@chromium.org>
> ---
>  doc/APIchanges       |  3 +++
>  libavcodec/aacenc.c  | 11 +++++++++++
>  libavcodec/avcodec.h |  4 ++++
>  libavcodec/version.h |  2 +-
>  4 files changed, 19 insertions(+), 1 deletion(-)
>
> diff --git a/doc/APIchanges b/doc/APIchanges
> index 0b609e3d3b..e730a7e126 100644
> --- a/doc/APIchanges
> +++ b/doc/APIchanges
> @@ -2,6 +2,9 @@ The last version increases of all libraries were on 2023-02-09
>
>  2023-04-10 - xxxxxxxxxx - lavu 58.6.100 - frame.h
>  av_frame_get_plane_buffer() now accepts const AVFrame*.
>  
> diff --git a/libavcodec/aacenc.c b/libavcodec/aacenc.c
> index ed036209e9..daf5538056 100644
> --- a/libavcodec/aacenc.c
> +++ b/libavcodec/aacenc.c
> @@ -1106,6 +1106,17 @@ static int aac_encode_frame(AVCodecContext *avctx, AVPacket *avpkt,
>  too_many_bits = FFMIN(too_many_bits, 6144 * s->channels - 3);
>  too_few_bits = FFMIN(FFMAX(rate_bits - rate_bits/4, target_bits), too_many_bits);
>  
> +        if (avctx->flags & AV_CODEC_FLAG_STRICT_BITRATE) {
>

Use avctx->bit_rate_tolerance instead. By default, it's set to ~400ish kbps.
Just detect if it's set to zero to enable this code path. You can set the
variable via both the command line and the API.


> +            if (rate_bits < frame_bits) {
> +                /* temporarily degrade quality and repeat until frame fits */
> +                s->lambda *= 0.75f;
> +                continue;
> +            }
> +            /* reset lambda when solution is found */
> +            s->lambda = avctx->global_quality > 0 ? avctx->global_quality : 120;
> +            break;
> +        }
>

That's a heavy handed approach. A better way would be to use the
rate_bits/frame_bits, multiply lambda by the ratio, and use that lambda as
the starting point. That way, you'd need less reencodes to satisfy the condition.

By the way, do you have any specific use for the encoder?
I am in the process of rewriting it, and I'd like to know where it's useful,
apart from the obvious streaming use-case.
_______________________________________________
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:[~2023-04-24 12:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-24  9:26 Jeremy Wu
2023-04-24 12:26 ` Lynne [this message]
2023-04-25  7:40   ` Jeremy Wu
  -- strict thread matches above, loose matches on Subject: below --
2023-04-24  9:14 Jeremy Wu
2023-04-24  8:36 Jeremy Wu

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=NTnDc8v--3-9@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