Mandatory APIs and Functions¶
Disclaimer¶
Developers can implement any subset of the oneVPL API. The specification makes no claim about what encoder, decoder, VPP filter, or any other underlying features are mandatory for the implementation. The oneVPL API is designed in the way that users have several options to discover capabilities exposed by the implementation:
Before session creation, users can get list of supported encoders, decoders, VPP filters, corespondent color formats, and memory types with help of the
MFXEnumImplementations()
function.Once the session is created, users can call Query functions to obtain low level implementation capabilities.
Attention
The legacy Intel® Media Software Development Kit implementation does not support the first approach to obtain capabilities.
Exported Functions¶
The Exported Functions table lists all
functions that must be exposed by any oneAPI Video Processing Library implementation.
The realization of all listed functions is mandatory; most functions may return
mfxStatus::MFX_ERR_NOT_IMPLEMENTED
.
Note
Functions MFXInit()
and MFXInitEx()
are not required to be
exported.
See Mandatory APIs for details about which functions and in which conditions
must not return mfxStatus::MFX_ERR_NOT_IMPLEMENTED
.
Function |
API Version |
---|---|
1.0 |
|
1.0 |
|
1.0 |
|
1.0 |
|
1.0 |
|
1.0 |
|
1.0 |
|
1.0 |
|
1.0 |
|
1.0 |
|
1.0 |
|
1.0 |
|
1.0 |
|
1.0 |
|
1.0 |
|
1.0 |
|
1.0 |
|
1.0 |
|
1.0 |
|
1.0 |
|
1.0 |
|
1.0 |
|
1.0 |
|
1.0 |
|
1.0 |
|
1.0 |
|
1.0 |
|
1.0 |
|
1.0 |
|
1.0 |
|
1.0 |
|
1.0 |
|
1.0 |
|
1.0 |
|
1.0 |
|
1.0 |
|
1.0 |
|
1.0 |
|
1.0 |
|
1.19 |
|
2.0 |
|
2.0 |
|
2.0 |
|
2.0 |
|
2.0 |
|
2.0 |
Mandatory APIs¶
All implementations must implement the APIs listed in the Mandatory APIs table:
Functions |
Description |
---|---|
Required functions for the dispatcher to create a session. |
|
Required functions for the dispatcher to return implementation capabilities. |
|
Required function for synchronization of asynchronous operations. |
If the implementation implements any encoder, decoder, or VPP filter, it must implement the corresponding mandatory APIs, as described in the Mandatory Encode, Decode and VPP APIs tables:
Functions |
Description |
---|---|
Required functions if the implementation implements any encoder. |
Functions |
Description |
---|---|
Required functions if the implementation implements any decoder. |
Functions |
Description |
---|---|
Required functions if the implementation implements any VPP filter. |
Note
Mandatory functions must not return the
MFX_ERR_NOT_IMPLEMENTED
status.
If at least one of encoder or decoder or VPP filter is implemented,
MFXQueryImplsDescription()
function must return valid
mfxImplDescription
structure instance with mandatory capabilities
of the implementation including decoder, encoder, or VPP capabilities information.
Any other functions or extension buffers are optional for the implementation.