From: Anton Kesy via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: Anton Kesy <code@ffmpeg.org>
Subject: [FFmpeg-devel] [PR] avcodec/qsvenc: add unsupported codec level log (PR #21376)
Date: Mon, 05 Jan 2026 01:50:50 -0000
Message-ID: <176757785073.25.78374611642325482@4457048688e7> (raw)
PR #21376 opened by Anton Kesy (antonkesy)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/21376
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/21376.patch
Adds missing log of struct mfxInfoMFX member: codec level.
>From e931cae425f9e87fa1573928f563611151dd81d0 Mon Sep 17 00:00:00 2001
From: Anton Kesy <anton@kesy.de>
Date: Mon, 5 Jan 2026 02:48:24 +0100
Subject: [PATCH] avcodec/qsvenc: add unsupported codec level log
Adds missing log of struct mfxInfoMFX member: codec level.
Signed-off-by: Anton Kesy <anton@kesy.de>
---
libavcodec/qsvenc.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/libavcodec/qsvenc.c b/libavcodec/qsvenc.c
index fc1b8795d8..db16aa80de 100644
--- a/libavcodec/qsvenc.c
+++ b/libavcodec/qsvenc.c
@@ -683,6 +683,8 @@ static int check_enc_param(AVCodecContext *avctx, QSVEncContext *q)
av_log(avctx, AV_LOG_ERROR, "Selected ratecontrol mode is unsupported\n");
if (UNMATCH(LowPower))
av_log(avctx, AV_LOG_ERROR, "Low power mode is unsupported\n");
+ if (UNMATCH(CodecLevel))
+ av_log(avctx, AV_LOG_ERROR, "Current codec level is unsupported\n");
if (UNMATCH(FrameInfo.FrameRateExtN) || UNMATCH(FrameInfo.FrameRateExtD))
av_log(avctx, AV_LOG_ERROR, "Current frame rate is unsupported\n");
if (UNMATCH(FrameInfo.PicStruct))
--
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:[~2026-01-05 1:51 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=176757785073.25.78374611642325482@4457048688e7 \
--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