mirrors/pipewire
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/pipewire/pipewire.git synced 2025-10-29 05:40:27 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions

Update README.md

Browse source
This commit is contained in:
Wim Taymans 2020-05-02 08:16:03 +00:00
parent f043ed86d9
commit 7a7527bc90
1 changed files with 6 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

12
README.md
View file

@ -38,10 +38,10 @@ or with the provided scripts shown below.
PipeWire can use environment variables to control the behaviour of
applications:
PIPEWIRE_DEBUG=<level> to increase the debug level
PIPEWIRE_LOG=<filename> to redirect log to filename
PIPEWIRE_LATENCY=<num/denom> to configure latency
PIPEWIRE_NODE=<id> to request link to specified node
* PIPEWIRE_DEBUG=<level> to increase the debug level
* PIPEWIRE_LOG=<filename> to redirect log to filename
* PIPEWIRE_LATENCY=<num/denom> to configure latency
* PIPEWIRE_NODE=<id> to request link to specified node
### Using tools
@ -63,7 +63,7 @@ In dual mode, JACK apps will by default use the JACK server. To direct a JACK
app to PipeWire, you can use the pw-jack script like this:
```
$ pw-jack &lt;appname&gt;
$ pw-jack <appname>
```
If you replaced JACK with PipeWire completely, pw-jack does not have any
@ -79,7 +79,7 @@ at this point.
Use the pw-pulse script to launch a PulseAudio application on PipeWire, like:
```
$ pw-pulse &lt;appname&gt;
$ pw-pulse <appname>
```
### Running ALSA applications