Re: [FFmpeg-devel] [PATCH v3 1/4] lavc/hevc_refs: fix dpb logical for IRAP

2022-07-24 Thread Xiang, Haihao
On Mon, 2022-07-18 at 09:09 +, Xiang, Haihao wrote: > On Fri, 2022-07-15 at 13:06 +0800, Fei Wang wrote: > > From: Xu Guangxin > > > > According to C.5.2.2, item 2. When we got an IRAP, and the > > NoOutputOfPriorPicsFlag = 0, we need bump all outputable frames. > > > > Tested-by: Fei Wang

[FFmpeg-devel] [PATCH v3 2/2] ffmpeg_opt: consider HW acceleration method when selecting decoder

2022-07-24 Thread Xiang, Haihao
From: Haihao Xiang Usually a HW decoder is expected when user specifies a HW acceleration method via -hwaccel option, however the current implementation doesn't take HW acceleration method into account, it is possible to select a SW decoder. For example: $ ffmpeg -hwaccel vaapi -i av1.mp4 -f

[FFmpeg-devel] [PATCH v3 1/2] ffmpeg_opt: select a decoder after getting values for per-stream hwdec options

2022-07-24 Thread Xiang, Haihao
From: Haihao Xiang After applying this patch, the desired HW acceleration method is known before selecting decoder, so we may take HW acceleration method into account when selecting decoder for input stream in the next commit There should be no functional changes in this patch Signed-off-by:

[FFmpeg-devel] [PATCH v12 13/13] configure: add --enable-libvpl option

2022-07-24 Thread Xiang, Haihao
From: Haihao Xiang This allows user to build FFmpeg against Intel oneVPL. oneVPL 2.6 is the required minimum version when building Intel oneVPL code. It will fail to run configure script if both libmfx and libvpl are enabled. It is recommended to use oneVPL for new work, even for currently

[FFmpeg-devel] [PATCH v12 12/13] lavfi/qsv: create mfx session using oneVPL for qsv filters

2022-07-24 Thread Xiang, Haihao
From: Haihao Xiang Use the mfxLoader handle in qsv hwdevice to create mfx session for qsv filters. This is in preparation for oneVPL support --- libavfilter/qsvvpp.c | 109 --- libavfilter/qsvvpp.h | 5 ++ libavfilter/vf_deinterlace_qsv.c |

[FFmpeg-devel] [PATCH v12 06/13] qsvenc: restrict multi-frame encode to MFX_VERSION < 2.0

2022-07-24 Thread Xiang, Haihao
From: Haihao Xiang 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 ---

[FFmpeg-devel] [PATCH v12 10/13] lavu/hwcontext_qsv: make qsv hwdevice works with oneVPL

2022-07-24 Thread Xiang, Haihao
From: Haihao Xiang In oneVPL, MFXLoad() and MFXCreateSession() are required to create a workable mfx session[1] Add config filters for D3D9/D3D11 session (galinart) The default device is changed to d3d11va for oneVPL when both d3d11va and dxva2 are enabled on Microsoft Windows This is in

[FFmpeg-devel] [PATCH v12 11/13] lavc/qsv: create mfx session using oneVPL for decoding/encoding

2022-07-24 Thread Xiang, Haihao
From: Haihao Xiang If qsv hwdevice is available, use the mfxLoader handle in qsv hwdevice to create mfx session. Otherwise create mfx session with a new mfxLoader handle. This is in preparation for oneVPL support --- libavcodec/qsv.c | 226 +++---

[FFmpeg-devel] [PATCH v12 09/13] lavu/hwcontext_qsv: add loader field to AVQSVDeviceContext

2022-07-24 Thread Xiang, Haihao
From: Haihao Xiang In oneVPL, a valid mfxLoader handle is needed when creating mfx session for decoding, encoding and processing[1], so add loader field to AVQSVDeviceContext. User should fill this field before calling av_hwdevice_ctx_init() if using oneVPL This is in preparation for oneVPL

[FFmpeg-devel] [PATCH v12 08/13] qsv: restrict OPAQUE memory to MFX_VERSION < 2.0

2022-07-24 Thread Xiang, Haihao
From: Haihao Xiang OPAQUE memory 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 ---

[FFmpeg-devel] [PATCH v12 07/13] qsvenc: restrict MFX_RATECONTROL_LA_EXT to MFX_VERSION < 2.0

2022-07-24 Thread Xiang, Haihao
From: Haihao Xiang MFX_RATECONTROL_LA_EXT 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

[FFmpeg-devel] [PATCH v12 05/13] qsv: restrict audio related code to MFX_VERSION < 2.0

2022-07-24 Thread Xiang, Haihao
From: Haihao Xiang Audio 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 ---

[FFmpeg-devel] [PATCH v12 04/13] qsv: restrict user plugin to MFX_VERSION < 2.0

2022-07-24 Thread Xiang, Haihao
From: Haihao Xiang User plugin 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 ---

[FFmpeg-devel] [PATCH v12 03/13] qsv: remove mfx/ prefix from mfx headers

2022-07-24 Thread Xiang, Haihao
From: Haihao Xiang The following Cflags has been added to libmfx.pc, so mfx/ prefix is no longer needed when including mfx headers in FFmpeg. Cflags: -I${includedir} -I${includedir}/mfx Some old versions of libmfx have the following Cflags in libmfx.pc Cflags: -I${includedir} We may add

[FFmpeg-devel] [PATCH v12 02/13] configure: fix the check for MFX_CODEC_VP9

2022-07-24 Thread Xiang, Haihao
From: Haihao Xiang The data structures for VP9 in mfxvp9.h is wrapped by MFX_VERSION_NEXT, which means those data structures have never been used in a public release. Actually MFX_CODEC_VP9 and other VP9 stuffs are added in mfxstructures.h. In addition, mfxdefs.h is included in mfxvp9.h, so we

[FFmpeg-devel] [PATCH v12 01/13] configure: ensure --enable-libmfx uses libmfx 1.x

2022-07-24 Thread Xiang, Haihao
From: Haihao Xiang Intel's oneVPL is a successor to MediaSDK, but removed some obsolete features of MediaSDK[1], some early versions of oneVPL still use libmfx as library name[2]. However some of obsolete features, including OPAQUE memory, multi-frame encode, user plugins and LA_EXT rate control

[FFmpeg-devel] [PATCH v12 00/13] make QSV works with the Intel's oneVPL

2022-07-24 Thread Xiang, Haihao
From: Haihao Xiang The oneAPI Video Processing Library (oneVPL) is a single interface for encode, decode and video processing[1][2]. oneVPL is a successor to Intel(R) Media SDK, but removed obsolete features. Intel(R) Media SDK lifetime comes to an end now, new features for new Intel Gen

[FFmpeg-devel] [PATCH] avcodec/x86/pngdsp: Remove obsolete ff_add_bytes_l2_mmx()

2022-07-24 Thread Andreas Rheinhardt
It is overridden by ff_add_bytes_l2_sse2() on any non-ancient CPU. Signed-off-by: Andreas Rheinhardt --- libavcodec/x86/pngdsp.asm| 16 ++-- libavcodec/x86/pngdsp_init.c | 7 --- 2 files changed, 2 insertions(+), 21 deletions(-) diff --git a/libavcodec/x86/pngdsp.asm

Re: [FFmpeg-devel] [PATCH] qsv: Update ffmpeg qsv_errors to recognize GPU hang

2022-07-24 Thread Xiang, Haihao
On Fri, 2022-07-22 at 11:06 -0700, Dmitry Rogozhkin wrote: > GPU hang is one of the most typical errors on Intel GPUs in > case something goes wrong. It's important to recognize it > explicitly for easier bugs triage. Also, this error code > can be used to trigger GPU recovery path in self-written

Re: [FFmpeg-devel] [PATCH 14/18] avcodec/hevcdec: Don't allocate redundant HEVCContexts

2022-07-24 Thread Andreas Rheinhardt
Michael Niedermayer: > On Sat, Jul 23, 2022 at 11:42:23PM +0200, Andreas Rheinhardt wrote: >> Michael Niedermayer: >>> On Sat, Jul 23, 2022 at 07:44:40AM +0200, Andreas Rheinhardt wrote: Andreas Rheinhardt: > Michael Niedermayer: >> On Sat, Jul 02, 2022 at 08:32:06AM +0200, Andreas

Re: [FFmpeg-devel] [PATCH 14/18] avcodec/hevcdec: Don't allocate redundant HEVCContexts

2022-07-24 Thread Michael Niedermayer
On Sat, Jul 23, 2022 at 11:42:23PM +0200, Andreas Rheinhardt wrote: > Michael Niedermayer: > > On Sat, Jul 23, 2022 at 07:44:40AM +0200, Andreas Rheinhardt wrote: > >> Andreas Rheinhardt: > >>> Michael Niedermayer: > On Sat, Jul 02, 2022 at 08:32:06AM +0200, Andreas Rheinhardt wrote: > >

Re: [FFmpeg-devel] [PATCH] configure: properly require libx264 if enabled

2022-07-24 Thread Jan Ekström
On Sun, Jul 24, 2022 at 5:48 PM Jan Ekström wrote: > > On Sun, Jul 24, 2022 at 2:04 PM Jan Ekström wrote: > > > > On Sun, Jul 24, 2022 at 1:12 PM Marvin Scholz wrote: > > > > > > When libx264 can not be found even though it is enabled, it should error > > > out properly instead of silently

Re: [FFmpeg-devel] Contact of the Technical Committee

2022-07-24 Thread Jean-Baptiste Kempf
Have you tried tc@ffmpeg.o.. ? jb On Sun, 24 Jul 2022, at 17:12, Nicolas George wrote: > Hi. > > What is the address to ask a question to the technical committee? > > Thanks, > > -- > Nicolas George > > ___ > ffmpeg-devel mailing list >

[FFmpeg-devel] [PATCH] fate/imf: Rename IMF fate-target

2022-07-24 Thread Andreas Rheinhardt
It conflicts with the name of the test using the testtool in libavformat.mak. Fixes ticket #9841. Signed-off-by: Andreas Rheinhardt --- Other naming suggestions welcome. tests/fate/imf.mak | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tests/fate/imf.mak

Re: [FFmpeg-devel] [PATCH v5 00/25] Subtitle Filtering 2022

2022-07-24 Thread Soft Works
> -Original Message- > From: ffmpeg-devel On Behalf Of > Nicolas George > Sent: Sunday, July 24, 2022 5:10 PM > To: FFmpeg development discussions and patches de...@ffmpeg.org> > Subject: Re: [FFmpeg-devel] [PATCH v5 00/25] Subtitle Filtering 2022 > > I suspect that if I were to do

Re: [FFmpeg-devel] [PATCH v5 00/25] Subtitle Filtering 2022

2022-07-24 Thread Soft Works
> -Original Message- > From: ffmpeg-devel On Behalf Of > Nicolas George > Sent: Sunday, July 24, 2022 5:10 PM > To: FFmpeg development discussions and patches de...@ffmpeg.org> > Subject: Re: [FFmpeg-devel] [PATCH v5 00/25] Subtitle Filtering 2022 > > I hesitated a long time before

[FFmpeg-devel] Contact of the Technical Committee

2022-07-24 Thread Nicolas George
Hi. What is the address to ask a question to the technical committee? Thanks, -- Nicolas George signature.asc Description: PGP signature ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To

Re: [FFmpeg-devel] [PATCH v5 00/25] Subtitle Filtering 2022

2022-07-24 Thread Nicolas George
I hesitated a long time before replying, but all considering, at this point expressing what is weighing on my heart cannot make things worse. Michael Niedermayer (12022-07-03): > What is the timeline for the audio+video merge ? I cannot give a timeline because I do not work on FFmpeg on a

Re: [FFmpeg-devel] [PATCH] configure: properly require libx264 if enabled

2022-07-24 Thread Jan Ekström
On Sun, Jul 24, 2022 at 2:04 PM Jan Ekström wrote: > > On Sun, Jul 24, 2022 at 1:12 PM Marvin Scholz wrote: > > > > When libx264 can not be found even though it is enabled, it should error > > out properly instead of silently disabling it. > > --- > > configure | 2 +- > > 1 file changed, 1

Re: [FFmpeg-devel] [PATCH] configure: properly require libx264 if enabled

2022-07-24 Thread Jan Ekström
On Sun, Jul 24, 2022 at 1:12 PM Marvin Scholz wrote: > > When libx264 can not be found even though it is enabled, it should error > out properly instead of silently disabling it. > --- > configure | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/configure b/configure >

[FFmpeg-devel] [PATCH] configure: properly require libx264 if enabled

2022-07-24 Thread Marvin Scholz
When libx264 can not be found even though it is enabled, it should error out properly instead of silently disabling it. --- configure | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/configure b/configure index 46f6490a64..6629d14099 100755 --- a/configure +++ b/configure @@