Those are the only instructions I need to run to have a fully working Pipewire setup that is compatible with PulseAudio, Jack and ALSA:
$ yay -Rcns pulseaudio-jack
# note that pipewire-jack-dropin is an AUR package
$ yay -S pipewire-{jack,jack-dropin,alsa,pulse}
$ systemctl --user enable pipewire pipewire-pulse pipewire-media-session
$ systemctl reboot
# done
If you had told me a day ago that replacing pulseaudio and jack would be that smooth I would have never believed you.
Jack
Bitwig 3.3 will not work out of the box with pipewire-jack-dropin, except I manually set a buffer size like this PIPEWIRE_LATENCY="256/48000" pw-jack bitwig-studio
.
2021-04-03
To get reasonably good call quality:
$ rg -i msbc /etc/pipewire/media-session.d/bluez-monitor.conf
36: # MSBC is not expected to work on all headset + adapter combinations.
37: bluez5.msbc-support = true
Thank you Andreas and contributors.
Would you like to add a comment/clarification as not to run
systemctl --user enable ...
(orsystemctl --user start ...
) as root, but as the normal user? Otherwise the user (running it viasu
) gets a confusing errorFailed to connect to bus: Operation not permitted
. As per https://bbs.archlinux.org/viewtopic.php?id=223737: "Don't run systemd services as root, run them as a regular user."