Hello world :-) I was just about to report request to enable PulseAudio by default in Chrome just as it is in Firefox, but I found this thread that requests disabling the PulseAudio by default: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216327 PulseAudio distinguishes input and output devices and the sound streams so you can list them and adjust parameters such as volume per stream rather than per device. This is really important for WebRTC where you can easily and quickly switch between different devices for instance web camera microphone or internal laptop microphone or external microhpne. In Firefox that uses PulseAudio I can see many input devices and I can select among them. In Chromium that uses only ALSA by default I can see only "default" microphone and this is not the one that works nor any other input device. I did a compilation of Chromium with PulseAudio enabled but each pkg update tells me it wants to replace it with a binary that has defaults (no PulseAudio). Is PulseAudio still not welcome in Chromium by default? Best regards, Tomek
I'm experiencing an issue as well but not sure if it's due to this or some other weirdness. But I've noticed that on my framework laptop on FreeBSD 14.0-CURRENT #0 main-n255077-490a0f77de7, Chromium ignores my mute requests (either via Fn key or KDE Plasma UI), but respects volume increase / decrease requests. Firefox however respects all three and will (un)mute immediately.
I would like to see PulseAudio enabled by default in Chromium too. My microphone does not work in WebRTC using default Chromium, it works correctly in Chromium built with PulseAudio enabled. The only problem is that to build Chromium I need to use an external server, and it takes 12+ hours. It is impossible to build the port on a laptop (needs to much RAM). Maybe, a good solution would be a slave port, something like 'chromium-pulseaudio'.