-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Desktop] Support capture of monitor devices at Linux #11691
Comments
@rebron What does "Chromium/waiting upstream" tag mean? The change requested in Brave in the exact opposite path of what Chromium authors have decided to take https://bugs.chromium.org/p/chromium/issues/detail?id=1155954. If that is an issue this bug should probably be closed. |
@guest271314 sorry, I removed the |
@bsclifton FWIW, a brief synopsis of relevant workarounds to capture entire system audio output, and specific playback devices guest271314/SpeechSynthesisRecorder#17 (comment), guest271314/SpeechSynthesisRecorder#17 (comment), https://github.com/guest271314/setUserMediaAudioSource. Notice that the Web has not broken becuase the user defined which devices on their machine they decide to capture with |
@bsclifton A short list of Chromium FUGU requests that are still open Issue 1136480: FUGU Implement capture of system and application audio output to headphones and speakers https://bugs.chromium.org/p/chromium/issues/detail?id=1136480; Issue 1100101: Ability to create virtual microphone and camera devices https://bugs.chromium.org/p/chromium/issues/detail?id=1100101; Issue 1151308 in chromium: Implement Media Capture Automation https://bugs.chromium.org/p/chromium/issues/detail?id=1151308. |
@bsclifton Importantly, note that this issue Default device selection and listing inconsistencies
thereafter followed by the opening of this issue default audio output should be first in the enumerateDevice returned list #756 https://github.com/w3c/mediacapture-main/issues/756
This bug is basically the same as w3c/mediacapture-output#113, but I filed it here because enumerateDevices is defined in this spec. If the former is true and correct the latter is moot due to 1)
and 2)
and capable of confusing users in the field that actually are intending to capture
Since Chromium is ostensibly FOSS, and Brave, AFAIK, is not bound to repeat verbatim what Chromium source code does, else there would be no reason for Brave, Brave browser is well-suited to implement at least the capture of monitor devices at |
Description
Chromium refuses to support capture of monitor devices at
navigator.mediaDevices.getUserMedia({audio: true})
https://bugs.chromium.org/p/chromium/issues/detail?id=931749.Support capture of monitor devices at Brave browser.
Steps to Reproduce
navigator.mediaDevices.getUserMedia({audio: true})
navigator.mediaDevices.enumerateDevices()
afternavigator.mediaDevices.getUserMedia({audio: true})
Actual result:
Monitor devices are not listed at Linux.
Expected result:
Monitor devices to be listed at
enumerateDevices()
and capable of being captured bygetUserMedia()
.Reproduces how often:
Easily reproduced.
Brave version (brave://version info)
1.16.12 Chromium: 86.0.4240.30 (Official Build) nightly (64-bit)
Version/Channel Information:
Other Additional Information:
Miscellaneous Information:
The text was updated successfully, but these errors were encountered: