From: Fei Wang <fei.w.wang-at-intel.com@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: Fei Wang <fei.w.wang@intel.com>, Linjie Fu <linjie.fu@intel.com>
Subject: [FFmpeg-devel] [PATCH v7 2/2] doc/vaapi_encode: add documentations for max_frame_size
Date: Thu, 5 May 2022 17:07:15 +0800
Message-ID: <20220505090715.2016246-2-fei.w.wang@intel.com> (raw)
In-Reply-To: <20220505090715.2016246-1-fei.w.wang@intel.com>
From: Linjie Fu <linjie.fu@intel.com>
Add docs for max_frame_size option.
Signed-off-by: Linjie Fu <linjie.fu@intel.com>
Signed-off-by: Fei Wang <fei.w.wang@intel.com>
---
doc/encoders.texi | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/doc/encoders.texi b/doc/encoders.texi
index 966032a720..43f6288e33 100644
--- a/doc/encoders.texi
+++ b/doc/encoders.texi
@@ -3665,6 +3665,11 @@ performance. This option doesn't work if driver doesn't implement vaSyncBuffer
function. Please make sure there are enough hw_frames allocated if a large
number of async_depth is used.
+@item max_frame_size
+Set the allowed max size in bytes for each frame. If the frame size exceeds
+the limitation, encoder will adjust the QP value to control the frame size.
+Invalid in CQP rate control mode.
+
@item rc_mode
Set the rate control mode to use. A given driver may only support a subset of
modes.
--
2.25.1
_______________________________________________
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-05-05 9:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-05 9:07 [FFmpeg-devel] [PATCH v7 1/2] lavc/vaapi_encode: add support for maxframesize Fei Wang
2022-05-05 9:07 ` Fei Wang [this message]
2022-05-23 2:14 ` Wang, Fei W
2022-05-30 1:27 ` Xiang, Haihao
2022-06-06 6:16 ` Xiang, Haihao
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=20220505090715.2016246-2-fei.w.wang@intel.com \
--to=fei.w.wang-at-intel.com@ffmpeg.org \
--cc=fei.w.wang@intel.com \
--cc=ffmpeg-devel@ffmpeg.org \
--cc=linjie.fu@intel.com \
/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