From 7a7527bc906c8dd069b6f92516f7df21a59d6e9e Mon Sep 17 00:00:00 2001 From: Wim Taymans Date: Sat, 2 May 2020 08:16:03 +0000 Subject: [PATCH] Update README.md --- README.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index 9b464c328..f4c5e10b5 100644 --- a/README.md +++ b/README.md @@ -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= to increase the debug level +* PIPEWIRE_LOG= to redirect log to filename +* PIPEWIRE_LATENCY= to configure latency +* PIPEWIRE_NODE= 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 <appname> +$ pw-jack ``` 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 <appname> +$ pw-pulse ``` ### Running ALSA applications