Closed Bug 1628639 Opened 4 years ago Closed 4 years ago

[WFH]Audio from integrated microphone doesn't work after unplug the headset

Categories

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

Product:
Core
Component:
WebRTC: Audio/Video
Version:
77 Branch
Platform:
Desktop
Windows 10
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INVALID
Tracking Flags:
Tracking Status
firefox77 --- wontfix

People

(Reporter: rpopovici, Unassigned)

References

Details

(Whiteboard: [WFH])

[Affected versions]:
Nightly 77

[Affected platforms]:

  • Win 10x64 (desktop)

[Steps to reproduce]:

  1. Open Nightly and start a call from https://jitsi.org/
  2. Allow the headset
  3. Unplug the headset

[Expected result]:
Input source should be switched to integrated.

[Actual result]:
Audio doesn't work at all

[Additional notes]:
-Audio still doesn't work after re-pluging the headset. The same thing happens in facebook and webroom.net call.
-I use TTRS headset.

[Regression Range]:
Webrtc calling with mozregression builds doesn't work(I tried with facebook and jitsi)
This bug still reproduces in 68, but in older versions than 68, another bug is occurring(When I unplug the headsets the call freezes)

OS: Unspecified → Windows 10
Hardware: Unspecified → Desktop
Summary: Audio doesn't work after unplug the headsets → Audio from integrated camera doesn't work after unplug the usb headset
Summary: Audio from integrated camera doesn't work after unplug the usb headset → Audio from integrated microphone doesn't work after unplug the headset
See Also: → 1614657
Summary: Audio from integrated microphone doesn't work after unplug the headset → [WFH]Audio from integrated microphone doesn't work after unplug the headset
Whiteboard: [WFH]

Generally, it's a site's responsibility to divert to a different source if a microphone is unplugged.

Alex, are you suggesting bug 1614657 is related and solves this problem?

Flags: needinfo?(achronop)

No, I am suggesting the same as you, I should have explained it. Since bug 1614657 landed, the end event works well so it's up to the application to implement the desired switch logic, if any. Otherwise, the input track will stop and nothing else will happen.

Flags: needinfo?(achronop)

I also verified that both Chrome and Safari act the same. This appears to be a site issue, not a Firefox issue.

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.