4 ms·
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
by jcelerier 5y ago
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.
- zibzab 5y agoWhat 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
- nyanpasu64 5y agoDoes `systemctl --user disable --now pulseaudio` help? Also you can use `enable --now` to enable and start at the same time.
- alias_neo 5y agoDon't forget to mask pulseaudio, just disabling it isn't enough.
- kzrdude 5y agoThe difference seems to be: disabled - the service is not started automatically masked - the service can't be started at all, even explicitly requested by user or app
- alias_neo 5y agoOn Ubuntu at least, I had to mask it otherwise pulseaudio was started again on reboot despite being disabled.
- WastingMyTime89 5y agoEverything 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.