- From: Bug-Reaper via GitHub <sysbot+gh@w3.org>
- Date: Thu, 29 Feb 2024 23:55:08 +0000
- To: public-webrtc-logs@w3.org
@jan-ivar Just for reference, the exposed monitor devices are 100% functional. These devices function exactly as intended and have practical application for music visualization and other exotic audio configurations. While I agree specs are unlikely to force a vendor's hand, I want to acknowledge there are use-cases where these devices are the one's a user/developer intended to use. The mistake that a virtual device is "non-functioning" seams earnest and with good intention. That said it is quite frustrating to learn the input device you configured is arbitrarily blacklisted by a vendor despite it's availability. A user could disable monitor devices if they wanted on the system level. I'd imagine if we wanted to disable monitor devices by default it'd be better to take that upstream to the audio-libraries as opposed to have vendors go against spec b/c they do not commonly use the feature. -- GitHub Notification of comment by Bug-Reaper Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/708#issuecomment-1972169494 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 29 February 2024 23:55:09 UTC