Suggest troubleshooting from a terminal

This makes sure that the user sees all errors and warnings coming from
yabridge, including that `mmap()` error message from the previous
commit.
This commit is contained in:
Robbert van der Helm
2021-07-18 22:54:45 +02:00
parent fe61a28524
commit 5bce89d50b
+6
View File
@@ -521,6 +521,12 @@ If your problem is not listed here, then feel free to post on the [issue
tracker](https://github.com/robbert-vdh/yabridge/issues) or to ask about it in tracker](https://github.com/robbert-vdh/yabridge/issues) or to ask about it in
the yabridge [Discord](https://discord.gg/pyNeweqadf). the yabridge [Discord](https://discord.gg/pyNeweqadf).
- Both yabridgectl and yabridge try to diagnose many common issues for you. If
you're running into crashes or other issues, then try launching your DAW from
a terminal and reading the log output for any clues. Bitwig Studio writes
plugin output to `~/.BitwigStudio/log/engine.log`, so you may need to look
there instead.
- Using PipeWire's JACK implementation might cause certain plugins to crash. - Using PipeWire's JACK implementation might cause certain plugins to crash.
PipeWire currently uses rtkit instead of the realtime priorities you would PipeWire currently uses rtkit instead of the realtime priorities you would
normally set up using groups and `/etc/limits.d`, and it will impose a limit normally set up using groups and `/etc/limits.d`, and it will impose a limit