... | @@ -167,7 +167,14 @@ We recommend that you continue to use PulseAudio, JACK and ALSA API's for now. |
... | @@ -167,7 +167,14 @@ We recommend that you continue to use PulseAudio, JACK and ALSA API's for now. |
|
|
|
|
|
### Is there a native GUI tool to configure PipeWire
|
|
### 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.
|
|
It depends what kind of configuration you wan to do. Most features are configured in the config files, See [Wiki](home).
|
|
|
|
|
|
|
|
To configure Card Profiles, default devices, ports and other settings, we recommend to use pavucontrol. Your
|
|
|
|
desktop might also have settings pannels to configure aspects of PipeWire (GNOME-Contrl-Center).
|
|
|
|
|
|
|
|
To make connections in the graph, there are [qpwgraph](https://gitlab.freedesktop.org/rncbc/qpwgraph) and
|
|
|
|
[Helvum](https://gitlab.freedesktop.org/pipewire/helvum). You can also use the JACK applications such
|
|
|
|
as Carla, qjackctl or Catia.
|
|
|
|
|
|
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.
|
|
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.
|
|
|
|
|
... | @@ -310,14 +317,4 @@ Please see [issue 713](https://gitlab.freedesktop.org/pipewire/pipewire/-/issues |
... | @@ -310,14 +317,4 @@ Please see [issue 713](https://gitlab.freedesktop.org/pipewire/pipewire/-/issues |
|
|
|
|
|
### Does PipeWire support network streaming
|
|
### Does PipeWire support network streaming
|
|
|
|
|
|
PipeWire is optimized for local use cases and does *not* transparently work over a network. It is however possible to implement network streaming with various modules or applications:
|
|
PipeWire is optimized for local use cases and does *not* transparently work over a network. It is however possible to implement network streaming with various [modules or applications](Network). |
|
|
|
|
|
* PulseAudio streaming, to use the pulseaudio protocol to send data over the network.
|
|
|
|
* ROC streaming, for general network streaming.
|
|
|
|
* RAOP streaming, to send audio data to an Apple Airplay device.
|
|
|
|
* simple transport, to send/receive data from a mobile phone
|
|
|
|
* Bluetooth streaming
|
|
|
|
|
|
|
|
It is also possible to use zita-n2j to implement low-latency data streaming between JACK and PipeWire servers.
|
|
|
|
|
|
|
|
A native netjack implementation is expected to be implemented eventually as well. |
|
|