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

Add instructions for PipeWire 0.32.0

Browse Source
This commit is contained in:
Robbert van der Helm
2021-07-23 19:27:26 +02:00
parent 4b256d456b
commit f5ada4469b
1 changed files with 11 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+11 -8
View File
@@ -527,14 +527,17 @@ the yabridge [Discord](https://discord.gg/pyNeweqadf).
plugin output to `~/.BitwigStudio/log/engine.log`, so you may need to look plugin output to `~/.BitwigStudio/log/engine.log`, so you may need to look
there instead. there instead.
- Using PipeWire's JACK implementation might cause certain plugins to crash. - Using PipeWire's JACK implementation might cause certain plugins to crash with
PipeWire currently uses rtkit instead of the realtime priorities you would the out of the box configuration. PipeWire versions before 0.32.0 used rtkit
normally set up using groups and `/etc/limits.d`, and it will impose a limit instead of regular realtime scheduling, and both PipeWire and rtkit would
on the maximum amount of CPU time a realtime process may use at a time. This impose a low limit on the maximum amount of CPU time a realtime process may
will cause plugins that take a long time to initialize, for instance because use at a time. This would cause plugins that take a long time to initialize to
they're loading a lot of resources, to crash. For the time being the best crash. With PipeWire 0.32.0 you only need to change a single configuration
solution for this problem would be to just use JACK2 until PipeWire doesn't file to prevent this from happening. Simply copy
require rtkit anymore. `/usr/share/pipewire/jack.conf` to `~/.config/pipewire/jack.conf`, uncomment
the `rt.time.soft` and `rt.time.hard` arguments for the
`libpipewire-module-rt` module, and then set both to `-1`. Alternatively, you
can also use regular JACK2 or straight ALSA instead of PipeWire.
- 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