Closed pgcd closed 1 year ago
Try running which wine
and wine --version
in a terminal. Also make sure that there's a drive pointing at /
set up in the drives tab in winecfg
.
I had to downgrade wine
to stable for unrelated reasons so the version now is different from the one I reported earlier but the problem is still there and everything else works or doesn't work exactly the same way (in my specific case). Here is the output
pgcd@pgcd-mint:~$ which wine
/usr/bin/wine
pgcd@pgcd-mint:~$ wine --version
wine-8.0.2
In winecfg
, drive Z:
is correctly pointing to /
.
Something I noticed that might be relevant: the plugins are installed in ~/audioapps/Music\ SW/VST2/
(mapped to F:\Music SW\VST2\
) but the log shows that wine tries to load the DLL from /media/pgcd/Ceres/Music SW/VST2/
, which is different copy for the old Win system.
I thought this might be due to something wrong in the wineprefix, so I tried creating a new one (audio
), then I ran
WINEPREFIX=~/.local/wineprefixes/audio yabridgectl sync
WINEPREFIX=~/.local/wineprefixes/audio yabridgectl status
env WINEPREFIX=~/.local/wineprefixes/audio YABRIDGE_DEBUG_FILE=/tmp/yabridge.log YABRIDGE_DEBUG_LEVEL=2+editor bitwig-studio
The first two commands returned the expected result, but Bitwig still couldn't find the plugins and the log still shows yabdrige
/wine
trying to load them from the Ceres
drive.
One further observation: the same happens when the Ceres
drive is unmounted, which adds to my confusion.
Another bit of information: I have updated Bitwig to the latest (5.0.11) version, which offers a little more feedback. To begin with, now I can see these plugins have scanning errors (Bitwig reports they're taking a long time to scan and that may indicate a hidden window somewhere); furthermore VacuumPro actually comes up with a specific iLok error: I have tried keeping iLok License Manager running while scanning but that seems to make no difference. So I guess what I'd need to know (or report) is:
Those plugin files (like /media/pgcd/Ceres/Music SW/VST2/Strum Session 2.dll
) are not inside of a Wine prefix, and Wine will thus default to using the default Wine prefix over at ~/.wine
. You should not install Windows plugins outside of a Wine prefix. Otherwise there's no way to know what Wine prefix they belong to.
Those plugin files (like
/media/pgcd/Ceres/Music SW/VST2/Strum Session 2.dll
) are not inside of a Wine prefix, and Wine will thus default to using the default Wine prefix over at~/.wine
. You should not install Windows plugins outside of a Wine prefix. Otherwise there's no way to know what Wine prefix they belong to.
I didn't "install" them - that's a data disk shared with the Windows installation, and I couldn't find any reference to it (using regedit
and grep
) in either the default wineprefix or the clean one that I've been using to try and understand this problem. What makes no sense to me is that this happens even when the volume is unmounted, so it shouldn't be (as far as I understand) a matter of something find
inding potentials VSTs either.
I'm happy to try any possible solution, of course.
You're better off installing the plugins the normal way in a regular Wine prefix. Just like on regular Windows, plugins that aren't entirely self contained and that have any form of DRM are not likely to work if you just copy them over to a different Windows install.
You're better off installing the plugins the normal way in a regular Wine prefix. Just like on regular Windows, plugins that aren't entirely self contained and that have any form of DRM are not likely to work if you just copy them over to a different Windows install.
You are totally right! I tried reinstalling properly (by running the whole process instead of simply copying the DLL) and now they all show up (I haven't tried the authorization with iLok but it's outside the scope), so I think this can be closed. Many thanks and forgive me for being such a newbie!
No problems, I'm here to help. You'll probably get a faster response if you ask on the Discord instead of here.
Thanks for giving yabridge a shot!
Problem description
Most of my plugins work correctly, but Air's VacuumPro and AAS Ultra Analog Session (and others) fail to show up in the host even though they show up in
yabridgectl list
.What did you expect to happen?
All processed plugins should show up in the host
What actually happened?
Some plugins (eg. VacuumPro) don't show up in the host
Operating system
Linux Mint 21.2
How did you install yabridge?
directly from the releases page
yabridge version
5.0.5
yabridgectl version
5.0.5
Wine version
wine-8.18 (Staging)
Plugin
VacuumPro
Plugin type
VST2
Plugin architecture
64-bit
Host
Bitwig Studio 4.4.10
Desktop environment or WM
No response
GPU model
No response
GPU drivers and kernel
No response
Debug log
Anything else?
No
yabridge.log
was created using the suggested command, but it looks like Bitwig's log includes the relevant info so I'm attaching that one instead.One thing that strikes me is that, although my system
wine
version is 8.0.18, it looks likeyabridge
uses 6.0.3 instead, and I can't find neither the binary nor any reference to it in my system.