- From: guest271314 via GitHub <sysbot+gh@w3.org>
- Date: Tue, 04 Aug 2020 14:29:52 +0000
- To: public-webrtc-logs@w3.org
@alvestrand > Why does this need special treatment? > Wouldn't a sound card just be another input device? Agree. Reading this language https://chromium-review.googlesource.com/c/chromium/src/+/1064373/ ``` PulseAudio: Filter out unavailable inputs and refuse to open monitor inputs If there are no available inputs, PulseAudio will, for some reason, select the monitor of the current default sink as the default source. ... this CL also explicitly returns invalid AudioParameters for monitor devices, and explicitly fails to open them as inputs - to be on the safe side. ``` it appears that Chromium just "refuse" to open certain devices - rather than fix the actual problem with PulseAudio being described, where Mozilla Firefox and Nightly do not have that problem, and using `pavucontrol` as a workaround confirms that selection of monitor devices is possible. Perhaps you can actually fix whatever problem was reported at https://issuetracker.google.com/79580580 re PulseAudio in order for Chromium to be in alignment with your evaluation? -- GitHub Notification of comment by guest271314 Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/629#issuecomment-668630693 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 4 August 2020 14:29:54 UTC