-
-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Yabridge can't find Wine in Bitwig, PopOS #392
Comments
UPDATE: It still shows |
You need to install wine because it seems wine is missing from your system. You can install wine from the official gitlab @ https://gitlab.winehq.org/wine/wine/-/wikis/Download |
Also install wine Stable. Wine staging hasnt worked well for me so far. im using cutefishos and wine stable 9.0 at the moment of this message and im able to run waves plugins surprising well so good luck again |
I did actually install wine-staging using the winehq PPA, per the the instructions in the yabridge README. |
Thanks for giving yabridge a shot!
Problem description
This is a newly installed copy of yabridge and wine. As a test, I installed scaler2 with wine and ran
yabridgectl sync
.It finds the plugins and creates .so files in
/.vst/yabridge
.The logs report:
This leads me to believe that yabridge cannot find the wine executable (in
/opt/wine-staging/bin
, which is in my $PATH at bitwig launch). I also tried making a symlink in/usr/bin
, but it still see Wine version: ''Since I'm not familiar with how yabridge locates the wine executable, I'm not sure what else to try.
Operating system
PopOS 22.04 / Jammy
How did you install yabridge?
Directly from the releases page. Moved it to $HOME/.loal/share/yabridge
yabridge version
5.1.1
yabridgectl version
5.1.1
Wine version
wine-10.0-rc3 (Staging)
Plugin
Scaler 2
Plugin type
VST2
Plugin architecture
32-bit
Host
Bitwig 5.3 Beta 3
Desktop environment or WM
Gnome
GPU model
NVIDIA GeForce GTX 1080
GPU drivers and kernel
NVIDIA 560.35.03
Debug log
The above steps did not create a /tmp/yabrideg log file, but from bitwig's logs:
Anything else?
No response
The text was updated successfully, but these errors were encountered: