| Message ID | 20200916064457.181230-1-haihao.xiang@intel.com |
|---|---|
| Headers | show |
| Series | qsv: Fix compiler errors when using libmfx 2.0 (oneVPL) | expand |
> -----Original Message----- > From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of > Haihao Xiang > Sent: Wednesday, September 16, 2020 8:45 AM > To: ffmpeg-devel@ffmpeg.org > Cc: Haihao Xiang <haihao.xiang@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
On Wed, 2020-09-16 at 08:12 +0000, Soft Works wrote: > > -----Original Message----- > > From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of > > Haihao Xiang > > Sent: Wednesday, September 16, 2020 8:45 AM > > To: ffmpeg-devel@ffmpeg.org > > Cc: Haihao Xiang <haihao.xiang@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_intel_media_sdk.html#new-apis-in-onevpl for the new APIs/features. > > PS: How about VPP tone-mapping? Do you mean libmfx based tone-mapping? Thanks Haihao > > Kind regards, > softworkz > _______________________________________________ > 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".
> -----Original Message----- > From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of > Xiang, Haihao > Sent: Wednesday, September 16, 2020 10:30 AM > To: ffmpeg-devel@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@ffmpeg.org> On Behalf Of > > > Haihao Xiang > > > Sent: Wednesday, September 16, 2020 8:45 AM > > > To: ffmpeg-devel@ffmpeg.org > > > Cc: Haihao Xiang <haihao.xiang@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. > > > > 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? Thanks and kind regards, softworkz
On Wed, 2020-09-16 at 20:44 +0000, Soft Works wrote: > > -----Original Message----- > > From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of > > Xiang, Haihao > > Sent: Wednesday, September 16, 2020 10:30 AM > > To: ffmpeg-devel@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@ffmpeg.org> On Behalf Of > > > > Haihao Xiang > > > > Sent: Wednesday, September 16, 2020 8:45 AM > > > > To: ffmpeg-devel@ffmpeg.org > > > > Cc: Haihao Xiang <haihao.xiang@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@ffmpeg.org > https://ffmpeg.org/mailman/listinfo/ffmpeg-devel > > To unsubscribe, visit link above, or email > ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
Hi Mark, Zhong, Could you please review this patchset too when you get a chance? Thanks Haihao > 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.html > The oneVPL source code: > https://github.com/oneapi-src/oneVPL > > This patchset fixes compiler errors when building FFmpeg against oneVPL > > Note this patchset includes some patches in the FFmpeg archives: > http://ffmpeg.org/pipermail/ffmpeg-devel/2020-August/268141.html > http://ffmpeg.org/pipermail/ffmpeg-devel/2020-September/269334.html > > 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) > > configure | 15 +++++-- > fftools/ffmpeg_qsv.c | 2 +- > libavcodec/qsv.c | 21 +++++++-- > libavcodec/qsv.h | 4 +- > libavcodec/qsv_internal.h | 4 +- > libavcodec/qsvdec.c | 11 ++++- > libavcodec/qsvdec.h | 2 +- > libavcodec/qsvdec_h2645.c | 2 +- > libavcodec/qsvdec_other.c | 2 +- > libavcodec/qsvenc.c | 25 ++++++++++- > libavcodec/qsvenc.h | 6 ++- > libavcodec/qsvenc_h264.c | 2 +- > libavcodec/qsvenc_hevc.c | 2 +- > libavcodec/qsvenc_jpeg.c | 2 +- > libavcodec/qsvenc_mpeg2.c | 2 +- > libavcodec/qsvenc_vp9.c | 2 +- > libavfilter/qsvvpp.c | 24 +++++++++- > libavfilter/qsvvpp.h | 4 +- > libavfilter/vf_deinterlace_qsv.c | 58 +++++++++++++----------- > libavfilter/vf_scale_qsv.c | 76 ++++++++++++++++++-------------- > libavutil/hwcontext_opencl.c | 2 +- > libavutil/hwcontext_qsv.c | 58 +++++++++++++++++------- > libavutil/hwcontext_qsv.h | 2 +- > 23 files changed, 225 insertions(+), 103 deletions(-) >
On 16/09/2020 07:44, Haihao Xiang wrote: > 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.html > The oneVPL source code: > https://github.com/oneapi-src/oneVPL > > This patchset fixes compiler errors when building FFmpeg against oneVPL > > Note this patchset includes some patches in the FFmpeg archives: > http://ffmpeg.org/pipermail/ffmpeg-devel/2020-August/268141.html > http://ffmpeg.org/pipermail/ffmpeg-devel/2020-September/269334.html > > 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) > > configure | 15 +++++-- > fftools/ffmpeg_qsv.c | 2 +- > libavcodec/qsv.c | 21 +++++++-- > libavcodec/qsv.h | 4 +- > libavcodec/qsv_internal.h | 4 +- > libavcodec/qsvdec.c | 11 ++++- > libavcodec/qsvdec.h | 2 +- > libavcodec/qsvdec_h2645.c | 2 +- > libavcodec/qsvdec_other.c | 2 +- > libavcodec/qsvenc.c | 25 ++++++++++- > libavcodec/qsvenc.h | 6 ++- > libavcodec/qsvenc_h264.c | 2 +- > libavcodec/qsvenc_hevc.c | 2 +- > libavcodec/qsvenc_jpeg.c | 2 +- > libavcodec/qsvenc_mpeg2.c | 2 +- > libavcodec/qsvenc_vp9.c | 2 +- > libavfilter/qsvvpp.c | 24 +++++++++- > libavfilter/qsvvpp.h | 4 +- > libavfilter/vf_deinterlace_qsv.c | 58 +++++++++++++----------- > libavfilter/vf_scale_qsv.c | 76 ++++++++++++++++++-------------- > libavutil/hwcontext_opencl.c | 2 +- > libavutil/hwcontext_qsv.c | 58 +++++++++++++++++------- > libavutil/hwcontext_qsv.h | 2 +- > 23 files changed, 225 insertions(+), 103 deletions(-) Can you explain the compatibility effects here? In particular: If you build against oneVPL, does everything still work on old MSDK setups? (In particular, those like Haswell which are technically out of support but still very widely used.) If you build against MSDK, does everything still work on a oneVPL setup? - Mark
On Tue, 2020-09-29 at 16:09 +0100, Mark Thompson wrote: > On 16/09/2020 07:44, Haihao Xiang wrote: > > 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.html > > The oneVPL source code: > > https://github.com/oneapi-src/oneVPL > > > > This patchset fixes compiler errors when building FFmpeg against oneVPL > > > > Note this patchset includes some patches in the FFmpeg archives: > > http://ffmpeg.org/pipermail/ffmpeg-devel/2020-August/268141.html > > http://ffmpeg.org/pipermail/ffmpeg-devel/2020-September/269334.html > > > > 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) > > > > configure | 15 +++++-- > > fftools/ffmpeg_qsv.c | 2 +- > > libavcodec/qsv.c | 21 +++++++-- > > libavcodec/qsv.h | 4 +- > > libavcodec/qsv_internal.h | 4 +- > > libavcodec/qsvdec.c | 11 ++++- > > libavcodec/qsvdec.h | 2 +- > > libavcodec/qsvdec_h2645.c | 2 +- > > libavcodec/qsvdec_other.c | 2 +- > > libavcodec/qsvenc.c | 25 ++++++++++- > > libavcodec/qsvenc.h | 6 ++- > > libavcodec/qsvenc_h264.c | 2 +- > > libavcodec/qsvenc_hevc.c | 2 +- > > libavcodec/qsvenc_jpeg.c | 2 +- > > libavcodec/qsvenc_mpeg2.c | 2 +- > > libavcodec/qsvenc_vp9.c | 2 +- > > libavfilter/qsvvpp.c | 24 +++++++++- > > libavfilter/qsvvpp.h | 4 +- > > libavfilter/vf_deinterlace_qsv.c | 58 +++++++++++++----------- > > libavfilter/vf_scale_qsv.c | 76 ++++++++++++++++++-------------- > > libavutil/hwcontext_opencl.c | 2 +- > > libavutil/hwcontext_qsv.c | 58 +++++++++++++++++------- > > libavutil/hwcontext_qsv.h | 2 +- > > 23 files changed, 225 insertions(+), 103 deletions(-) > > Can you explain the compatibility effects here? In particular: > > If you build against oneVPL, does everything still work on old MSDK > setups? (In particular, those like Haswell which are technically out of > support but still very widely used.) > > If you build against MSDK, does everything still work on a oneVPL setup? The mfx dispatcher from oneVPL works well with the legacy MSDK implementation (E.g. libmfxhw64.so) except the removed features. The soname is libmfx.so.2 for oneVPL dispatcher, libmfx.so.1 for legacy MedSDK, you can't use legacy MSDK dispatcher at runtime if you build FFmpeg against oneVPL. It doesn't work too if building against legacy MSDK and use oneVPL dispatcher at runtime. Thanks Haihao > > - Mark > _______________________________________________ > 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".
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.html The oneVPL source code: https://github.com/oneapi-src/oneVPL This patchset fixes compiler errors when building FFmpeg against oneVPL Note this patchset includes some patches in the FFmpeg archives: http://ffmpeg.org/pipermail/ffmpeg-devel/2020-August/268141.html http://ffmpeg.org/pipermail/ffmpeg-devel/2020-September/269334.html 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) configure | 15 +++++-- fftools/ffmpeg_qsv.c | 2 +- libavcodec/qsv.c | 21 +++++++-- libavcodec/qsv.h | 4 +- libavcodec/qsv_internal.h | 4 +- libavcodec/qsvdec.c | 11 ++++- libavcodec/qsvdec.h | 2 +- libavcodec/qsvdec_h2645.c | 2 +- libavcodec/qsvdec_other.c | 2 +- libavcodec/qsvenc.c | 25 ++++++++++- libavcodec/qsvenc.h | 6 ++- libavcodec/qsvenc_h264.c | 2 +- libavcodec/qsvenc_hevc.c | 2 +- libavcodec/qsvenc_jpeg.c | 2 +- libavcodec/qsvenc_mpeg2.c | 2 +- libavcodec/qsvenc_vp9.c | 2 +- libavfilter/qsvvpp.c | 24 +++++++++- libavfilter/qsvvpp.h | 4 +- libavfilter/vf_deinterlace_qsv.c | 58 +++++++++++++----------- libavfilter/vf_scale_qsv.c | 76 ++++++++++++++++++-------------- libavutil/hwcontext_opencl.c | 2 +- libavutil/hwcontext_qsv.c | 58 +++++++++++++++++------- libavutil/hwcontext_qsv.h | 2 +- 23 files changed, 225 insertions(+), 103 deletions(-)