Visible to Intel only — GUID: GUID-33E3251C-22E3-44C0-B4C9-4BF310FC6043
Use Intel® oneVPL Core API for the Best Portability
Intel(R) Media SDK API Features Removed from oneVPL
Key Features Added to oneVPL 2.x API
AV1 Encode Features Added to Intel® oneVPL
Other Differences Between Intel(R) Media SDK and oneVPL
oneVPL Hardware Support Details
Why oneVPL Dispatcher Is Safer
Visible to Intel only — GUID: GUID-33E3251C-22E3-44C0-B4C9-4BF310FC6043
Key Features Added to oneVPL 2.x API
VPL session initialization is more flexible and designed for multiple adapters. By default, it is slower than Intel(R) Media SDK initialization. Low latency init is added to the API to address this gap. 2.x session initialization is not required to transition to oneVPL, but it is easy to adopt and has many advantages over 1.x initialization. To support legacy hardware, you can use 2.x initialization with the Intel(R) Media SDK runtime.
Intel(R) Media SDK memory allocation is designed for Intel(R) Media SDK-only pipelines. VPL Internal memory allocation is intended to simplify interoperability with other graphics APIs. Additional interop capabilities in development. Internal memory allocation is incompatible with legacy Intel(R) Media SDK runtime and cannot be used on legacy hardware.
Additional API features are added with each API update. It includes the following:
Fused decode+VPP
Hyperencode
Encode statistics
VPL RAW/Bayer support
3DLUT
Dispatcher logging
Extended AV1 parameters