@@ -78,7 +78,7 @@ You get the most glitch-free experience when using [PipeWire](https://pipewire.o
...
@@ -78,7 +78,7 @@ You get the most glitch-free experience when using [PipeWire](https://pipewire.o
Server Name: PulseAudio (on PipeWire 0.3.80)
Server Name: PulseAudio (on PipeWire 0.3.80)
```
```
To check if PipeWire is up and running you can use
To check if PipeWire is up and running you can use
```bash
```bash
systemctl --user status pipewire
systemctl --user status pipewire
...
@@ -90,11 +90,11 @@ At the moment we recommend running engine-core with [JACK](https://jackaudio.org
...
@@ -90,11 +90,11 @@ At the moment we recommend running engine-core with [JACK](https://jackaudio.org
### Configure JACK/ALSA
### Configure JACK/ALSA
Have a look at `config/sample.engine-core.ini`. Here you can set things like the log level and much more. For JACK no adaptations are necessary.
Have a look at `config/sample.engine-core.ini`. Here you can set things like the log level and much more. For JACK no adaptations are necessary.
For ALSA you might want to set a different audio device or even configure your own. An example can be found in `config/sample.asoundrc`. Very important is the `alsa_buffer`, if you experience jitter, cracklings or other audio artifacts you should increase this number. If the buffer is to large you will experience bad latency, to reduce the latency you have to reduce the buffer size.
For ALSA you might want to set a different audio device or even configure your own. An example can be found in `config/sample.asoundrc`. Very important is the `alsa_buffer`, if you experience jitter, cracklings or other audio artifacts you should increase this number. If the buffer is to large you will experience bad latency, to reduce the latency you have to reduce the buffer size.
When you are finished copy the configuration `config/sample.engine-core.ini` to `config/engine-core.ini`.
When you are finished copy the configuration `config/sample.engine-core.ini` to `config/engine-core.ini`.