New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 610998 link

Starred by 3 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Bug



Sign in to add a comment

AudioManager device matching code sometimes selects unexpected device

Project Member Reported by guidou@chromium.org, May 11 2016

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.
 
Components: -Internals>Media>Audio Blink>WebRTC
this is webrtc related.
Cc: srnarayanan@chromium.org jansson@chromium.org
Components: -Blink>WebRTC Blink>WebRTC>Audio Blink>GetUserMedia>Mic
Owner: tommi@chromium.org
Status: Assigned (was: Untriaged)
Sending to Tommi for triage.

Comment 3 by tommi@chromium.org, May 13 2016

Cc: tommi@chromium.org
Owner: guidou@chromium.org

Comment 4 by guidou@chromium.org, May 14 2016

Labels: OS-Windows

Comment 5 by guidou@chromium.org, Sep 19 2016

Summary: AudioManager device matching code sometimes selects unexpected device (was: AudioManager device matching code sometimes selects unexpected)
[Re-triage] What's the status of this bug? If still valid, should it have lower priority?

Comment 7 by guidou@chromium.org, Jun 26 2017

Status: Available (was: Assigned)
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.

Comment 8 by guidou@chromium.org, Jun 26 2017

Owner: ----
Labels: -Pri-2 Pri-3
Owner: solenberg@chromium.org
Status: Assigned (was: Available)
Guido, is this still relevant? Looks like the associated WebRTC (and Chromium) bugs have been fixed.

Sign in to add a comment