Intel Media SDK (legacy)

Intel Media SDK is a discontinued media software interface whose names remain in older Intel acceleration stacks and logs, distinct from the hardware generations those stacks use.

Intel Media SDK provided interfaces for accelerated video decode, encode and processing on supported Intel media hardware. Older applications, distribution packages and logs can still describe that software stack.

Intel has discontinued the project and directs users toward its successor library, now called Intel VPL. “Legacy” here describes the software project, not the age of every device an application might use.

API names preserve the operation roles

The SDK uses MFX-prefixed interfaces. Names in an older source or trace can identify the intended stage:

Legacy interface family Role
MFXVideoDECODE Encoded input to decoded pictures
MFXVideoVPP Picture processing
MFXVideoENCODE Prepared pictures to encoded output
MFXVideoCORE Shared session/core services

Those roles explain why a log can name several Intel media operations in one conversion. Decode and encode remain different stages even when both are accessed through the same SDK family.

The installed stack contains several parts

An application built against a media interface needs a compatible implementation and driver path at execution time. Development headers and sample projects are another layer.

An older package name can therefore describe the API dependency without identifying the exact active graphics driver or physical engine.

Changing a library package alone does not add a codec feature to the device. Conversely, newer physical hardware can require a software stack different from the one assumed by an old application build.

QSV wrapper names do not date the entire route

Suppose an original log names an h264_qsv encoder and MFX-related initialization. That identifies an Intel-oriented H.264 encoding route at the shown stage.

It does not report which decoding operation preceded it, the surface format supplied by its filters or the complete version of every runtime component. Those facts need their own log/configuration context.

The qsv name remains meaningful in software that uses successor interfaces as well. A stable wrapper name is useful for recognizing the family of the operation while API/runtime versions identify the particular stack.

The successor keeps the task categories

Intel VPL continues the decode, encode and video-processing roles with its current API and implementation-selection model. The dispatcher discussion shows how matching implementations and sessions are selected.

See Also

References