Audio in device intermittently stops working, Unexpexted OutputNodeVolumeChanged received |
||||||||
Issue descriptionChrome Version: Asus chromebox, panther, chrome for meetings 56.0.2924.110 57.0.2987.146 58.0.3029.68 What steps will reproduce the problem? (1)Connect Buddy USB Audio card, connect mic to audio card input. (2)Start a videoconference (3)Wait for a hour, or so. What is the expected result? video/audio should be working with no disconnections What happens instead? intermittently, mic in stops working. Full logs shared to @google.com https://drive.google.com/a/google.com/file/d/0B-g52zibXA02RlNxZ295c1QwbXM/view?usp=sharing Have following interesting in logs: ui.20170426-020005: [754:754:0426/020008.129104:ERROR:cras_audio_handler.cc(598)] Unexpexted OutputNodeVolumeChanged received on node: 0x600000000 ui.20170426-020005: [1:44:0429/143629.190355:WARNING:webrtcvoiceengine.cc(2314)] SetOutputVolume: no recv stream775620115 Workaround is to change hangouts settings audio-in device to different device, save and then change back to original device.
,
May 4 2017
,
May 4 2017
,
May 4 2017
,
May 11 2017
Setting as assigned since it has an owner.
,
May 11 2017
assigning to mats in case this looks familiar marchuk - have we seen this on later builds?
,
May 11 2017
It's happening to a number of our units running 56.0.2924.121
,
Jun 22 2017
Team, FYI the customer who reported this issue found out that this was not a Chrome OS problem, issue was specific to the signal they were using as the microphone feed and the fact that it was not a direct connected microphone. They have resolved the problem by changing the signal type so we might probably want to close this bug. Thanks for your time and efforts.
,
Jul 5 2017
,
Nov 7 2017
Closing as per #7 |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by marchuk@chromium.org
, May 4 2017