From: Damiano Galassi via ffmpeg-devel <ffmpeg-devel@ffmpeg.org> To: ffmpeg-devel@ffmpeg.org Cc: Damiano Galassi <code@ffmpeg.org> Subject: [FFmpeg-devel] [PATCH] libavcodec/qsvenc.c: update has_b_frames value after initialization of encoder (PR #20463) Date: Mon, 08 Sep 2025 08:14:06 -0000 Message-ID: <175731924688.25.10834054636849312853@463a07221176> (raw) PR #20463 opened by Damiano Galassi (galad) URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20463 Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20463.patch The original patch was sent by Artem Galin (whom worked at Intel at the time) to HandBrake, but it didn't make it upstream. It sets the context has_b_frames value just like is done in almost all the other encoders that uses b-frames. >From 07ce64d0e8ed3874dd0f031b7e928b854c89b3ba Mon Sep 17 00:00:00 2001 From: galinart <artem.galin@intel.com> Date: Thu, 17 Oct 2024 16:17:36 +0100 Subject: [PATCH] libavcodec/qsvenc.c: update has_b_frames value after initialization of encoder --- libavcodec/qsvenc.c | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/libavcodec/qsvenc.c b/libavcodec/qsvenc.c index 318a99e2a1..039a108aae 100644 --- a/libavcodec/qsvenc.c +++ b/libavcodec/qsvenc.c @@ -1842,6 +1842,13 @@ int ff_qsv_enc_init(AVCodecContext *avctx, QSVEncContext *q) return ret; } + // Update AVCodecContext with actual encoding parameters + mfxInfoMFX *info = &q->param.mfx; + avctx->has_b_frames = 0; + if (info->GopRefDist > 1) { + avctx->has_b_frames = info->GopRefDist - 1; + } + q->avctx = avctx; return 0; -- 2.49.1 _______________________________________________ ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
reply other threads:[~2025-09-08 8:14 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=175731924688.25.10834054636849312853@463a07221176 \ --to=ffmpeg-devel@ffmpeg.org \ --cc=code@ffmpeg.org \ /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