| Note! |
|---|
|
Audio Proxy Server (APS) is a wrapper to the S60 sound device.
Its main purpose is to bypass the Vendor ID (VID) related restrictions on S60 3rd Edition and S60 3rd Edition, FP1 platforms, when streaming audio data in 3rd party applications.
The component is most suitable for VoIP developers who need to set the appropriate audio priority and preference values in order to utilize full duplex audio.
APS supports audio streaming using the following codecs:
Please note that some devices do not support all of the codecs mentioned above.
APS is available for S60 3rd Edition MR and S60 3rd Edition FP1 releases (since APS v2.0).
The latest version available: 2.43
| Note! |
|---|
|
APS release 2.4.3
APS release 2.4.2
iPlayerSettings.iSettings.iCaps = TMdaAudioDataSettings::ERoutingControl; iPlayerSettings.iSettings.iFlags = 0; // (CAudioOutput::ENoPreference)
When ERoutingControl capability is set by the client, APS takes the initial output routing preference from iFlags instead of using the default (CAudioOutput::EPrivate). (Note: These flags have no effect on S60 3.0 version of APS, which doesn't have this issue).
APS release 2.41
Known issues:
APS release 2.31
APS release 2.3
TAPSRequest::EAPSPlayerInitComplete and TAPSRequest::EAPSRecorderInitComplete
These callbacks must be caught and processed by CQueueHandler::RunL on the client side. The client should now create and initialize the recorder AFTER receiving TAPSRequest::EAPSPlayerInitComplete. Also, the APS server is ready for streaming only AFTER both callbacks are received by the client.
Client applications must utilize this new initialization procedure as their pre APS 2.3 compatible implementations will not work with APS 2.3 without these changes.
Developers should refer to QueueHandler.cpp file of the bundled example application and make sure their client's implementation is similar to that in CQueueHandler::RunL as well as CStreamerEngine::InputStreamInitialized and CStreamerEngine::OutputStreamInitialized in StreamerEngine.cpp.
This change was necessary as the initialization of the sound device and codecs was not done properly on earlier APS releases, making the initialization and configuration process prone to failures and resulting in potentially unstable device.
from terminating the streaming session when receiving an empty buffer.
new callbacks from the APS (TAPSRequest::EAPSPlayerInitComplete and TAPSRequest::EAPSRecorderInitComplete)
Known issues: Previous APS 2.x installations must be uninstalled prior to installing APS 2.3. An 'Update error' -note may otherwise be shown on the screen and the installation will terminate.
APS release 2.2
due to lack of API support.
APS 2.x releases due to 164-byte buffer limitation.
starting streaming.
APS release 2.1 (First release from S60 R&D)
APS release 2.0 (Forum Nokia)
APS release 1.1 ("VID hack")
caused by 4KB buffer in the adaptation layer.
The latest version of the Audio Proxy Server plugin can be found in the SDK API Plug-in.
The following obsolete standalone packages are also available: APS v2.3, APS v1.1
Audio routing limitations on S60 3rd Edition
--
No related wiki articles found