AudioManager device matching code sometimes selects unexpected device |
|||||||||
Issue description<b>Version: <Kenneth, what is the frequency?></b> OS: Windows What steps will reproduce the problem? (1) Use an audio adapter that creates a single audio input device but multiple output devices. The issue has been reported to occur with Cirrus Logic CS4206B (AB 40) (2) Try to use an application that uses the renderToAssociatedSink constraint with getUserMedia. What is the expected output? Output goes to the headphones output device. What do you see instead? Output goes to digital audio (S/PDIF) output device. See crbug.com/604523 and https://bugs.chromium.org/p/webrtc/issues/detail?id=5854 It seems that the problem is that all output devices are actually associated with the only input device and the matching code does not always select the match that the user expects. For now, we have mitigated the problem by making the renderToAssociatedSink constraint false by default.
,
May 13 2016
Sending to Tommi for triage.
,
May 13 2016
,
May 14 2016
,
Sep 19 2016
,
Jun 26 2017
[Re-triage] What's the status of this bug? If still valid, should it have lower priority?
,
Jun 26 2017
This bug makes the "googRenderToAssociatedSink" getUserMedia constraint to produce unexpected results for Windows users with the affected hardware. Marking this bug as available, since the audio team is probably better equipped to deal with this bug, which requires Windows + the appropriate hardware to reproduce.
,
Jun 26 2017
,
Oct 6 2017
,
Aug 1
,
Nov 13
Guido, is this still relevant? Looks like the associated WebRTC (and Chromium) bugs have been fixed. |
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by yini...@chromium.org
, May 11 2016