Il giorno ven, 20/11/2020 alle 11.26 -0500, Ben Cotton ha scritto:
== Summary ==
This change proposal is to route all audio from PulseAudio and JACK
the PipeWire Audio
daemon by default.
== Owner ==
* Name: [[User:Wtaymans| Wim Taymans]]
* Email: wim.taymans(a)gmail.com
== Detailed Description ==
Currently, all desktop audio is handled by the PulseAudio daemon.
Applications make use of the
PulseAudio client library to communicate with the PulseAudio daemon
that mixes and manages the audio streams from the clients.
The desktop shell (gnome-shell) and the control panel
(gnome-control-panel) both use the
Pulseaudio client libraries to manage the volume and configuration of
the PulseAudio daemon.
This proposal is to replace the PulseAudio daemon with a functionally
based on PipeWire. This means that all existing clients using the
PulseAudio client library
will continue to work as before, as well as applications shipped as
All PRO audio is handled with the JACK client library, which talks to
the JACK server. This
proposal will install a JACK client library replacement that talks
directly to PipeWire. All
existing PRO audio jack applications will then work on top of
For pro audio we should test very deeply with clients like ardour,
audacity, rosegarden, hydrogen and so on.
Pro audio is very sensible to latency and real time scheduling, and
jack is very mature in handling these requirements.
IMHO pipewire is too young to accomplish these tasks.
I think this should be an opt-in or out and that jack should remain as
an alternative to pipewire's jack module.