From Gentoo Wiki
(Redirected from Pipewire)
Jump to:navigation Jump to:search
As of early 2022, PipeWire is still in active development. Some things may still not be fully integrated, tested, or implemented, and there may be large changes. It can work well for some, though the experience is not guaranteed to be perfect, free of issues, or bugs.
This article describes the state-of-affairs in ~arch rather than stable for now. This will change in future once things slow down a bit.

PipeWire is a low-latency, graph-based, processing engine and server, for interfacing with audio and video devices. It can be used to support use-cases currently handled by ALSA, PulseAudio, and/or JACK, and aims to improve handling of audio and video under Linux.

Some key features of PipeWire include:

  • Minimal latency capture/playback of audio and video.
  • Real-time multimedia processing.
  • Multi-process architecture allowing multimedia content sharing between applications.
  • Seamless support for PulseAudio, JACK, ALSA, and GStreamer.
  • Applications sandboxing support with Flatpak, with a security model that facilitates interacting containerized applications.

PipeWire currently ships a PipeWire daemon, an example session manager, tools to introspect and use the PipeWire Daemon, a library to develop PipeWire applications and plugins, and the SPA (Simple Plugin API) used by both the PipeWire daemon and the PipeWire library.



CONFIG_SND_PROC_FS and CONFIG_SND_VERBOSE_PROCFS is needed for newer versions of media-video/wireplumber to work.

Device Drivers  --->
    <*> Sound card support  --->
        <*> Advanced Linux Sound Architecture  --->
            [*]   Sound Proc FS Support
            [*]     Verbose procfs contents

USE flags

The use of PipeWire by applications is governed by the screencast USE flag.

USE flags for media-video/pipewire Multimedia processing graphs

X Enable audible bell for X11
bluetooth Enable Bluetooth Support
doc Add extra documentation (API, Javadoc, etc). It is recommended to enable per package instead of globally
echo-cancel Enable WebRTC-based echo canceller via media-libs/webrtc-audio-processing
extra Build pw-cat/pw-play/pw-record
gstreamer Add support for media-libs/gstreamer (Streaming media)
jack-client Install a plugin for running PipeWire as a JACK client
jack-sdk Use PipeWire as JACK replacement
lv2 Allow loading LV2 plugins via media-libs/lv2
pipewire-alsa Replace PulseAudio's ALSA plugin with PipeWire's plugin
ssl Enable raop-sink support (needs dev-libs/openssl)
system-service Install systemd unit files for running as a system service. Not recommended.
systemd Enable use of systemd-specific libraries and features like socket activation or session tracking
test Enable dependencies and/or preparations necessary to run tests (usually controlled by FEATURES=test but can be toggled independently)
udev Enable virtual/udev integration (device discovery, power and storage device support, etc)
v4l Enable support for video4linux (using linux-headers or userspace libv4l libraries)
zeroconf Support for DNS Service Discovery (DNS-SD)


Set the screencast USE flag on the ebuilds for which PipeWire support is desired, and PipeWire media-video/pipewire will be pulled in as a dependency. Alternatively, set the screencast USE flag in make.conf. After changing USE flags, rebuild affected packages:

root #emerge --ask --verbose --changed-use --update --deep @world

Alternatively, PipeWire may be emerged independently, though the previous method is usually what is required:

root #emerge --ask media-video/pipewire


PipeWire is still in heavy development - configuration paths, options and defaults can change from one minor release to another - if things on the system do not align with documentation, double check or at least make a backup before making changes.

Detailed, non Gentoo-specific, configuration documentation can be found at the project's official wiki. Typically things work reasonably well out of the box, and PipeWire's global configuration is usually best left unmodified.

Global PipeWire configuration can be changed by editing the /etc/pipewire/pipewire.conf file, and ~/.config/pipewire/pipewire.conf may be used for per-user configuration. Additionally, PipeWire recognizes multiple environment variables that allow these settings to be changed, per-user, or for individual commands.

In principle, existing PulseAudio or JACK tools can be used to interact with PipeWire when it is set up to behave as a JACK and/or PulseAudio server, but currently only parts of the respective APIs have been implemented.



PipeWire provides socket and service files when built with the systemd USE flag. The following systemctl command enables systemd's socket activation of PipeWire for the current user:

user $systemctl --user enable --now pipewire.socket

The socket activation only starts the service when required, which is usually sufficient. Alternatively the user service can be always started when the user logs in by replacing pipewire.socket with pipewire.service:

user $systemctl --user enable --now pipewire.service

Starting with 0.3.39, PipeWire also requires media-video/wireplumber to run properly:

user $systemctl --user enable --now wireplumber.service

In these cases, the --now flag is optional but probably safe to use as starting PipeWire with default configuration merely allows using new interfaces but does not change the existing ones i.e. non-PipeWire clients continue using the same libraries and services they were using previously. To also replace PulseAudio and/or JACK, follow the instructions in the relevant section.

OpenRC with elogind (any of Gentoo's desktop profiles)

PipeWire relies on a working D-Bus user daemon with an XDG compliant environment. Both requirements should be automatically met when a desktop profile is used, thanks to their elogind integration. On such systems, starting PipeWire is as simple as running the pipewire binary.

There is no truly standardized way (outside of systemd) to load PipeWire when starting a graphical shell, and users need to choose the correct approach based on how their graphical environment is started. The following table lists some ways to launch PipeWire when logging into a graphical environment:

In all cases where systemd user services are not being used, PipeWire must be started before anything that might try to connect to any sound input or output, such as a volume monitoring applet. Additionally, consider disabling PA autospawn as described in man pulse-client.conf.
Older versions of PipeWire (<0.3.39) worked by calling pipewire directly, but this is no longer recommended/correct.
Starting PipeWire with various non-systemd setups
Setup Instructions Content to add Notes
Display manager (SDDM, LightDM, GDM, etc) Gentoo's PipeWire package now installs the needed autostart files to /etc/xdg/autostart/pipewire.desktop, so no action should be required! Alternatively, edit the ~/.xprofile file. N/A if using XDG option.
FILE ~/.xprofile
gentoo-pipewire-launcher &
The XDG approach should work for Wayland as well as X, but .xprofile may not be sourced when starting a Wayland session (unclear).
Sway Edit ~/.config/sway/config file.
FILE ~/.config/sway/config
exec gentoo-pipewire-launcher
Either elogind or seatd must be in use, otherwise start sway with:
user $dbus-launch --exit-with-session sway

Remember to set the XDG_RUNTIME_DIR, following what the ebuild prints out after installation.

Login without session management

Ensure there is a viable D-Bus session active:

FILE ~/.xinitrc
if which dbus-launch >/dev/null && test -z "$DBUS_SESSION_BUS_ADDRESS"; then
       eval `dbus-launch --sh-syntax --exit-with-session`

Check that XDG_RUNTIME_DIR is set. This is usually managed by either systemd-logind, its fork elogind for OpenRC and similar init systems, or seatd - an alternative free-standing implementation of logind. In addition to running one of the 3 logind variants, a PAM module must also be loaded to let the daemon interact with users logging in and out of the system.

On systems without any such logind implementation and the required PAM module, the user must create the require directory and set the environmental variable manually:

# Ensure XDG_Runtime_dir is set
export XDG_RUNTIME_DIR=$(mktemp -d /tmp/$(id -u)-runtime-dir.XXX)

The PipeWire executable must also be called:

FILE ~/.xinitrc

Setting Sample Rates

PipeWire uses a global sample rate in the processing pipeline. All signals are converted to this sample rate and then converted to the sample rate of the device.

To change the sample rate, uncomment and change this line:

FILE pipewire.conf
default.clock.rate = 48000

It is also possible to dynamically force a sample rate at runtime see here

Avoid Resampling

Since 0.3.33, it is possible to specify up to 16 alternative sample rates. Use the following config option to specify the sample rates:

FILE pipewire.conf
default.clock.allowed-rates = [48000 44100 96000]

Note that this not enabled by default because of kernel driver bugs.

According to the PipeWire developer, with the above configuration, no resampling is done when the graph is at a rate which both the client and the device can support.

Replacing PulseAudio

Unless using ALSA or JACK, the PulseAudio libraries (the new media-libs/libpulse package for ~arch users, see bug #536780) will still need to be installed, but PipeWire will use these to emulate a PulseAudio server (PulseAudio's daemon will not be running in such a configuration). Not many applications support PipeWire's native API so the most common setup is to use PipeWire's PulseAudio-server emulation and use PulseAudio's API in applications (e.g. USE=pulseaudio still set in make.conf).

If media-sound/pulseaudio is installed with the daemon USE flag enabled, then:

  1. Turn it off in /etc/pulse/client.conf set autospawn = no. Remove any ; at the beginning of the line.
  2. Disable daemon via configuration by editing /etc/pulse/daemon.conf and change 'daemonize' to daemonize = no. Remove any ; at the beginning of the line.

Alternatively, if media-sound/pulseaudio-daemon is installed, simply depclean (emerge --ask --depclean --verbose media-sound/pulseaudio-daemon) it.


These instructions must be executed as and for each user that needs PipeWire!

First disable PulseAudio's user service (safe to do even if user service was not in use) and then enable the PipeWire and PipeWire-Pulse sockets:

user $systemctl --user disable --now pulseaudio.socket pulseaudio.service
user $systemctl --user enable --now pipewire.socket pipewire-pulse.socket wireplumber.service
While PipeWire does not appear to utilize it beyond the cookie file, it may be a good idea to delete or rename the directory of existing PulseAudio user configuration that's usually found under the ~/.config/pulse/ directory.

Optionally, mask PulseAudio user service and socket, but it should be noted that this will not help much if PulseAudio configuration permits autostart (as is default):

user $systemctl --user mask pulseaudio.socket pulseaudio.service
A reboot is strongly advised for the change to take effect. Of course this can be avoided but due to PulseAudio usually being configured to autostart and often surviving logouts, this feat of stubbornness is left as an exercise to particularly skilled readers.


PipeWire versions 0.3.28 and greater now store the .conf files in /usr/share/pipewire/ directory. To create the PipeWire directory in /etc, type in the following command as root:

root #cp -r /usr/share/pipewire/ /etc/

To have PipeWire to act as a PulseAudio user daemon/server, no action is required on XDG-compliant desktops. If using a manual start solution, be sure to call gentoo-pipewire-launcher in scripts.

Verifying that it worked

Make sure prior that $ gentoo-pipewire-launcher & has been launched either manually or as script stated in the previous sections.

To check whether PipeWire is now acting as the PulseAudio user daemon/server, use this pactl command in a Bash compatible shell:

user $LANG=C pactl info | grep "Server Name"
Server Name: PulseAudio (on PipeWire 0.3.39)

Adding Multi user support

The default configuration only allows the current user (who started pipewire-pulse) to play audio.

For multi-user support, the TCP interface is needed:

user $cp -r /usr/share/pipewire/ /etc/
user $$EDITOR /etc/pipewire/pipewire-pulse.conf

Locate server.address = [ section and uncomment one of the available TCP options.

Replacing JACK

To have JACK clients routed through PipeWire, currently the only method supported by Gentoo is to run them via pw-jack which uses LD_PRELOAD to redirect clients from JACK's original libraries to PipeWire's alternatives:

user $pw-jack qsynth
Existing JACK users are likely to have realtime capability set up but new users are advised to raise the RLIMIT_MEMLOCK value from Gentoo's default of 64 kilobytes to 256 kilobytes on all PipeWire users that want to use its JACK emulation. For instructions on how to achieve that please see the subsection on that below (also listed in the table of contents for this page). Failure to do this will likely cause at least occasional buffer underuns (xruns) as a single page fault is likely to spend half to the entire length of a buffer just in kernel time to resolve.

It should be noted that either due to PipeWire incompleteness or Gentoo configuration shortcomings, not every client will work. Some may even ungracefully exit due to missing symbols. It will likely also require re-configuration of JACK clients, because they will attempt to use their old configuration files, if such exist.

Alternatively it should be possible to have PipeWire connect to a real jackd and act as a gateway for non-JACK applications but, unless there already is a working JACK setup, this is not recommended for the overall worse user experience with JACK.


CS:GO (and other games using the Valve's Source engine)

It appears that this issue has been resolved by a patch by Valve in early 2021. If the issue is no longer present without any fixes applied, then please delete this subsection entirely.

The default sound buffer length is 0.025. This can sometimes be too low causing cracking audio; for now the workaround is to increase the size of the application's audio buffer from within CS:GO[1][2]:

snd_mixahead is the length of the sound buffer in seconds, so 0.05 is 50ms (0.10, edited: 25ms is the default). This is essentially the audio delay, so reducing it gives better synchronization. Not all hardware can handle a buffer setting this low though, so if there are any crackling or pops at 0.05, increase this setting by 0.01 until the crackling/pops disappear.

Increasing RLIMIT_MEMLOCK for PulseAudio clients (systemd specific)

While the general issue of insufficient lockable memory limit is common among Gentoo and, indeed, most Desktop GNU/Linux distributions, this subsection chiefly addresses an additional resource limit on systemd units. Readers not using systemd's user services should follow instructions on JACK clients instead.

In case if messages such as this are observed:

user $systemctl --user status pipewire-pulse.service
.. pipewire-pulse[pid]: Failed to mlock memory [address] 32816: This is not a problem but for best performance, consider increasing RLIMIT_MEMLOCK

The amount of memory that pipewire-pulse process can lock can be adjusted via:

user $systemctl edit --user pipewire-pulse.service

and add in the blank space in the upper section of the editor window (not forgetting to save the file afterwards, of course):

### Anything between here and the comment below will become the new contents of the file


### Lines below this comment will be discarded
systemd is case sensitive and does not recognize the SI abbreviation for kilo, so be sure to use the capital letter K or will print a warning about illegal value and not apply the override!

If the system is shared between multiple users, this has to be done for each user (or the created override file has to be copied over with appropriate permissions).

Finally, to have the override applied, reload the configuration and then restart the service:

user $systemctl --user daemon-reload
user $systemctl --user restart pipewire-pulse.service

The current unit default is set to LimitMEMLOCK=131072 (same as 128K) by the Gentoo package which as of PipeWire 0.3.21 appears to allow for 1 PulseAudio client (subsequent clients will receive buffers backed by unlocked memory). Increasing the number to 256K as seen above should allow for 3 clients with buffers locked to memory at the same time.

While this is just a conjecture, it seems very likely that the LimitMEMLOCK which sets the per-unit hard limit (and implicitly also the LimitMEMLOCKSoft to the same value) must be within the bounds set on the user in question, which is 64 kilobytes for users without realtime capability. To actually have the default 128K or any other value above 64 kilobytes applied, set a new limit for non-system accounts:

FILE /etc/security/limits.d/50-custom.conf
# This raises the lockable memory upper limit of every process running under a non-system account (except for nobody) from default 64 to 256 kilobytes (in increments of page size); default (soft limit) remains at 64 kilobytes
1000:65533      hard    memlock 256

The new limits are only in effect on new logins, therefore the user must log out and back in. This is usually enough but if pipewire-pulse.service survived the logout, then it must be manually restarted as described previously in this subsection.

Increasing RLIMIT_MEMLOCK for JACK clients (and PulseAudio clients with OpenRC)

Unlike the case of PulseAudio clients, for which the user service does memory locking of buffers, JACK clients do it themselves. In the likely event that the clients report being unable to lock memory, in addition to the hard limit (max permitted value) described in previous sub-section on PulseAudio RLIMIT_MEMLOCK, the soft limit (the default value) must also be raised:

FILE /etc/security/limits.d/50-custom.conf
# This both raises the max and sets the default lockable memory limit of every process running under a non-system account (except for nobody) from default 64 to 256 kilobytes (in increments of page size)
1000:65533      -    memlock 256


PipeWire should already be enabling the bluez5 module when built with the pulseaudio USE flag. Please check if it's being set system-wide as PulseAudio API for clients is not going anywhere in a hurry.

By default, Bluetooth support is disabled to avoid clashes with PulseAudio's Bluetooth stack since currently the main use case is as an addition to not a replacement for PA. Uncomment PipeWire's bluez5 module for Bluetooth devices to be listed:

FILE /etc/pipewire/media-session.d/media-session.conf
modules = {
    default = [
        bluez5          # bluetooth support

Then run:

user $systemctl --user restart pipewire-pulse.service

See also

  • PulseAudio — a multi-platform, open source, sound server that provides a number of features on top of the low-level audio interface ALSA
  • ALSA — describes the setup of a sound card with ALSA (Advanced Linux Sound Architecture).

External resources