-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Broo.monitor doesn't get listed as an input device. Only "Broo" exists as an output. #15
Comments
pactl load-module module-remap-source master=Broo source_name=Phone_Mic source_properties=device.description=PhoneMic Solution for anyone with the same problem |
First, please mention your OS, Piepwire/PulseAudio version, etc.
GNOME settings is not listing the Monitor input, as for some reason it does not list the Monitor inputs and only lists the explicit input nodes.
|
Weird, I have the same Pipewire version on Debian Testing. There have been other Arch users too. Can you check your packages? I have something like: $ dpkg -l | grep pipewire | grep ii
ii gstreamer1.0-pipewire:amd64 0.3.80-2 amd64 GStreamer 1.0 plugin for the PipeWire multimedia server
ii libpipewire-0.3-0:amd64 0.3.80-2 amd64 libraries for the PipeWire multimedia server
ii libpipewire-0.3-common 0.3.80-2 all libraries for the PipeWire multimedia server - common files
ii libpipewire-0.3-modules:amd64 0.3.80-2 amd64 libraries for the PipeWire multimedia server - modules
ii pipewire:amd64 0.3.80-2 amd64 audio and video processing engine multimedia server
ii pipewire-alsa:amd64 0.3.80-2 amd64 PipeWire ALSA plugin
ii pipewire-audio 0.3.80-2 all recommended set of PipeWire packages for a standard audio desktop use
ii pipewire-bin 0.3.80-2 amd64 PipeWire multimedia server - programs
ii pipewire-pulse 0.3.80-2 amd64 PipeWire PulseAudio daemon |
All my packages are up-to-date (atleast pacman claims so) |
Tbh this is sort of a known issue, but what you mentioned is weird/new, because Discord, Firefox, and most applications typically detects Monitor sources but for you it isn't. GNOME not showing it was expected (as I mentioned earlier) I had tried using a duplex in pipewire, but reverted it due to unmuting problem (b2f25e0). |
Unfortunately facing the same issue in Fedora 39, in particular with Zoom. The noted command:
... did not work. I am however not having issues with other apps like Discord, Firefox, OBS, etc. |
@AidanGCr Yes, that's what I know and face as well. As mentioned earlier, Zoom et al probably don't recognize Monitor for some reason (bad programming with Linux as an afterthought). You can use easyeffects for the time being if you don't want to bother with commands. Easyeffects creates a dedicated source and it works with Zoom. (Do see this comment in a pinned issue). Actually using "duplex" with pipewire solves the issue with Zoom but it was unmuting automatically (see the linked commit). I think I should report to pipewire devs. |
Hi, Pipewire has released v1, and after using duplex the sink is no longer automatically unmuting, so I reintroduced that commit. Using duplex makes a dedicated source which is visible to all applications like Zoom. Please update and let me know. |
Though for some reason EasyEffects isn't working (as mentioned in the OG commit). If someone uses EasyEffects and knows its quirks, please let me know. |
Closing next week or later if no follow-ups. |
This is definitely fixed now for both server cases with #24. |
pactl list short sinks:
pactl list short sinks
In GNOME (Or any other app) i cannot see Broo being listed as an input device. The output device works as an input device, but i am unable to use it in most apps (eg Discord) since its not listed as input
The text was updated successfully, but these errors were encountered: