[FFmpeg-devel] [PATCH 0/6] qsv: Fix compiler errors when using libmfx 2.0 (oneVPL)

[Soft Works]

> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces at ffmpeg.org> On Behalf Of
> Haihao Xiang
> Sent: Wednesday, September 16, 2020 8:45 AM
> To: ffmpeg-devel at ffmpeg.org
> Cc: Haihao Xiang <haihao.xiang at intel.com>
> Subject: [FFmpeg-devel] [PATCH 0/6] qsv: Fix compiler errors when using
> libmfx 2.0 (oneVPL)
> 
> The oneAPI Video Processing Library (oneVPL) is a single interface for
> encode, decode and video processing, the obsolete features in Intel Media
> Software Development Kit are removed from oneVPL.
> 
> The oneVPL specification:
> https://spec.oneapi.com/versions/latest/elements/oneVPL/source/index.ht
> ml
> The oneVPL source code:
> https://github.com/oneapi-src/oneVPL
> 
> Haihao Xiang (6):
>   qsv: add ${includedir}/mfx to the search path for old versions of
>     libmfx
>   qsv: libmfx no longer supports user plugin since version 2.0 (oneVPL)
>   qsv: libmfx no longer supports audio since version 2.0 (oneVPL)
>   qsvenc: libmfx no longer supports multi-frame encode since version 2.0
>     (oneVPL)
>   qsvenc: libmfx no longer supports MFX_RATECONTROL_LA_EXT since
> version
>     2.0 (oneVPL)
>   qsv: libmfx no longer supports OPAQUE memory since version 2.0
>     (oneVPL)

Hi,

MFX => ClearVideo => QuickSync => MediaSDK => oneVPL

Is there actually something new in "oneVPL 2.0" or is this just MSDK 1.34 with many things removed and once another name added?

PS: How about VPP tone-mapping?

Kind regards,
softworkz