Issue metadata
Sign in to add a comment
|
Failed input audio on Mac OSX |
||||||||||||||||||||||||
Issue descriptionVersion: many, currently 50.0.2661.94 OS: Mac OSX, currently 10.11.4 What steps will reproduce the problem? (1) Enter a Google Hangout or other VC app within Chrome (2) Video and audio output work, but input via headset or built-in microphone fails (other attendees/call recipients hear no audio) This problem has been occurring for me and others in Hangouts meetings intermittently for several months.. on canary and stable. I have even had the mic input work, go out, come back, and go out again within the same session. It seems to be limited to Chrome on OSX and not specific to Hangouts, some notes from my occurrence yesterday: - Mac system audio config and testing of the mic show it working properly - Switching to another browser and entering the Hangout, the mic works - Switching tabs/profiles/launching a new Chrome window still fails - Switching audio devices, turning mute on/off the mic still fails - Other audio input tests within Chrome fail, ie https://test.webrtc.org/? reports this audio capture failure, with headset or default device: [ FAILED ] No active input channels detected. Microphone is most likely muted or broken, please check if muted in the sound settings or physically on the device. Then rerun the test. I am happy to help troubleshoot further and have left my laptop/Chrome in the failed state (if it continues). May be related to or potential duplicate of chromium:504363, though some users there report different behavior, namely successful tests outside of Hangouts/Gmail.
,
May 12 2016
,
May 12 2016
Thanks for reporting hcm@. I am aware of this issue and have been working a long time on trying to resolve it (see crbug.com/549021 ). We have done some changes in M52 that has resulted in positive feedback from several users. Are you able to try M52 for a period of time and report back?
,
May 12 2016
I knew there must be an issue out there but didn't find that one- thanks, glad we're trying to address. Will try 52 for a while and report back.
,
May 12 2016
Thanks. If you hit this often on your machine, perhaps you are willing to try a special build with extra logging to narrow down more. I have so far failed to reproduce consistently on any of my devices. Just FYI, if it happens, you can also try: sudo killall coreaudiod from command line and see if that helps. Not a solution, just a test.
,
May 12 2016
Willing to run a build if it would help, but like you say, hard to repro consistently. Probably has happened five times over last 6 months for me.
,
May 12 2016
Thanks. Would be great if you could use M52 consistently then and report back. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by hcm@chromium.org
, May 12 2016