I get quite a few logs with a ton of cruft prepended to them, maybe this will help.
1.9 KiB
name, about, title, labels, assignees
| name | about | title | labels | assignees |
|---|---|---|---|---|
| Setup help | How do I install yabridge |
Thanks for giving yabridge a shot! If you're having issues with plugins not working at all or scans timing out then make sure to check out the troubleshooting common issues section of the readme. yabridgectl sync will also try to diagnose most if these issues for you during setup.
Also try our Discord for some quick help or questions.
Problem description A short description of the current situation.
System information
- Plugin: [e.g. Vital, optional if this is a general issue]
- Plugin type: [VST2/VST3, optional if this is a general issue]
- Host: [e.g. Bitwig Studio, REAPER or Ardour]
- Operating system: [e.g. Manjaro, or Ubuntu 20.04]
- Wine version: [e.g. Wine Staging 5.13]
- Audio: [e.g. JACK2, ALSA, PipeWire]
- Installation method: [symlinks/copies], [manual/yabridgectl]
- yabridge version: [e.g. 1.3.0 or commit
a29f43a] - yabridgectl version: [e.g. 1.3.0 or commit
a29f43a, if using]
Debug log Please also include a debug log if possible. If you are having issues with yabridgectl, then you can omit this section.
-
First make sure that there are no leftover Wine processes left running in the background using
wineserver -k. -
Launch your host from a terminal using:
rm -f /tmp/yabridge.log; env YABRIDGE_DEBUG_FILE=/tmp/yabridge.log YABRIDGE_DEBUG_LEVEL=2 <host>Where
<host>is the name of your host, likebitwig-studio,reaper, orardour6. -
Try to scan or load the plugin that's causing issues.
-
/tmp/yabridge.logshould now contain a debug log. You can either attach this log directly to the issue by dragging the file onto this text box, or you could upload the contents to a website like GitHub's Gists or Hastebin.