Media Device Framework Overview

This document provides an overview of the Media Device Framework (MDF) component.

Purpose

The MDF component provides a codec interface that supports both audio and video codecs. The codec interface allows easy implementation of OpenMAX IL (Integration Layer) based codecs. The MDF also includes an implementation of the OpenMAX core to load and unload OpenMax components.

Note: The use of OpenMAX is optional.

Required background

The MDF component provides support for OpenMAX IL based codecs. The OpenMAX IL API was developed by the Khronos Group to provide cross platform portability for audio and video media components. For more information about OpenMAX IL, refer to OpenMAX Overview.

Architectural relationships

The MDF component provides a codec interface below the MMF controller plugins and above the hardware. The codec interface provides MMF clients with access to PUs. The MDF interacts with DevSound for audio and DevVideo for video.

API summary

The MDF component includes the following APIs:

API	Description
Codec Resolver	Custom resolver for identifying codecs. For more information, see Codec Resolver Overview.
Hardware Device Adapter Plugin	Instructs the Processing Unit (PU) Loader Plugin. For more information, see Hardware Device Adapter Plugin Overview.
OpenMAX Translation	Provides translation for OpenMAX. For more information, see OpenMAX Translation Overview.
Processing Unit Loader Plugin	Loads PUs. For more information, see Processing Unit Loader Plugin Overview.
Processing Unit Resolver	Handles streaming and parsing for codec plugins. For more information, see Processing Unit Resolver Overview.

Typical uses

The MDF component is used for the following:

Resolving audio and video codecs.
Loading and unloading PUs.
Configuring PUs.
Loading and unloading OpenMAX codecs.
Translating OpenMAX codecs to Symbian C++.