New issue
Advanced search Search tips

Issue 863143 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

Does not respect sound output device settings correctly

Reported by mpupi...@gmail.com, Jul 12

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36

Example URL:
None - OS issue

Steps to reproduce the problem:
1. Buy an Arctis 7 headset
2. Go to "App volume and device preferences" and set chrome to use the chat channel as the output device
3. Observe that it outputs audio to the game channel instead

What is the expected behavior?
Should output to the chat channel, like every other application does.

What went wrong?
You hired terrible programmers.

Did this work before? N/A 

Is it a problem with Flash or HTML5? HTML5

Does this work in other browsers? Yes

Chrome version: 67.0.3396.99  Channel: stable
OS Version: 10.0
Flash Version: 

Contents of chrome://gpu: 

Do not try and tell me this is an issue with the headset or driver or Windows 10 because every other application can output to the chat channel when instructed to.
 
Labels: Needs-Triage-M67
Cc: susan.boorgula@chromium.org
Labels: Triaged-ET TE-Hardware-Dependency
mpupilli@ Thanks for the issue.

As this issue needs to be tested with Arctis 7 headset, this is unavailable at TE end to test further.
Hence adding 'TE-Hardware-Dependency' label for further help in triaging the issue.

Thanks.. 

Comment 3 by dbbrooks@chromium.org, Jan 17 (5 days ago)

Owner: maxmorin@chromium.org
maxmorin@ for routing. 

It sounds like this might not be specific to the Arctis 7 headset. Maybe we can try to repro the issue with any bluetooth, or usb headset? I bet there's one floating around the office. If I can find one I'll try to repro the issue.

Comment 4 by mpupi...@gmail.com, Jan 18 (5 days ago)

It's definitely not specific. The arctis presents itself as two separate
audio output devices so you might be able to replicate with any two. Thanks
for revisiting.

On Thu, 17 Jan 2019, 23:33 dbbro… via monorail <
monorail+v2.4268122611@chromium.org wrote:

Comment 5 by maxmorin@chromium.org, Yesterday (45 hours ago)

Cc: maxmorin@chromium.org henrika@chromium.org
Owner: guidou@chromium.org
Guido: This might be due to the mapping of "" to default device name (similar to  https://crbug.com/880180 ), could you take a look?

+Henrik since he's been poking at Windows audio code recently.

Comment 6 by henrika@chromium.org, Yesterday (44 hours ago)

Cc: ossu@chromium.org
Labels: -Pri-2 Pri-3
Obligatory reminder: "Please keep discussions respectful and constructive. See our code of conduct."

https://chromium.googlesource.com/chromium/src/+/master/CODE_OF_CONDUCT.md

Next, upgrade to latest stable version (71) and get back with new results.

Reducing priority since tied to unique external hardware.

Comment 7 by henrika@chromium.org, Yesterday (44 hours ago)

Labels: Needs-Feedback

Sign in to add a comment