Transition Guide
Visible to Intel only — GUID: GUID-147AF357-50A7-4095-8AA6-1F45EE344BAE
Supported APIs
Core APIs are supported by both Intel® Media SDK implementation and oneVPL implementation, as shown in this table:
Implementation |
|||
|---|---|---|---|
CPU vplswref64 |
No |
Yes |
Yes |
GPU (Intel® Media SDK) mfxhw64 |
Yes* |
Yes |
No |
GPU (oneVPL) mfx-gen |
No |
Yes |
Yes |
NOTE:
(*) The use of removed APIs is only possible if the application is compiled with legacy Intel® Media SDK headers, linked with the legacy Intel® Media SDK dispatcher, and targets legacy GPUs.
Note that it is also possible to use the Intel® Media SDK dispatcher with the Intel® Media SDK and oneVPL runtime plugins. This can be a good choice for legacy applications to work on legacy hardware without code changes. However, for the hardware covered by the oneVPL runtime plugin, it is only possible to use Core APIs, as these are the only functions and options that are common between Intel® Media SDK dispatcher and the oneVPL runtime implementation. The use of removed APIs on hardware targeted by the oneVPL plugin will result in a runtime error when the requested symbol cannot be found.
Application portability is maximized with Core API. Applications written with Core API are portable:
If compiled with legacy Intel® Media SDK headers or oneVPL headers
If used on any hardware supported by Intel® Media SDK or oneVPL
With any implementation supporting Intel® Media SDK or oneVPL Specification
NOTE:
Supported Hardware