Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH v11 06/13] qsvenc: support multi-frame encode when MFX_VERSION < 2.0
Date: Thu, 21 Jul 2022 00:45:09 +0200
Message-ID: <DB6PR0101MB2214C73476A41BA41C04CA448F8E9@DB6PR0101MB2214.eurprd01.prod.exchangelabs.com> (raw)
In-Reply-To: <20220720084006.5033-7-haihao.xiang@intel.com>

Xiang, Haihao:
> From: Haihao Xiang <haihao.xiang@intel.com>
> 
> Multi-frame encode isn't supported for MFX_VERSION >= 2.0[1][2]. This is
> in preparation for oneVPL support
> 
> [1] https://spec.oneapi.io/versions/latest/elements/oneVPL/source/VPL_intel_media_sdk.html#msdk-full-name-feature-removals
> [2] https://github.com/oneapi-src/oneVPL
> ---
>  libavcodec/qsvenc.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/libavcodec/qsvenc.h b/libavcodec/qsvenc.h
> index 4cadc38a59..40e2f65eff 100644
> --- a/libavcodec/qsvenc.h
> +++ b/libavcodec/qsvenc.h
> @@ -44,7 +44,7 @@
>  #else
>  #define QSV_HAVE_AVBR   0
>  #define QSV_HAVE_VCM    0
> -#define QSV_HAVE_MF     1
> +#define QSV_HAVE_MF     !QSV_ONEVPL
>  #endif
>  
>  #define QSV_COMMON_OPTS \

"support multi-frame encode when MFX_VERSION < 2.0" sounds as if you
were adding support for multi-frame encode. But the remaining commit
message makes it clear that you are actually restricting multi-frame
encode to MFX_VERSION < 2.0. So maybe you should reword the commit title
accordingly (some other commits in this patchset suffer from the same
defect).

- Andreas
_______________________________________________
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".

  reply	other threads:[~2022-07-20 22:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-20  8:39 [FFmpeg-devel] [PATCH v11 00/13] make QSV works with the Intel's oneVPL Xiang, Haihao
2022-07-20  8:39 ` [FFmpeg-devel] [PATCH v11 01/13] configure: ensure --enable-libmfx uses libmfx 1.x Xiang, Haihao
2022-07-20  8:39 ` [FFmpeg-devel] [PATCH v11 02/13] configure: fix the check for MFX_CODEC_VP9 Xiang, Haihao
2022-07-20  8:39 ` [FFmpeg-devel] [PATCH v11 03/13] qsv: remove mfx/ prefix from mfx headers Xiang, Haihao
2022-07-20  8:39 ` [FFmpeg-devel] [PATCH v11 04/13] qsv: load user plugin for MFX_VERSION < 2.0 Xiang, Haihao
2022-07-20  8:39 ` [FFmpeg-devel] [PATCH v11 05/13] qsv: build audio related code when " Xiang, Haihao
2022-07-20  8:39 ` [FFmpeg-devel] [PATCH v11 06/13] qsvenc: support multi-frame encode " Xiang, Haihao
2022-07-20 22:45   ` Andreas Rheinhardt [this message]
2022-07-21  5:20     ` Xiang, Haihao
2022-07-20  8:40 ` [FFmpeg-devel] [PATCH v11 07/13] qsvenc: support MFX_RATECONTROL_LA_EXT " Xiang, Haihao
2022-07-20  8:40 ` [FFmpeg-devel] [PATCH v11 08/13] qsv: support OPAQUE memory " Xiang, Haihao
2022-07-20  8:40 ` [FFmpeg-devel] [PATCH v11 09/13] lavu/hwcontext_qsv: add loader field to AVQSVDeviceContext Xiang, Haihao
2022-07-20  8:40 ` [FFmpeg-devel] [PATCH v11 10/13] lavu/hwcontext_qsv: make qsv hwdevice works with oneVPL Xiang, Haihao
2022-07-21 22:19   ` Mark Thompson
2022-07-22  3:10     ` Xiang, Haihao
2022-07-20  8:40 ` [FFmpeg-devel] [PATCH v11 11/13] lavc/qsv: create mfx session using oneVPL for decoding/encoding Xiang, Haihao
2022-07-20  8:40 ` [FFmpeg-devel] [PATCH v11 12/13] lavfi/qsv: create mfx session using oneVPL for qsv filters Xiang, Haihao
2022-07-20  8:40 ` [FFmpeg-devel] [PATCH v11 13/13] configure: add --enable-libvpl option Xiang, Haihao

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=DB6PR0101MB2214C73476A41BA41C04CA448F8E9@DB6PR0101MB2214.eurprd01.prod.exchangelabs.com \
    --to=andreas.rheinhardt@outlook.com \
    --cc=ffmpeg-devel@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