Webrtc audio bug
Reported by
mar...@missionlabs.co.uk,
Dec 8 2017
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36 Steps to reproduce the problem: During a webrtc call unplug and replug in the output audio device quickly. The audio doesn't reappear once the device has been plugged back in. What is the expected behavior? Audio should start again on the device. What went wrong? There was no audio coming through the device. Did this work before? No Chrome version: 61.0.3163.100 Channel: n/a OS Version: OS X 10.12.6 Flash Version: This works fine on firefox.
,
Dec 8 2017
,
Dec 12 2017
"Unable to reproduce the issue on the reported chrome version 61.0.3163.100 and on the latest stable 63.0.3239.84 using mac 10.13.1 with the below mentioned steps. 1. Launched chrome 2. Navigated to https://appr.tc/ 3. Made a call to another device using the unique id 4. Plugged in audio cable 5. while the call is running plugged out the cable and plugged in again. We observed the audio was audible properly with out any issue. @Reporter: Could you please check the same by creating a new profile and let us know the behavior. Thanks! "
,
Dec 12 2017
If I use the above steps - when I unplug the usb device the audio starts coming through my machine speakers and when I plug back in it doesn't start playing back from the usb device. I've replicated using this website https://webrtc.github.io/samples/src/content/peerconnection/audio/ - if you start a call then unplug and replug the usb device then the audio doesn't restart. On firefox the audio does start coming through the device again once replugged in. Thanks!
,
Dec 18 2017
[Triage] Guido: does this ring a bell? I have some vague memory of something similar.
,
Dec 18 2017
This may happen when output goes to a nondefault output device. I think there was a bug filed about that. Selecting a nondefault output device with setSinkId(), removing the device and then replugging the device does not cause audio to be redirected back to the nondefault device.
,
Aug 2
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by mar...@missionlabs.co.uk
, Dec 8 2017