Pipewire: Difference between revisions

From miki
Jump to navigation Jump to search
Line 11: Line 11:
# Connect to it with
# Connect to it with
PULSE_SERVER=tcp:<ip>:4713 pactl info
PULSE_SERVER=tcp:<ip>:4713 pactl info
* [https://pipewire.pages.freedesktop.org/wireplumber/ WirePlumber - documentation]


== References ==
== References ==

Revision as of 10:09, 25 April 2022

Pipewire is the new sound system on Linux, meant to replace Pulseaudio.

Links

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

Bluetooth

  • To change bluetooth device selected profile:
# See available profile and device id with 'pactl list'
pactl set-card-profile bluez_card.38_18_4C_4B_6A_3A a2dp-sink-sbc_xq

Troubleshooting

Setting and keeping bluetooth profile for headset

In principe WirePlumber should remember the last selected profile.

When using pipewire-media-session, the default profile could be selected in bluez-monitor.conf, but this file no longer exists with WirePlumber.

Crackling / Stuttering audio

This applies in a VM. Not sure these apply when PipeWire is run on the host.