Closed Bug 1749511 Opened 3 years ago Closed 2 years ago

Webroom/Google Meets videocalls do not change microphone device when plugged in

Categories

(Core :: WebRTC: Audio/Video, defect)

defect

Tracking

()

RESOLVED DUPLICATE of bug 1771029
Tracking Status
firefox96 --- affected
firefox97 --- affected
firefox98 --- affected

People

(Reporter: estanislao.larriera, Unassigned)

References

Details

Steps to reproduce

1- Join a call on https://webroom.net/ with a headset next to the machine
2- After call begins, plug in the headset and change the microphone device to the headset mic from call settings
3- Verify the audio is being sent by headset microphone

Actual result

Audio is still being sent by computer microphone

Expected result

Audio shoul be sent by headset mic

This issue also affects Google Meet calls.

steps to reproduce

  1. Join a google meet with another person. https://meet.google.com/
  2. Once inside plug headphones with a microphone. TTRS
  3. A Windows10 SETTINGS popup screen appears asking you to select what device was plugged.
  4. Select headphones or headset and click OK.
  5. start Hitting the microphone on the ( laptop near the lcd)
  6. start Hitting the microphone on the headphone (away from the computer lcd)

Actual result
The Sound is heard via headphones, but audio is still being captured via the built in microphone near the lcd, not the microphone from the headphones

Expected result
Once the headphones are inserted, Audio IN should be from the headphones.

Tested on
Windows 10 64bit (affected), Ubuntu 20 64bit (affected), and MacOS 12 (seems not affected)

Nightly 98 (Affected)
Beta. 97.0b2 (Affected)
Release. 96 (Affected)

Summary: Webroom videocall do not change microphone device when plugged in → Webroom/Google Meets videocalsl do not change microphone device when plugged in
Summary: Webroom/Google Meets videocalsl do not change microphone device when plugged in → Webroom/Google Meets videocalls do not change microphone device when plugged in

This also fails using cisco webex
we saw it using latest beta 97.0b4 on a win10 machine when the user inserts the headphones on windows10 the mic is still receiving from the internal machine.
https://cart.webex.com/sign-up-webex)

Severity: S4 → S3

I'm guessing microphone switching will address this. ChunMin, what do you think?

Flags: needinfo?(cchang)

The mic switching can work differently on different video conferencing platform, depends on how they implement their code. For GoogleMeet, I can switch the microphone if I change it manually by clicking settings > Audio > select the mic I plugged in, on MacBook M1Max.

I would need to investigate how GoogleMeet implement the mic switching

Hi there, thanks for reporting and confirming this issue. Would you mind navigating to your about:support page and grab its data to me? I'd like to understand your audio settings, thanks!

Flags: needinfo?(muirpablo)
Flags: needinfo?(estanislao.larriera)
See Also: → 1764380

To reporters of comment 0, comment 1 and comment 2, does it work for you here?

Switching audio input is an application decision, so these sound like bugs/decisions in WebRoom, Google Meet, and WebEX respectively, not Firefox. Sites need to write JS to respond to the devicechange event, and take appropriate action, as shown.

Sites may be tripping over bug 1238038 for which the fiddle has a workaround (other sites like Whereby do this and work fine):

track.stop(); // work around Firefox concurrent mic limit (bug 1238038) 

Bug 1238038 got fixed just 10 days ago, so please try again in the lastest Nightly!

When I try Meet it does seem to switch in Chrome but still not in Firefox, so we should probably reach out to them about that.

See Also: → 1771029

Redirect needinfos that are pending on inactive users to the triage owner.
:jib, since the bug has recent activity, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(muirpablo)
Flags: needinfo?(jib)
Flags: needinfo?(estanislao.larriera)

Bug 1771029 comment 6 contains a summary of improvements in this area, and outlines steps needed for Meet and similar sites to take advantage of them, so I think we can dup this bug to that.

Please comment here if the improvements made there aren't sufficient for your site.

Status: NEW → RESOLVED
Closed: 2 years ago
Flags: needinfo?(jib)
Resolution: --- → DUPLICATE
Flags: needinfo?(cchang)
Severity: S3 → S4
You need to log in before you can comment on or make changes to this bug.