Constructor.

Adds a data sink to the controller.

A typical data sink would be a file, descriptor, audio output (speaker) or display. A controller plugin may require multiple data sinks to be added (for example a video playing controller would require two); the exact number is plugin-specific. Data sinks are plugins themselves, and are loaded by the controller framework inside the controller thread.

Adds a data sink to the controller, and receives a handle to allow removal and direct communication with that data sink.

A typical data sink would be a file, descriptor, audio output (speaker) or display. A controller plugin may require multiple data sinks to be added (for example a video playing controller would require two); the exact number is plugin-specific. Data sinks are plugins themselves, and are loaded by the controller framework inside the controller thread.

Add a data sink to the controller asynchronously, and receive a handle to allow removal and direct communication with that data sink.

A typical data sink would be a file, descriptor, audio output (speaker) or display. A controller plugin may require multiple data sinks to be added (for example a video playing controller would require two); the exact number is plugin-specific. Data sinks are plugins themselves, and are loaded by the controller framework inside the controller thread.

Adds a data source to the controller.

A typical data source would be a file, descriptor, audio input (microphone) or camera. A controller plugin may require multiple data sources to be added (for example a video recorder controller would require two); the exact number is plugin-specific. Data sources are plugins themselves, and are loaded by the controller framework inside the controller thread.

Adds a data source to the controller, and receive a handle to allow removal and direct communication with that data source.

A typical data source would be a file, descriptor, audio input (microphone) or camera. A controller plugin may require multiple data sources to be added (for example a video recorder controller would require two); the exact number is plugin-specific. Data sources are plugins themselves, and are loaded by the controller framework inside the controller thread.

Add a data source to the controller asynchronously, and receive a handle to allow removal and direct communication with that data source.

Note: only one call to this method can be outstanding at any time.

A typical data source would be a file, descriptor, audio input (microphone) or camera. A controller plugin may require multiple data sources to be added (for example a video recorder controller would require two); the exact number is plugin-specific. Data sources are plugins themselves, and are loaded by the controller framework inside the controller thread.

Adds a file handle data sink, together with its source info, to the controller, and receives a handle to allow removal and direct communication with that data sink.

Note: only one call to this method can be outstanding at any time.

The data sink would be a file for this API. A controller plugin may require multiple data sinks to be added (for example a video playing controller would require two); the exact number is plugin-specific. Data sinks are plugins themselves, and are loaded by the controller framework inside the controller thread.

Add a file handle data source, together with its source info, to the controller asynchronously, and receive a handle to allow removal and directcommunication with that data source.

Note: only one call to this method can be outstanding at any time.

The data source would be a file for this API. A controller plugin may require multiple data sources to be added (for example a video recorder controller would require two); the exact number is plugin-specific. Data sources are plugins themselves, and are loaded by the controller framework inside the controller thread.

Cancels a previous registration to receive events from the controller plugin.

This must be called from the DoCancel() method of the active object using the ReceiveEvents() API function.

Closes the controller plugin.

Calling this method will unload the controller plugin and close down the controller thread.

Sends a custom command asynchronously to the controller plugin.

Custom commands allow controller plugins to extend the standard API.

Note: This method will return immediately. The RunL of the active object owning the aStatus parameter will be called when the command is completed by the controller plugin.

Sends a custom command asynchronously to the controller plugin.

Custom commands allow controller plugins to extend the standard API.

Note: This method will return immediately. The RunL() of the active object owning the aStatus parameter will be called when the command is completed by the controller plugin.

Sends a custom command synchronously to the controller plugin.

Custom commands allow controller plugins to extend the standard API.

Note: This method will not return until the controller plugin has serviced the command.

Sends a custom command synchronously to the controller plugin.

Custom commands allow controller plugins to extend the standard API.

Note: This method will not return until the controller plugin has serviced the command.

Gets the duration of the clip in microseconds.

Note: The controller must be in the PRIMED or PLAYING state before this can be called.

Returns a particular meta data entry from the clip.

All meta data entries can be retrieved by multiple calls to this method, iterating aIndex from 0 to the value returned by GetNumberOfMetaDataEntries().

Gets the number a meta data entries in the clip.

A clip may contain zero or more entries of meta data, e.g Author, Copyright etc.

Gets the current position microseconds.

Note: The controller must be in the PRIMED or PLAYING state before this can be called.

Loads a controller plugin by specifying the UID of the plugin to load.

Creates a new thread and loads the specified controller into the new thread. Use the classes CMMFControllerPluginSelectionParameters and CMMFFormatSelectionParamters to find the uid of the controller to load. This version of Open() will give each controller its own heap which will consume one chunk. Use the overloaded version of Open() to create controllers that share a single heap.

Loads a controller plugin by specifying a CMMFControllerImplementationInformation object.

CMMFControllerImplementationInformation is passed as a parameter to allow the controller thread's heap size to be determined without a further query to ECOM.

The function creates a new thread and loads the specified controller into the new thread. The classes CMMFControllerPluginSelectionParameters and CMMFFormatSelectionParamters are used to find the UID of the controller to load. This version of Open() will give each controller its own heap which will consume one chunk. Use the overloaded version of Open() to create controllers that share a single heap.

Loads a controller plugin by specifying the UID of the plugin to load.

Creates a new thread and loads the specified controller into the new thread. Use the classes CMMFControllerPluginSelectionParameters and CMMFFormatSelectionParamters to find the uid of the controller to load.

Loads a controller plugin by specifying a CMMFControllerImplementationInformation object.

CMMFControllerImplementationInformation is passed as a parameter to allow the controller thread's heap size to be determined without a further query to ECOM.

The function creates a new thread and loads the specified controller into the new thread. The classes CMMFControllerPluginSelectionParameters and CMMFFormatSelectionParamters are used to find the UID of the controller to load.

Same as RMMFController::Open(TUid, const TMMFPrioritySettings&) which loads a controller plugin by specifying the UID of the plugin to load, except that this is expected to be called by user thread without DRM Capability.

Creates a new thread through DRM Plugin Server and loads the specified controller into the new thread. Use the classes CMMFControllerPluginSelectionParameters and CMMFFormatSelectionParamters to find the uid of the controller to load. This version of Open() will give each controller its own heap which will consume one chunk. Use the overloaded version of Open() to create controllers that share a single heap.

CMMFControllerPluginSelectionParamters

Same as Open(const CMMFControllerImplementationInformation&, const TMMFPrioritySettings&) which loads a controller plugin by specifying a CMMFControllerImplementationInformation object.

CMMFControllerImplementationInformation is passed as a parameter to allow the controller thread's heap size to be determined without a further query to ECOM.

The function creates a new thread through DRM Plugin server and loads the specified controller into the new thread. The classes CMMFControllerPluginSelectionParameters and CMMFFormatSelectionParamters are used to find the UID of the controller to load. This version of Open() will give each controller its own heap which will consume one chunk. Use the overloaded version of Open() to create controllers that share a single heap.

CMMFControllerPluginSelectionParamters

Same as RMMFController::Open(TUid, const TMMFPrioritySettings&, TBool) which loads a controller plugin by specifying the UID of the plugin to load, except that this is expected to be called by user thread without DRM Capability.

Creates a new thread through DRM Plugin server and loads the specified controller into the new thread. Use the classes CMMFControllerPluginSelectionParameters and CMMFFormatSelectionParamters to find the uid of the controller to load.

CMMFControllerPluginSelectionParamters

Same as Open(const CMMFControllerImplementationInformation&, const TMMFPrioritySettings&, TBool) which loads a controller plugin by specifying a CMMFControllerImplementationInformation object.

CMMFControllerImplementationInformation is passed as a parameter to allow the controller thread's heap size to be determined without a further query to ECOM.

The function creates a new thread through DRM Plugin Server and loads the specified controller into the new thread. The classes CMMFControllerPluginSelectionParameters and CMMFFormatSelectionParamters are used to find the UID of the controller to load.

CMMFControllerPluginSelectionParamters

Pauses the controller.

The controller will cease transferring data from its data source(s) to its data sink(s). A subsequent call to Play() will result in the data transfer resuming from the same place as when the Pause() was called.

This moves the controller from the PLAYING back to the PRIMED state.

Note: Play() must have been called prior to calling Pause().

Starts the controller playing. The controller will begin transferring data from its data source(s) to its data sink(s).

This moves the controller from the PRIMED to the PLAYING state.

Play() means "Start Playing" - i.e. this method will return as soon as playback has begun.

If the data transfer comes to an end due to an internal event (e.g. source runs out of data), the caller will be notified via the ReceiveEvents() interface.

Note: Prime() must have been called prior to calling Play().

Prepares the controller to start playing.

The controller should initialise its sources, sinks and buffers. This moves the controller from the STOPPED to the PRIMED state.

Registers to receive events from the controller plugin.

Events can be generated at any time, and are generally associated with things that occur due to something happening internally within the controller. For example, an event will be generated if the controller stops playing due to reaching the end of a file.

Removes a data sink from the controller.

In certain situations, it may be necessary to remove a data sink from a controller, for example when you need change output devices on the fly.

It should be noted that not all controller plugins will support the removal of a data sink.

Removes a data source from the controller.

In certain situations, it may be necessary to remove a data source from a controller, for example when you need to play a different file of the same format as the current one.

It should be noted that not all controller plugins will support the removal of a data source.

Reverts the controller plugin back to the state it was in just after it had been Opened.

Note: All sources and sinks will be removed from the controller.

Sets the current position microseconds.

Note: The controller must be in the PRIMED or PLAYING state before this can be called.

Sets the priority settings for this controller.

Set the priority of the controller's sub thread.

This can be used to increase the responsiveness of the audio plugin to minimise any lag in processing. This function should be used with care as it may have knock-on effects elsewhere in the system.

Stops the controller.

The controller will cease transferring data from its data source(s) to its data sink(s), reset its position and delete any allocated buffers. In effect, calling Stop() undoes any actions performed by the controller during the call to Prime().

This moves the controller from the PRIMED back to the STOPPED state.

The controller proxy. Used to pass messages to the controller thread.

Used to hold the destination information for messages for the standard controller plugin interface.