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

Mention RLIMIT_RTTIME for better Ctrl+F-ability

Browse Source
This commit is contained in:
Robbert van der Helm
2021-09-27 20:16:59 +02:00
parent 46b4dc0341
commit 8712932cec
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+3 -3
View File
@@ -611,9 +611,9 @@ the yabridge [Discord](https://discord.gg/pyNeweqadf).
the out of the box configuration. PipeWire versions before 0.32.0 used rtkit the out of the box configuration. PipeWire versions before 0.32.0 used rtkit
instead of regular realtime scheduling, and both PipeWire and rtkit would instead of regular realtime scheduling, and both PipeWire and rtkit would
impose a low limit on the maximum amount of CPU time a realtime process may impose a low limit on the maximum amount of CPU time a realtime process may
use at a time. This would cause plugins that take a long time to initialize to use at a time (`RLIMIT_RTTIME`). This would cause plugins that take a long
crash. With PipeWire 0.32.0 you only need to change a single configuration time to initialize to crash. With PipeWire 0.32.0 you only need to change a
file to prevent this from happening. Simply copy 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, you