webrtc audio desktop capture does not work with surround sound devices
Reported by
f...@bebo.com,
Mar 16 2017
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3043.0 Safari/537.36 Steps to reproduce the problem: 1. Set your default audio device to a surround sound setup (e.g. https://www.razerzone.com/surround#product_specs and enable virtual surround sound) 2. use a site / extension which support desktop sharing with "audio" 2.1. So we can reproduce this easily I hacked up a version of the webrtc-experiments desktopCapture-p2p: https://github.com/fpn/Chrome-Extensions/tree/master/desktopCapture-p2p 2.2. Install the extension 2.3. Click the Extension Button in the Chrome toolbar 2.4 On "Your Entire Screen" make sure "Share audio" is selected and click "Share" 3. {name: "TrackStartError", message: "", constraintName: ""} Big error message comes up, if you set a breakpoint at the top of getUserMediaError(), you can see it is a TrackStartError What is the expected behavior? desktop sound is sent via webrtc What went wrong? {name: "TrackStartError", message: "", constraintName: ""} Did this work before? No Chrome version: 59.0.3043.0 Channel: canary OS Version: 10.0 Flash Version: Quite a few headsets (Razer, Logitech, ..) come with Virtual Surround Software which makes itself the default audio device - the same is true for some laptops with surround sound and of course real surround sound setups.
,
Mar 21 2017
,
May 20 2017
Can confirm that I'm running into the same issue (I'm on Chrome v58). I have an extension(https://chrome.google.com/webstore/detail/huegasm-for-philips-hue-l/mbjanbdhcpohhfecjgbdpcfhnnbofooj) which leverages Chrome's ```chrome.desktopCapture.chooseDesktopMedia(['screen', 'audio'])``` to request the user's screen+audio stream. The subsequent call to ```navigator.mediaDevices.getUserMedia()``` with the retrieved chromeMediaSourceId produces a TrackStartError when surround sound is turned on.
,
Feb 14 2018
,
Feb 15 2018
,
Mar 9 2018
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by msrchandra@chromium.org
, Mar 20 2017