The oneAPI Video Processing Library (oneVPL) is a programming interface for video decoding, encoding, and processing to build portable media pipelines on CPUs, GPUs, and other accelerators.
It provides device discovery and selection in media centric and video analytics workloads and API primitives for zero-copy buffer sharing. oneVPL is backwards and cross-architecture compatible to ensure optimal execution on current and next generation hardware without source code changes.
See the oneVPL Specification for additional information. This is part of the oneAPI specification.
This repository contains the following components of oneVPL:
- Copies of the oneVPL Specification API header files. The version of the oneVPL API is listed in the mfxdefs.h file.
- oneVPL Dispatcher
- Examples demonstrating API usage
- oneVPL command line tools
To use oneVPL for video processing you need to install at least one implementation. Here is a list of current implementations.
- oneVPL-cpu for use on CPU
- oneVPL-intel-gpu for use on Intel Xe graphics and newer
- Media SDK for use on legacy Intel graphics
graph TD;
VPL[oneVPL Dispatcher]-->oneVPL-cpu;
VPL[oneVPL Dispatcher]-->oneVPL-intel-gpu;
VPL[oneVPL Dispatcher]-->MediaSDK;
VPL[oneVPL Dispatcher]-->Future1;
VPL[oneVPL Dispatcher]-->Future2;
As shown in this diagram, the oneVPL Dispatcher dispatches the application to use either the VPL CPU runtime, VPL GPU runtime, or the Media SDK GPU Runtime. We may support more implementations in the future.
Runtime loaded by oneVPL Dispatcher and their Microsoft* DirectX* support:
| GPU | Media SDK | oneVPL | Microsoft* DirectX* Support |
|---|---|---|---|
| Earlier platforms, back to BDW (Broadwell) | ✔️ | DX9/DX11 | |
| ICL (Ice Lake) | ✔️ | DX9/DX11 | |
| JSL (Jasper Lake) | ✔️ | DX9/DX11 | |
| EHL (Elkhart Lake) | ✔️ | DX9/DX11 | |
| SG1 | ✔️ | DX9/DX11 | |
| TGL (Tiger Lake) | ✔️ | ✔️ | DX9/DX11* |
| DG1 (Iris® Xe MAX) | ✔️ | ✔️ | DX11* |
| RKL (Rocket Lake) | ✔️ | DX11 | |
| ADL-S (Alder Lake S) | ✔️ | DX11 | |
| ADL-P (Alder Lake P) | ✔️ | DX11 | |
| Future platforms... | ✔️ | DX11 |
For TGL and DG1, if both oneVPL and Intel(R) Media SDK runtime are installed then the oneVPL Dispatcher will prefer oneVPL runtime unless the application requests D3D9 by setting the oneVPL Dispatcher filter property "mfxImplDescription.AccelerationMode" to MFX_ACCEL_MODE_VIA_D3D9.
You can install oneVPL:
- from oneVPL home page as a part of Intel® oneAPI Base Toolkit.
- from source code. See Installation from Sources for details.
For more details on installation options and procedures, see the Intel® oneAPI Video Processing Library Installation Guide.
If you did not install to standard system locations, you need to set up the environment, so tools like CMake and pkg-config can find the library and headers.
For Linux:
source <vpl-install-location>/etc/vpl/vars.sh
For Windows:
<vpl-install-location>\etc\vpl\vars.bat
Add the following code to your CMakeLists, assuming TARGET is defined as the component that wants to use oneVPL:
if(WIN32 AND CMAKE_SIZEOF_VOID_P EQUAL 4)
set(CMAKE_LIBRARY_ARCHITECTURE x86)
endif()
find_package(VPL REQUIRED)
target_link_libraries(${TARGET} VPL::dispatcher)
The following command line illustrates how to link a simple program to oneVPL using pkg-config.
gcc program.cpp `pkg-config --cflags --libs vpl`
See CONTRIBUTING.md for more information.
This project is licensed under the MIT License. See the LICENSE file for details.
See the Intel Security Center for information on how to report a potential security issue or vulnerability.