Chrome Fake Audio Testing with WebRTC

[Ozy Ozden]

We have been attempting to use the following chrome flags to test a WebRTC application that uses

a specified audio file for playback instead of the standard beep . 

--use-fake-ui-for-media-stream 

--use-file-for-fake-audio-capture

--use-fake-device-for-media-stream

We start the process off using xvfb on a server running Centos 6.5.

The command used to start the session is

export DISPLAY=:1 && /usr/bin/xvfb-run -e /dev/stdout --server-num=100 --server-args="-screen 0  ${width}x${height}x16"  /usr/bin/google-chrome --enable-logging --v=1 --vmodule=*=1 --user-data-dir=/chromed/google-chrome100 --window-size=${width},${height} --disable-client-side-phishing-detection --disable-sync  --use-fake-ui-for-media-stream --use-file-for-fake-audio-capture=/opt/zenon/public_html/demo/a2002011001-e02.wav --use-fake-device-for-media-stream --start-maximized   --user-data-dir=/chromed/google-chrome100 ${gop} &

I have attached the chrome_debug.log for the session

[Patrik Höglund]

Hi Ozy!

I assume you mean it doesn't work. What are you trying to do? The easiest way to test if it works is to run Chrome with the flags, go to http://apprtc.appspot.com/?debug=loopback and click join. You should hear your file play out.

Note that the file isn't looped, so when the file has played out it will not play again until you create a new media stream (for instance by reloading the above page).

/ P