- From: guidou via GitHub <sysbot+gh@w3.org>
- Date: Wed, 06 Mar 2024 09:27:55 +0000
- To: public-webrtc-logs@w3.org
Just FYI, the reason Chrome doesn't expose monitor devices is not that they are virtual or non-functioning. In fact, Chrome exposes some virtual devices, like the "Communications" device on Windows, and "Default" devices on all platforms, which map to real microphones. The reason Chrome doesn't expose monitor devices is that in our past experience they create a lot of confusion among users because they are not microphones. gUM in Chromium is designed (UI, audio processing, etc.) to support microphones. So, this is not a bug in the spec. It would be a feature request for Chromium, which Chromium has no interest to implement at the moment. -- GitHub Notification of comment by guidou Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/708#issuecomment-1980438092 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 6 March 2024 09:27:57 UTC