Sender | Message | Time |
---|---|---|
26 Feb 2023 | ||
Microphone issues. On Linux, using pipewire and pipewire-pulse. Firefox 110.0 (64-bit), stock/default profile. Microphone works on https://mozilla.github.io/webrtc-landing/gum_test.html, although it seems there is a non-ideal filter, noise reduction going which "cuts" my voice. Microphone does NOT work on meet.jit.si, app.element.io, etc. When I check with pulsemixer and/or helvum, I see Firefox connects to the correct audio source (the microphone/input), but at "best" I hear some noise on the other device. This is also an issue on Chromium, with the additional issue that on it the GUM test does not work. So it is not a Firefox specific issue, but a Web browser issue? When I capture/record the mic with a native system app (e.g. | 11:53:47 | |
Download 2023-02-22T17-45-52UTC.png | 11:53:53 | |
This is how Firefox connects to the audio source/mic in meet.jit.si. It's the same for the gum test. | 11:53:59 | |
I’ve been using pipewire + Firefox + jitsi without issue fwiw (not sure about pipewire-pulse) | 11:54:00 | |
that's weird | 11:55:00 | |
specific webapps on firefox are not working ? Have you tried other things on firefox (like call.element.io, or bigbluebutton if you have access to an instance) | 11:55:55 | |
or on Chrome ? | 11:55:59 | |
In reply to @mindtree:matrix.org nice, so it is really an issue on my end/setup. i do not have any config files on ~/.config/pipewire or ~/.config/pulse. my nix audio config is
| 12:00:58 | |
it seems pretty close to what I have | 12:03:21 | |
I just don't have the alsa.support32bit , but it shouldn't matter for Firefox | 12:03:48 | |
I'm also using pipewire from the unstable channel, not sure if it changes things | 12:04:14 | |
In reply to @Minijackson:matrix.orgon firefox with a clean/stock profile, i just tried call.element.io and web.whatsapp.com. same issue. on firefox, only https://mozilla.github.io/webrtc-landing/gum_test.html has worked so far. | 12:18:36 | |
My profile is also very similar I think (though I don't have rtkit or wireplumber enabled). I'm also on GNOME - not sure if the desktop audio routing has anything to do with it? | 12:20:48 | |
In reply to @Minijackson:matrix.orgi disabled alsa there, so i suppose it would not make a difference. but i had tested with alsa enabled as well, and had same issue (ofc, like you said, firefox only supports pulse, so alsa should not make a difference). do you have alsa enabled anyway? | 12:21:18 | |
In reply to @mindtree:matrix.orgi should try it on gnome on a clean /home/user. i'm suspect something might be going on on my xmonad / user profile | 12:22:38 | |
In reply to @Minijackson:matrix.orgi'm on unstable as well. | 12:23:27 | |
can you try on a NixOS live USB ? | 12:23:56 | |
the GNOME live CD should be using PipeWire + Wireplumber, since it's the default when installing | 12:24:20 | |
(if not, you can make your own ISOs) | 12:24:43 | |
Minijackson: oh true, i'll try that. downloading the ISO right now | 12:26:11 | |
Minijackson: i just tried with nixos-gnome-22.11.2720.50c23cd4ff6-x86_64-linux.iso didn't work either. i tested on meet.jit.si and web.whatsapp.com. again, only https://mozilla.github.io/webrtc-landing/gum_test.html kinda worked | 13:36:59 | |
so i suppose this is a nixos/driver issue idk. i remember on Arch Linux it worked. I'll have to grab an Ubuntu, etc ... ISO to test it | 13:37:53 | |
just for reference, the pipewire and pulse /etc configs are | 13:38:38 | |
* just for reference, nixos-gnome-22.11.2720.50c23cd4ff6-x86_64-linux.iso pipewire and pulse /etc configs are | 13:38:48 | |
Download nixos-gnome-22.11.2720.50c23cd4ff6-x86_64-linux-etc-pipewire-pulse.tar | 13:39:28 | |
In reply to @yuu:matrix.orgoops, this contains only symlinks | 13:43:38 | |
Minijackson: oh no facepalm i legit tar --create --file . i suppose i should have added another option for directories | 13:46:55 | |
there's a --dereference I think | 13:47:22 | |
Minijackson: oh right, for a moment i forgot we are on NixOS which symlinks everything 🥲👍️ | 13:48:22 | |
i just tested on Ubuntu that uses pipewire and pipewire-pulse and had the same issue. Also, there I also tested with native GNOME app cheese, which had the same issue, and I reproduced this on NixOS. They connect to the correct audio source/input (the mic). So all I can have left, is that it is an issue with pipewire, pipewire-pulse, or some odd codec, filter. | 15:13:16 |