Chrome ADM

[kiranr...@gmail.com]

Hi All

I am trying to understand how chrome is implementing ADM, specifically device selection. In the process I came across the below code.

https://cs.chromium.org/chromium/src/remoting/protocol/webrtc_audio_module.h

https://cs.chromium.org/chromium/src/remoting/protocol/webrtc_audio_module.cc

int32_t WebrtcAudioModule::SetPlayoutDevice(uint16_t index) {

return 0;

}

Function seems to simply return.I guess I am missing some flow here.
Would someone like to point me to how Chrome is implementing ADM code?

Thanks in advance.

Kiran 

[Henrik Andreasson]

Only a fraction of the native ADM methods are implemented in Chrome; most are empty.

An example of the ADM being used by Peerconnection can be found here.

Chrome uses a multi-process architecture and ADM parts in the render process only work as a proxy to the implementations which contain the native audio parts in the audio process.

All these different implementations can be found here.

[Henrik Andreasson]

Device selection in Chrome is not using the WebRTC ADM as base; instead more complex web APIs are utilized.

Audio output devices are selected using setSinkId and input devices by using getUserMedia.

This demo illustrates how to use these APIs.

[kiranr...@gmail.com]

Thanks for your time.