From: Dmitrii Okunev <xaionaro@gmail.com>
To: Zhao Zhili <quinkblack@foxmail.com>,
FFmpeg development discussions and patches
<ffmpeg-devel@ffmpeg.org>
Cc: Dmitrii Okunev <xaionaro@dx.center>
Subject: Re: [FFmpeg-devel] [PATCH] avcodec/mediacodec: Add support of dynamic bitrate
Date: Wed, 29 May 2024 12:45:48 +0100
Message-ID: <a38d617a6cf13c1eff64f891bc367662b1acceb5.camel@gmail.com> (raw)
In-Reply-To: <tencent_94AC9E389DC2CDB5246BEE002D6B8A7CD20A@qq.com>
Thanks for the response.
On Wed, 2024-05-29 at 12:19 +0800, Zhao Zhili wrote:
> > 在 2024年5月29日,上午5:56,Dmitrii Okunev <xaionaro@gmail.com> 写道:
> >
> > MediaCodec supports parameter "video-bitrate" to change the bitrate
> > on fly. This commit adds capability to use it.
> >
> > It adds option -bitrate_ctrl_socket to the encoder which makes
> > the encoder to create an UNIX socket and listen for messages
> > to change the bitrate.
>
> Thank you for your contribution. However, libavcodec as a library has a clear define of margin, IO such as socket cannot be put into libavcodec. Reconfigure bitrate should be done via libavcodec API.
This was the last resort, I tried to find another solution before posting this patch.
But of course I'll gladly adapt the solution: could you give examples/pointers on how to change values via libavcodec API on fly in ffmpeg?
Best regards, Dmitrii.
_______________________________________________
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:[~2024-05-29 11:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-27 12:49 Dmitrii Okunev
2024-05-28 15:38 ` Andrew Sayers
2024-05-28 21:56 ` Dmitrii Okunev
2024-05-29 4:19 ` Zhao Zhili
2024-05-29 11:45 ` Dmitrii Okunev [this message]
2024-05-28 21:57 ` Dmitrii Okunev
2024-05-28 22:08 ` Dmitrii Okunev
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=a38d617a6cf13c1eff64f891bc367662b1acceb5.camel@gmail.com \
--to=xaionaro@gmail.com \
--cc=ffmpeg-devel@ffmpeg.org \
--cc=quinkblack@foxmail.com \
--cc=xaionaro@dx.center \
/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