From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ffbox0-bg.mplayerhq.hu (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTP id 96C6340A8A for ; Thu, 5 May 2022 09:13:57 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 2021568B3C1; Thu, 5 May 2022 12:13:55 +0300 (EEST) Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id BC81868B3AA for ; Thu, 5 May 2022 12:13:46 +0300 (EEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1651742032; x=1683278032; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=Ei8JUkL2lyh3BF9/RxFfugMKNCQrFAz5Ehk4nqytHSY=; b=kaSH0pR5uIjw2YdxLzj6j8LdWrNqOdWK8IFU+jbpkCLgj+gls+N2MCXd v08Zkkb/I/gBgGNa+RD5eSuNqG9T/I5td1NBVTusuUfp+qtbiiDESzAZe aYDY9V4+ASNtKAzJQV2ZgrD1C3R2sSRHZU2aOAo95FxzDje3EwZ2OF9MO cKliIG/TBXY2qxTnt/e/pCSfGvKS8h9AlLFgXMg0M7SwWXNVBvUkjDI34 UrrATjU8wmIRM9PZSMXHQdOGlRu0r8KRTxmdU6vRkJHX9/wFRJ3EfDRS/ V2M5pVwLk0uJ4dctNGGgjlcV+7FoRO0MrEiPTpEb5GxY08fDPjq20RjVL w==; X-IronPort-AV: E=McAfee;i="6400,9594,10337"; a="266892140" X-IronPort-AV: E=Sophos;i="5.91,200,1647327600"; d="scan'208";a="266892140" Received: from orsmga007.jf.intel.com ([10.7.209.58]) by fmsmga104.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 05 May 2022 02:13:39 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.91,200,1647327600"; d="scan'208";a="563152020" Received: from t.sh.intel.com ([10.239.159.147]) by orsmga007.jf.intel.com with ESMTP; 05 May 2022 02:13:38 -0700 From: Fei Wang To: ffmpeg-devel@ffmpeg.org Date: Thu, 5 May 2022 17:07:15 +0800 Message-Id: <20220505090715.2016246-2-fei.w.wang@intel.com> X-Mailer: git-send-email 2.25.1 In-Reply-To: <20220505090715.2016246-1-fei.w.wang@intel.com> References: <20220505090715.2016246-1-fei.w.wang@intel.com> MIME-Version: 1.0 Subject: [FFmpeg-devel] [PATCH v7 2/2] doc/vaapi_encode: add documentations for max_frame_size X-BeenThere: ffmpeg-devel@ffmpeg.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FFmpeg development discussions and patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: FFmpeg development discussions and patches Cc: Fei Wang , Linjie Fu Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: From: Linjie Fu Add docs for max_frame_size option. Signed-off-by: Linjie Fu Signed-off-by: Fei Wang --- 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".