PipeWire

From ArchWiki
Revision as of 22:03, 7 July 2019 by Fthiery (talk | contribs) (do not try to make chrome flag link clickable)
Jump to navigation Jump to search


PipeWire is a rather new multimedia framework by GNOME. The main developer is Wim Taymans.

Because PipeWire supports containers like Flatpak it doesn't rely on the user groups audio and video, but rather uses a complex PolKit-like security model asking Flatpak or Wayland for permission to record screen or audio.

Installation

Install the pipewire package from the official repositories or the pipewire-gitAUR package from the AUR.

The package installs systemd unit files for the service itself and automatic socket activation (which means it will autostart).

systemctl --user status pipewire.socket
systemctl --user status pipewire.service

Usage

Screen sharing

Because Gnome shell uses Wayland by default on Arch when started by GDM, screen sharing on videoconferencing services will not work, unless Pipewire and xdg-desktop-portal are installed; Firefox already supports PipeWire, but you need to enable WebRTC PipeWire support on Chromium 73 and over (open chrome://flags/#enable-webrtc-pipewire-capturer ).

Video

Although the software is not yet production ready, it is safe to play around with. Most application which rely on GStreamer to handle e.g. video streams should work out-of-the-box due to the PipeWire GStreamer plugin. Applications like e.g. cheese are therefore already able to share video input using it.

Audio (JACK)

Support for the Jack protocol on top of PipeWire is implemented and first applications relying on said interface are working in a test environment. Through that work one is able to achieve the low latency needed for pro-audio with PipeWire.

A detailed description of how to enable and use it can be found here.

ALSA/Legacy applications

Work on ALSA emulation is ongoing but first working code exists.

Bluetooth

PipeWire provides a bluetooth module which integrates directly into the Bluez Bluetooth framework. Pairing and management hence works the same since it is handled by higher level interfaces.

See also