On Windows, on a Meet call, the only available audio output is the default audio device
Categories
(Core :: WebRTC: Audio/Video, defect, P3)
Tracking
()
People
(Reporter: bugshideout, Unassigned)
References
(Depends on 1 open bug, Blocks 1 open bug)
Details
Attachments
(1 file)
|
335.55 KB,
image/png
|
Details |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:137.0) Gecko/20100101 Firefox/137.0
Steps to reproduce:
- on Windows 10 22H2, have two audio devices (speaker and headset for example)
- go to https://meet.google.com
- click on new meeting/start an instant meeting
- if asked, grant all permissions to use the camera and whatever else
- click on the microphone icon in the lower center/left to choose where the audio will be output (yes, the icon should be a speaker and not a microphone...)
- the only available option is System Default Speaker, regardless of how many there are plugged in your machine. On Chrome, we can see a big list.
Actual results:
- the only available option is System Default Speaker, regardless of how many there are plugged in your machine. On Chrome, we can see a big list.
Expected results:
I should see a list of multiple speakers, just like in Chrome
Screenshot is attached.
Do not worry about the fact that firefox is in incognito mode nor that it can't find a microphone. I did this screenshot while in a call in another windows. But the bug is always there no matter how many calls and reproducible 100% of the time.
Comment 1•10 months ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::WebRTC: Audio/Video' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Comment 2•9 months ago
|
||
Meet does not currently support speaker selection in Firefox. We suspect the reason to be bug 1868750.
Updated•9 months ago
|
Comment 3•9 months ago
|
||
The severity field is not set for this bug.
:jib, could you have a look please?
For more information, please visit BugBot documentation.
Comment 4•9 months ago
|
||
Parent bug work should help address this. Once we have that we'll ping the Meet team about it.
Description
•