setSinkId doesn't work in Chromium 64 bit
Reported by
porsa...@gmail.com,
Apr 5 2016
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.110 Safari/537.36 Example URL: https://webrtc.github.io/samples/src/content/devices/multi/ Steps to reproduce the problem: 1. Have 2 or more audio outputs available 2. Visit https://webrtc.github.io/samples/src/content/devices/multi/ 3. Change audio output device What is the expected behavior? Audio should play through selected audio device What went wrong? Audio doesn't play through selected audio device Did this work before? No Is it a problem with Flash or HTML5? HTML5 Does this work in other browsers? Yes Chrome version: 49.0.2623.110 (64 bit) Channel: stable OS Version: 10.0 Flash Version: Shockwave Flash 21.0 r0 This works fine on the 32 bit version.
,
Apr 8 2016
guidou@ can you have a look? I don't know exactly when this was supposed to be supported, but I would assume for M49 it should?
,
Apr 8 2016
I tried and it works fine. Maybe the user didn't give permission to use audio devices?
,
Apr 8 2016
I tried it with my Plantronics headset (D100M USB) which works fine in the 32 bit version. Then I tried a virtual sound card which actually worked for both 32 and 64 bit, so i'm pretty sure it's not permission issues.. I will test with a simple USB soundcard on Monday as well. When I switch to the Plantronics output I get this error: [4720:3352:0405/154629:ERROR:audio_manager_base.cc(264)] Invalid audio output parameters received; using fake audio path. Channels: 0, Sample Rate: 48000, Bits Per Sample: 16, Frames Per Buffer: 480
,
Apr 13 2016
That error occurs when the OS returns invalid values as hardware audio parameters. See https://code.google.com/p/chromium/codesearch#chromium/src/media/audio/audio_manager_base.cc&q=audio_manager_base.cc&sq=package:chromium&type=cs&l=256 It could be a driver issue, or some other environment-specific bugs.
,
Apr 13 2016
porsa@ - does the D100M USB work with any other 64-bit apps on that Windows 10 machine? Also, have you had a chance to run the "simple USB soundcard" test that you mentioned in comment #4?
,
Apr 15 2016
Ok, I got it figured out, apparently there is a "fix" available from plantronics which is described here: http://www.plantronics.com/us/support/kb/detail.jsp?vfurl=/articles/en_US/Troubleshooting/Computer-Headset-Troubleshooting-No-Audio-When-Using-Google-Chrome-on-Windows-8&retURL=/articles/en_US/How_To/RN19678®ion=us&c=B2B_Cordless&lang=en_US After changing that setting I was able to get sound to the headset when choosing the headset specifically, but not when setting it as default Communication device and choosing the "comunication" output, but at this point I think this might be an issue Plantronics needs to fix instead. Thanks a lot for the help troubleshooting, and sorry for bringing it up here when I should have went to Plantronics to begin with. By the way, I also got a regular usb soundcard tested which worked fine.
,
Apr 15 2016
porsager@: thanks for testing and providing feedback. Closing this bug. |
||||
►
Sign in to add a comment |
||||
Comment 1 by yini...@chromium.org
, Apr 7 2016