From: "Xiang, Haihao" <haihao.xiang-at-intel.com@ffmpeg.org> To: "ffmpeg-devel@ffmpeg.org" <ffmpeg-devel@ffmpeg.org> Cc: "nowrep@gmail.com" <nowrep@gmail.com> Subject: Re: [FFmpeg-devel] [PATCH] lavc/vaapi_encode: Add filler_data option Date: Mon, 7 Aug 2023 01:25:29 +0000 Message-ID: <a6b5c6b7f03d8a44a743db14dcbe4b6e7d717771.camel@intel.com> (raw) In-Reply-To: <20230805120745.216285-1-nowrep@gmail.com> On Sa, 2023-08-05 at 14:06 +0200, David Rosca wrote: > --- > libavcodec/vaapi_encode.c | 1 + > libavcodec/vaapi_encode.h | 9 ++++++++- > 2 files changed, 9 insertions(+), 1 deletion(-) > > diff --git a/libavcodec/vaapi_encode.c b/libavcodec/vaapi_encode.c > index bfca315a7a..f161c76304 100644 > --- a/libavcodec/vaapi_encode.c > +++ b/libavcodec/vaapi_encode.c > @@ -1860,6 +1860,7 @@ rc_mode_found: > #if VA_CHECK_VERSION(1, 3, 0) > .quality_factor = rc_quality, > #endif > + .rc_flags.bits.disable_bit_stuffing = !ctx->filler_data, > }; > vaapi_encode_add_global_param(avctx, > VAEncMiscParameterTypeRateControl, > diff --git a/libavcodec/vaapi_encode.h b/libavcodec/vaapi_encode.h > index a1e639f56b..a2170cb8b0 100644 > --- a/libavcodec/vaapi_encode.h > +++ b/libavcodec/vaapi_encode.h > @@ -198,6 +198,9 @@ typedef struct VAAPIEncodeContext { > // Max Frame Size > int max_frame_size; > > + // Filler Data > + int filler_data; > + > // Explicitly set RC mode (otherwise attempt to pick from > // available modes). > int explicit_rc_mode; > @@ -490,7 +493,11 @@ int ff_vaapi_encode_close(AVCodecContext *avctx); > { "max_frame_size", \ > "Maximum frame size (in bytes)",\ > OFFSET(common.max_frame_size), AV_OPT_TYPE_INT, \ > - { .i64 = 0 }, 0, INT_MAX, FLAGS } > + { .i64 = 0 }, 0, INT_MAX, FLAGS }, \ > + { "filler_data", \ > + "Enable filler data", \ > + OFFSET(common.filler_data), AV_OPT_TYPE_BOOL, \ > + { .i64 = 1 }, 0, 1, FLAGS } Could you add the description about this new option in encoders.texi ? Thanks Haihao > > #define VAAPI_ENCODE_RC_MODE(name, desc) \ > { #name, desc, 0, AV_OPT_TYPE_CONST, { .i64 = RC_MODE_ ## name }, \ _______________________________________________ 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".
prev parent reply other threads:[~2023-08-07 1:25 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-05 12:06 David Rosca 2023-08-07 1:25 ` Xiang, Haihao [this message]
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=a6b5c6b7f03d8a44a743db14dcbe4b6e7d717771.camel@intel.com \ --to=haihao.xiang-at-intel.com@ffmpeg.org \ --cc=ffmpeg-devel@ffmpeg.org \ --cc=nowrep@gmail.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