Pipewire
Jump to navigation
Jump to search
Pipewire is the new sound system on Linux, meant to replace Pulseaudio.
Links
- PipeWire - Debian Wiki.
- PipeWire - ArchLinux
- PipeWire on HackerNews
- PipeWire (old) configuration docs
- Speak about Pulse network transport:
# Setup server with pipewire-pulse -a tcp:4713 # Connect to it with PULSE_SERVER=tcp:<ip>:4713 pactl info
References
Configuration files:
- /usr/share/pipewire
- /usr/share/wireplumber
Commands
# View status
systemctl --user status pipewire
# Use PipeWire instead of JACK
pw-jack SOMEAPP
# PipeWire process viewer (quantum usage...)
pw-top
# Setup sinks, sources, audio devices
pw-link
qjackctl # Graphical tool, leveraging on JACK
qpwgraph # Alternative, pipewire native
# Command line
pw-cli
> info all
Troubleshooting
Setting and keeping bluetooth profile for headset
We want to use the profile sbc sbc_xq for our BT headset Sony WH-1000XM3.
- Set the profile manually - profile should be persistent on reboot / reconnect.
- In principe WirePlumber should remember the last selected profile.
- See [1]
- Configure profile
- When using pipewire-media-session, the default profile could be selected in bluez-monitor.conf, but this file no longer exists with WirePlumber.
- (UPDATE - Archlinux - Pipewire) Edit /etc/wireplumber/bluetooth.lua.d/51-bluez-config.lua (or ~/.config/wireplumber/bluetooth.lua.d/51-bluez-config.lua):
bluez_monitor.properties = {
["bluez5.enable-sbc-xq"] = true,
["bluez5.enable-msbc"] = true,
["bluez5.codecs"] = "[sbc sbc_xq]",
}
Crackling / Stuttering audio
This applies in a VM. Not sure these apply when PipeWire is run on the host.