There are also some DirectX/DXVA2 decoders.įuture articles will cover comparisons of oneVPL vs. The VA-API codecs call VA-API directly through a different implementation to provide decode and encode without using oneVPL. The *_qsv codecs are implemented with glue code that calls oneVPL to implement decode and encode operations. Application developers can choose between CPU implementations, Quick Sync Video (now implemented with oneVPL), as well as implementations calling VA-API/DirectX without oneVPL. Many codec implementations are available in FFMPEG.

As illustrated in the diagram below, the oneVPL dispatcher chooses which implementation to load when run. Users can switch to oneVPL in FFMPEG, even for older Intel hardware. Both options enable compilation of Intel® Quick Sync Video (*_qsv) codecs, which can be used without change from the FFMPEG command line or in applications. Just substitute ‘ -enable-libvpl’ instead of ‘ -enable-libmfx’ in the configure stage of FFMPEG compilation.

The switch to oneVPL from Media SDK in FFMPEG, is simple.

All Intel GPU media users are encouraged to switch to oneVPL to take advantage of hardware capabilities as soon as they become available. Going forward, the primary way to access new Intel® GPU media features is via oneVPL (no more feature additions are being added to Media SDK).

This is an important change because oneVPL is Intel’s evolution of the Intel® Media SDK (Media SDK). As part of Intel’s long-term contributions to open source industry standards FFMPEG and GStreamer for media processing, Intel added support for the Intel® oneAPI Video Processing Library (oneVPL) to FFMPEG.

Ffmpeg hevc