When F34 initially came out, PipeWire broke Bluetooth audio on my laptop. But a couple of days later, a patch came in and just fixed it without me having to do anything. Every couple of days, a new update for it drops and it just keeps getting better and more stable.
This really seems like a good one-for-all solution for low-latency audio.
PipeWire and fixing the Linux Video Capture stack
11–20 of 38 posts
Re: PipeWire and fixing the Linux Video Capture stack
#12I've heard so much nice things about this, but just can't figure out how to get it to work. AUR has packages for replacing PA and jack with pipewire, but when I tired this I ended up with a dead ardour and not even timeshift could get me back to a working system.
A reboot is often required to integrate the session changes. https://wiki.archlinux.org/title/PipeWire Your session environment might also need to be aware of how to interact with PipeWire, which by default is via pulsaudio compatibility interfaces. Required (practically, probably pulled in with just pipewire): pipewire pipewire-media-session pipewire-pulse Recommended: pipewire-alsa pipewire-jack lib32-pipewire lib3…
> "A reboot is often required to integrate the session changes."
"To apply the changes you must restart your computer"
It is just sad.
Re: PipeWire and fixing the Linux Video Capture stack
#13Earlier quoted context omitted.
A reboot is often required to integrate the session changes. https://wiki.archlinux.org/title/PipeWire Your session environment might also need to be aware of how to interact with PipeWire, which by default is via pulsaudio compatibility interfaces. Required (practically, probably pulled in with just pipewire): pipewire pipewire-media-session pipewire-pulse Recommended: pipewire-alsa pipewire-jack lib32-pipewire lib3…
> "A reboot is often required to integrate the session changes." "To apply the changes you must restart your computer" It is just sad.
Now that it matched feature-wise the leading competitor, truly the year of the linux desktop is now!
Re: PipeWire and fixing the Linux Video Capture stack
#14I really wish Zoom could start using PipeWire for their screen sharing and video as soon as possible. Currently their desktop app gives a very interesting error if trying to share the screen from Wayland/sway. There is no need to only support Gnome on Ubuntu et.al. with PipeWire. The only way to use Zoom from my point of view is through their web app. And every time I start a meeting from their web interface, they're…
Have you tried installing zoom as a flatpak from flathub?
Using it at Fedora Silverblue 34 (Gnome 40 on Wayland) and screen sharing works (using it often at work).
Re: PipeWire and fixing the Linux Video Capture stack
#15Earlier quoted context omitted.
I have the following packages: pipewire-alsa 1:0.3.38-1.1 pipewire-jack 1:0.3.38-1.1 pipewire-jack-dropin 3-2 pipewire-media-session 1:0.3.38-1.1 pipewire-pulse 1:0.3.38-1.1 As well as systemctl --user enable \ pipewire.service \ pipewire-media-session.service \ pipewire-pulse.service and everything works great. I really like that I can use qjackctl to route every audio app nowadays.
What do I need to remove to get this working without any conflicts? You mentioned qjackctl, is there a reason I must keep using that instead of having everything defaulted to PW pipe
Everything uses PW pipe.
Pipewire implements the API of all the system it replaces. So you can keep using Jack routing tools while everything is actually using Pipewire.
Re: PipeWire and fixing the Linux Video Capture stack
#16Earlier quoted context omitted.
A reboot is often required to integrate the session changes. https://wiki.archlinux.org/title/PipeWire Your session environment might also need to be aware of how to interact with PipeWire, which by default is via pulsaudio compatibility interfaces. Required (practically, probably pulled in with just pipewire): pipewire pipewire-media-session pipewire-pulse Recommended: pipewire-alsa pipewire-jack lib32-pipewire lib3…
> "A reboot is often required to integrate the session changes." "To apply the changes you must restart your computer" It is just sad.
Restarting your whole session is enough but you must restart every connections between the sound server and applications. Restarting is just often the easiest way to do that because it shutdowns everything and rebooting is extremely fast nowadays but it is not required.
Re: PipeWire and fixing the Linux Video Capture stack
#17I really wish Zoom could start using PipeWire for their screen sharing and video as soon as possible. Currently their desktop app gives a very interesting error if trying to share the screen from Wayland/sway. There is no need to only support Gnome on Ubuntu et.al. with PipeWire. The only way to use Zoom from my point of view is through their web app. And every time I start a meeting from their web interface, they're…
Their app is really bad.
The good news is that their screen sharing based on gnome's private screenshot API should stop working altogether as Gnome 41 is securing those APIs.
Their webapp is quite bad as well though and behind in features especially on Firefox on which, for whatever reason, there's no gallery mode.
They should drop their crap desktop app and focus on building a descent webapp instead.
Re: PipeWire and fixing the Linux Video Capture stack
#18I really wish Zoom could start using PipeWire for their screen sharing and video as soon as possible. Currently their desktop app gives a very interesting error if trying to share the screen from Wayland/sway. There is no need to only support Gnome on Ubuntu et.al. with PipeWire. The only way to use Zoom from my point of view is through their web app. And every time I start a meeting from their web interface, they're…
Have you tried installing zoom as a flatpak from flathub? Using it at Fedora Silverblue 34 (Gnome 40 on Wayland) and screen sharing works (using it often at work).
Zoom screen sharing on wayland has been hacked around Gnome's private d-bus screenshot api.
It doesn't work in any other environment.
Re: PipeWire and fixing the Linux Video Capture stack
#19Earlier quoted context omitted.
What do I need to remove to get this working without any conflicts? You mentioned qjackctl, is there a reason I must keep using that instead of having everything defaulted to PW pipe
Does `systemctl --user disable --now pulseaudio` help? Also you can use `enable --now` to enable and start at the same time.
Don't forget to mask pulseaudio, just disabling it isn't enough.
Re: PipeWire and fixing the Linux Video Capture stack
#20I don't suppose anyone has hints for switching to wired headset on Ubuntu "on-plug".
I switched to pipewire recently and the experience for Bluetooth is amazing.
On an average day I have audio output set to HDMI while I listen to Spotify and work; when I plug in a wired headset for a meeting the gnome switcher dialog pops up but when I select headset, it doesn't work since moving to pipewire, output remains with HDMI and input from the laptop internal mic. I have to go into Sound every time and manually switch to headset out and headset mic.
It doesn't seem to have this issue if I'm not using HDMI output.