GitLab will be down for maintenance Monday June 03, from approx 10am UTC for roughly 48 hours. This is for a major gitlab upgrade which requires a DB migration. See the tracker issue for more informations.
@@ -111,6 +111,14 @@ The situation is a bit like GUI toolkits. There are many, each with different us
...
@@ -111,6 +111,14 @@ The situation is a bit like GUI toolkits. There are many, each with different us
We recommend that you continue to use PulseAudio, JACK and ALSA API's for now.
We recommend that you continue to use PulseAudio, JACK and ALSA API's for now.
### Is there a native GUI tool to configure PipeWire
No. We recommend you use pavucontrol and carla/qjackctl. They work fine and there is no urgent need to rewrite those applications.
The PipeWire lowlevel API is a loose collection of objects, properties and parameters that are combined into a coherent use case by the Audio Toolkit in use (JACK/PulseAudio). So any GUI without a concrete use case would not make much sense.
That said, there are cli tools to configure and manipulate every aspect of PipeWire. See the migration from [JACK](Migrate-JACK)/[PulseAudio](Migrate-PulseAudio) to see how to map existing use cases to lowlevel PipeWire operations.
### What Is Wrong With JACK + PulseAudio?
### What Is Wrong With JACK + PulseAudio?
PulseAudio has a JACK backend that sends all the mixed streams to JACK. It however has some problems:
PulseAudio has a JACK backend that sends all the mixed streams to JACK. It however has some problems: