<audio>.setSinkId() doesn't have any effect with ALSA only (still playing on default output)
Reported by
colindef...@gmail.com,
Jun 15 2018
|
||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.87 Safari/537.36 Steps to reproduce the problem: 1. Make sure pulseaudio is disabled (pulseaudio -k to kill it, the speaker icon in the top right of Ubuntu GUI should disappear). Restart your browser if open. 2. Browse https://webrtc.github.io/samples/src/content/devices/multi/ 3. Allow the site to use your microphone (even if you don't have one, this permission is required for this site to list the sound devices). "Secure" button (omnibar) > Site settings > Microphone > Allow. And reload the site as suggested. 4. On the site, in the 2nd column, 2nd row, select the desired output (different from the default one) and play the sound file. 5. Unfortunately you should hear the sound playing on the default device, not on the one you have selected. What is the expected behavior? The sound should be played on the selected device. If you don't kill pulseaudio (you can restart it by typing pulseaudio in a terminal, then restart the browser) and if you follow the steps from 2 to 5 then you should hear the sound playing on the desired output. What went wrong? Even if navigator.mediaDevices.enumerateDesvices() enumerates correctly and even if after using <audio>.setSinkId() the <audio>.sinkId property has the desired value then the sound still plays on the default sound device. Did this work before? N/A Does this work in other browsers? N/A Chrome version: 66.0.3359.181 Channel: stable OS Version: Ubuntu 18.04 64-bit Flash Version:
,
Jun 22 2018
Unable to reproduce this issue on reported version 66.0.3359.181 and latest stable 67.0.3396.87 using Ubuntu 17.10 with steps mentioned in comment#0. 1. On using pulseaudio -k we are still seeing speaker icon. 2. Unable to hear audio in step-5. Attaching screenshots for reference. @Reporter: Please check the screenshots and let us know if we miss anything. Is this specific to Ubuntu 18.04? Any further information on reproducing the issue would help in better triaging.
,
Jun 22 2018
Hello, 1.If you still see the speacker icon Maybe pulseaudio is not totally killed... In a terminal you can try "ps -aux | grep pulseaudio" to see if pulseaudio process is still running. If it is not killed then maybe "sudo pulseaudio -k" will work. Or, to not launch automatically pulseaudio at boot time, add "autospawn = no" to "/etc/pulse/client.conf" and reboot 2. For step 5: Are you able to hear sound when pulse audio is running? Are you able to play sound on Default output? 3. Notes: On https://webrtc.github.io/samples/src/content/devices/multi/ I have a different device list when pulseaudio is running and when there is ALSA only. With or without pulse the device names are not the same (I guess pulseaudio and ALSA don't list the devices the same way in the OS). I haven't tried it on other Ubuntu than 18.04. I can see on your captures that you are use chrome. I am using chromium-browser. I don't know if this can make a difference for this topic.
,
Jun 22 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 23 2018
,
Jun 26 2018
,
Jun 26 2018
Dale - should this be supported?
,
Jun 26 2018
Probably, but it's not high priority since Pulse is the preferred audio output path and ALSA usage is low. +guidou who added this functionality.
,
Jun 26 2018
Ok, guidou routed it to me :) |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by susan.boorgula@chromium.org
, Jun 17 2018