Issue metadata
Sign in to add a comment
|
WebRTC : Audio input from the external mic is coming in chrome beta
Reported by
kpkulkar...@gmail.com,
Mar 31 2016
|
||||||||||||||||||||||
Issue descriptionChrome Version : 50.0.2661.37 WebRTC - Chrome beta issue ---------------------------------------------------------------------------------- Environment : Machine is running with chrome beta version - 50.0.2661.37 Steps to reproduce : 1. Start the meeting and connected the external mic 2. Then from the settings menu select the external mic Expected : Audio input from the external mic should be selected when the user speaks Observed : Audio input from the external mic is not coming Even if we select the external mic from the settings menu , still we are getting audio from the inbuilt mic of the laptop. Please find the console log in the attachment. Note - Issue is observed on the only one machine with mac os - 10.9.11 , running with chrome beta. With same version of the chrome beta we have not observed the issue on the windows machines and also other mac books running with mac os - 10.9.11
,
Mar 31 2016
What "settings menu" and meeting application are you using? Some applications aren't currently configured for dynamic audio and video input switching. For example, if you try to change inputs in an https://appr.tc/ via Chrome's settings, you won't see the change take effect until you leave the current call and join a new one. But if you switch inputs during a Google Hangout, for example, you should see/hear the change take effect immediately.
,
Mar 31 2016
I have tested with the bluejeans webrtc application and also with application like appear.in I tried to test with talky.in , but there was no mic and speaker selection option there.
,
Mar 31 2016
appear.in doesn't support on-the-fly input device switching. Its settings page says at the bottom, "Updating preferences will refresh your browser window. You will automatically rejoin the conversation." talky.in doesn't appear to be a valid WebRTC-based site, so I'll assume you're referring to talky.io. :) In any case, I don't want to try debugging a third party app. Can you try changing inputs in https://webrtc.github.io/samples/src/content/devices/input-output/ and see if they work as expected? If they do, then the problem is somehow in the other applications. If input device switching doesn't work in that sample page, then please also provide a copy of the javascript console output. Thanks!
,
Apr 1 2016
Thank you for providing more feedback. Adding requester "tnakamura@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://sites.google.com/a/chromium.org/dev/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 1 2016
,
Apr 4 2016
,
Apr 14 2016
Friendly ping to kpkulkar@ to reply to the request noted in comment #4.
,
Apr 22 2016
One more ping to the original reporter to respond to comment #4. If we don't hear back by late next week, we may close this bug.
,
Apr 25 2016
The behaviour seems the same as crbug.com/598535 .
,
Oct 19 2016
Tested with latest chrome beta version 54.0.2840.59 and we are able to get the audio input from the external mic. Hence we can close this bug. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by meh...@chromium.org
, Mar 31 2016