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

[Xiang, Haihao]

On Wed, 2020-09-16 at 20:44 +0000, Soft Works wrote:
> > -----Original Message-----
> > From: ffmpeg-devel <ffmpeg-devel-bounces at ffmpeg.org> On Behalf Of
> > Xiang, Haihao
> > Sent: Wednesday, September 16, 2020 10:30 AM
> > To: ffmpeg-devel at ffmpeg.org
> > Subject: Re: [FFmpeg-devel] [PATCH 0/6] qsv: Fix compiler errors when using
> > libmfx 2.0 (oneVPL)
> > 
> > On Wed, 2020-09-16 at 08:12 +0000, Soft Works wrote:
> > > > -----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?
> > 
> > You may refer to
> > https://spec.oneapi.com/versions/latest/elements/oneVPL/source/VPL_int
> > el_media_sdk.html#new-apis-in-onevpl
> >  for the new APIs/features.
> 
> Hi,
> 
> Thanks for the link. So, at this time there doesn't seem to be anything where
> ffmpeg would benefit from using it.  Hopefully there will be something
> interesting in the future.

It is in the todo list to use the new APIs.  The first step is to build FFmpeg
against oneVPL without compiler errors. 

> 
> > > 
> > > PS: How about VPP tone-mapping?
> > 
> > Do you mean libmfx based tone-mapping?
> 
> Yes, correct. The implementation already exists in VAAPI, but afaik it is not
> yet available via libmfx. Do you know about any plans regarding this?

I'm sorry I also don't know the plan about it. You'd be better to file an issue
on https://github.com/Intel-Media-SDK/MediaSDK/issues if you are interested onthis feature. 

Thanks
Haihao

> 
> Thanks and kind regards,
> softworkz
> _______________________________________________
> ffmpeg-devel mailing list
> ffmpeg-devel at ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
> 
> To unsubscribe, visit link above, or email
> ffmpeg-devel-request at ffmpeg.org with subject "unsubscribe".