Visible to Intel only — GUID: GUID-674F4020-74EF-4FF6-AFC4-D750129D15EB
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-674F4020-74EF-4FF6-AFC4-D750129D15EB
Why oneVPL Dispatcher Is Safer
If you are a Intel® Media SDK user, better to convert to oneVPL as soon as possible to avoid complications due to API mismatches between Intel(R) Media SDK and oneVPL in the runtimes.
As shown in the hardware support list, implementation is loaded regardless of which dispatcher is used. The exception is the 11th Generation Intel® Core and Intel® Iris® Xe MAX, which were released as oneVPL was emerging.
If you use Intel(R) Media SDK that is newer than VPL platforms, and application code uses removed feature, the problem may occur.
If you use only Core API in oneVPL, no issues occur, only reduced functionality.
Dispatcher → Runtime ↓ |
VPL |
|---|---|
Intel(R) Media SDK |
|
VPL |
Works but limited features. |
If you use Intel(R) Media SDK dispatcher and app that contains Intel(R) Media SDK features removed in VPL, use of removed features can cause applications to crash on the VPL hardware.
Dispatcher → Runtime ↓ |
Intel(R) Media SDK |
|---|---|
Intel(R) Media SDK |
|
VPL |
App crashes without a warning for removed features. |
The recommended mitigation is recompiling with the VPL API and relinking with the VPL dispatcher. This detects the presence of any removed features at compile time, which is preferable to an unanticipated crash.