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 DCF6C40203 for ; Fri, 22 Apr 2022 05:42:57 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 8959C68B3DD; Fri, 22 Apr 2022 08:42:52 +0300 (EEST) Received: from mga06.intel.com (mga06b.intel.com [134.134.136.31]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 635D968B3C5 for ; Fri, 22 Apr 2022 08:42:45 +0300 (EEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1650606170; x=1682142170; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=9bIXngKWuq/yoHAFWnVXi4d4F+WaMwLsRXYwk6pQq9Q=; b=YpqU1gUGNUg8ZjhCKnnCtiywsFLAOo3IRvJwX5dWbcgONNBHyf9wv7qS sdKW+Y8M0ObXijcUNkAQsN33Hy4CAzjEPnB7sCtCXwhLLTZJxCp60k5dq LQqBXKmf++PlueLcY7mfbOpQheG1r5owr7+EMcrjioofS7JRw2iUkad01 308lnV6Lkcd564O8UsxPkkYSHXUPciCwtbRcyayOYma/yrLUoPKYm35CL 0exsg/Us8i/Fs32o+l/mqVZnKSLZXAGswDOJ40sucEVtlwMwlTJnLE+XO f8FADmP1bJCGmiMmgA3Q8cplPPFAEeDwNpIzNf0Q0QZhBIJJVr+Zz59B+ Q==; X-IronPort-AV: E=McAfee;i="6400,9594,10324"; a="325030589" X-IronPort-AV: E=Sophos;i="5.90,280,1643702400"; d="scan'208";a="325030589" Received: from orsmga007.jf.intel.com ([10.7.209.58]) by orsmga104.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 21 Apr 2022 22:42:38 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.90,280,1643702400"; d="scan'208";a="556182274" Received: from t.sh.intel.com ([10.239.159.147]) by orsmga007.jf.intel.com with ESMTP; 21 Apr 2022 22:42:37 -0700 From: Fei Wang To: ffmpeg-devel@ffmpeg.org Date: Fri, 22 Apr 2022 13:36:15 +0800 Message-Id: <20220422053615.1638095-2-fei.w.wang@intel.com> X-Mailer: git-send-email 2.25.1 In-Reply-To: <20220422053615.1638095-1-fei.w.wang@intel.com> References: <20220422053615.1638095-1-fei.w.wang@intel.com> MIME-Version: 1.0 Subject: [FFmpeg-devel] [PATCH v5 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 aac9f25e55..d66713b69f 100644 --- a/doc/encoders.texi +++ b/doc/encoders.texi @@ -3630,6 +3630,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".