This document describes the client interfaces for audio effects in S60 Platform release 3.0.
These client-level effect APIs give audio applications the ability to control audio effects. Audio effects are abstractions of audio processing that apply artificial sounds or enhancements to audio. Audio Effect APIs rely on the Effects Framework to communicate with software/hardware entities that handle audio effects processing.
The Audio Effects API relies on one or more of following interfaces:
The MDA Client Utility APIs are defined by the classes: CMdaAudioConvertUtility, CMdaAudioInputStream, CMdaAudioOutputStream, CMdaAudioPlayerUtility, and CMdaAudioRecorderUtility. These utilities are application-level APIs that offer audio client applications the ability to play, record, or convert audio.
The Custom Command API is a generic interface that encapsulates the Custom Command APIs that are already provided by the MDA Client Utility API. A custom command is a custom message sent from the client to the controller via the Custom Command API.
The Custom Interface API is a generic mechanism for clients to retrieve an interface object by specifying the interface UID. Once retrieved, the client uses the interface as a normal API.
The MMF DevSound API is an interface to the adaptation layer of the audio subsystem.
These Effect APIs are defined for S60 Platform release 3.0 and beyond. The Effects Framework makes extensive use of the custom command facility and requires a controller plug-in capable of supporting custom commands defined for the Effects Framework. These custom commands are only available from S60 Platform release 3.0 onwards.