vanja/yabridge
1
0
Fork 0
mirror of https://github.com/robbert-vdh/yabridge.git synced 2026-05-09 20:29:10 +02:00
Code Issues Packages Projects Releases Wiki Activity

Link to an optimized preconfigured PipeWire config

Browse Source
This commit is contained in:
Robbert van der Helm
2022-01-02 15:55:27 +01:00
parent 0b9a16cf40
commit 14870c8dd9
1 changed files with 6 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+6 -8
View File
@@ -590,16 +590,14 @@ the yabridge [Discord](https://discord.gg/pyNeweqadf).
up yourself](https://jackaudio.org/faq/linux_rt_config.html). up yourself](https://jackaudio.org/faq/linux_rt_config.html).
- Using PipeWire's JACK implementation might cause certain plugins to crash with - Using PipeWire's JACK implementation might cause certain plugins to crash with
the out of the box configuration. PipeWire versions before 0.32.0 used rtkit the out of the box configuration, and yabridge will warn you about this in
instead of regular realtime scheduling, and both PipeWire and rtkit would advance. With PipeWire 0.32.0 you only need to change a single configuration
impose a low limit on the maximum amount of CPU time a realtime process may file to prevent this from happening. Simply copy
use at a time (`RLIMIT_RTTIME`). This would cause plugins that take a long
time to initialize to crash. With PipeWire 0.32.0 you only need to change a
single configuration file to prevent this from happening. Simply copy
`/usr/share/pipewire/jack.conf` to `~/.config/pipewire/jack.conf`, uncomment `/usr/share/pipewire/jack.conf` to `~/.config/pipewire/jack.conf`, uncomment
the `rt.time.soft` and `rt.time.hard` arguments for the the `rt.time.soft` and `rt.time.hard` arguments for the
`libpipewire-module-rt` module, and then set both to `-1`. Alternatively, you `libpipewire-module-rt` module, and then set both to `-1`. Alternatively, give
can also use regular JACK2 or straight ALSA instead of PipeWire. [this](https://github.com/robbert-vdh/dotfiles#pipewire) optimized PipeWire
configuration a try.
- If you have the `WINEPREFIX` environment variable set and you _don't_ want all - If you have the `WINEPREFIX` environment variable set and you _don't_ want all
of your plugins to use that specific Wine prefix, then you should unset it to of your plugins to use that specific Wine prefix, then you should unset it to