v2022.1.0
New in this release
Added
- Updated oneVPL dispatcher to support API 2.6
- Added ONEVPL_PRIORITY_PATH for RT loading
- Extended multi-adapter to support most combinations of GPU hardware that works with Intel(R) Media SDK and oneVPL
- Updated documentation on working with multiple adapters using 2.x API
- Added support for extended device ID on legacy GPUs
- Added support for Intel® Arc™ A Series Graphics
- Added support for:
- Rocky Linux*
- Windows* 11
- Windows* Server 2022
- Microsoft Visual Studio* 2022
Changed
- Intel(R) Media SDK is loaded when DX9 is requested
Depreciated
- Support for Microsoft Visual Studio* 2017
Fixed
- MFXCloneSession is not functional on legacy GPU systems
- hello-encode not working on DG2 due to default input resolution
oneVPL 2022.1.0 has been updated to include functional and security updates. Users should update to the latest version.
Issues and Limitations
- On Ubuntu 20.04, during basekit install you may see a warning about missing OpenCL support. You can verify the graphics stack components are correctly installed by running one of the interop samples with -hw. See https://github.com/oneapi-src/oneVPL for more information.
C++/Python previews
- This is a preview release made available to gather feedback for API improvements. Compatibility with future releases is not guaranteed.
Dispatcher
- MFXInit() and MFXInitEx() functions have been deprecated in the 2.0 oneVPL Specification. Use MFXLoad() instead. See the transition guide for more details.
- If initialized with MFXInit() or MFXInitEx(), support is limited to the 1.x API and will load Intel(R) Media SDK hardware library rather than oneVPL hardware library.
- For legacy GPU hardware enabled by Intel(R) Media SDK, only API features up to 1.35 are available, even when initialized with MFXLoad. For more details, see Upgrading from Intel® Media SDK to Intel® oneAPI Video Processing Library.
- Dispatcher support has been extended to include hardware implementations, including those that implement API versions lower then 2.0. Applications patterned after the 2021.1.1 release samples, rather than the 2.0 specification may fail after re-build as the previous sample code made the assumption that 2.0 APIs would be available. To remedy this please follow the coding patterns in the oneVPL spec
- Sessions initialized with MFXVideoSession::InitEx() defined in file mfxvideo++.h are limited to using the following fields in structure mfxInitParam: Implementation, Version. Applications which require setting non-default values for the following fields must use the C function MFXInitEx() instead: ExternalThreads, GPUCopy, ExtParam, NumExtParam.
Tools and samples
- Releases installed before the 2.4 API update may cause cmake build failures on Linux* OS due to compatibility issues. Prior package versions were aligned with release versions rather than API. As a result,
find_packagelooks for a current version (2.4) but finds a larger legacy version (2021.2.2) and assumes forward compatibility. - sample_decode may not finish with multi-resolution input in external memory mode with CPU implementation.
- legacy-vpp sample in hardware mode is not supported on Skylake systems.
- Encode B-frame distance setting is inconsistent between CPU and GPU implementations. For the CPU implementation 0 means no B-frames, while for the GPU implementation 1 means no B-frames.
- Colorspace flags are required when using sample_* tools, if colorspace is not set tools will fail.
- The sample_multi_transcode tool included in this release is only intended for GPU operation to remain more closely aligned with the version of this tool released with Intel(R) Media SDK.
- The sample_multi_transcode tool has a synchronization issue in 1->N pipelines. When decode is faster than encoders, the issue can cause the free frames consumed faster than the framework released, eventually resulting in tool crash when there is no more memory available.
- hello-transcode sample only supports the oneVPL CPU implementation.
- sample_decode may stop responding if input changes resolution.
- sample_encode software mode does not support NV12 as the input color format. Use i420 with the "i420" argument since NV12 is the default format.
- sample_encode does not support preprocess commands for scaling or color conversion for CPU
- Windows samples are installed to C:\Program Files (x86)\Intel\oneAPI\vpl\latest\examples by default. This should not be a writable location, so you will not be able to build samples here. To build examples, copy this folder to another location first.