Closed udaemon closed 2 years ago
This is on my list of breaking changes to consider for yabridge 4.x, but either way is a compromise, so I don't think I'll end up doing this. I've explained why a couple of times on the Discord, but the gist is that doing this would actually make everything more opaque and less flexible. Storing these .so files right next to the Windows plugin files makes it very clear what's going on at a glance without even loading the plugin, and it also avoids a layer of magic. You can just add your VstPlugins
directory to your DAW as if you were using Windows, and it will just work. If you for some reason really don't want to do that, then you can always symlink that VstPlugins
directory to somewhere in ~/.vst
and add that directory instead. There are instructions for this in the readme.
Some of the issues with automatically dropping a symlink to the generated .so file in a directory like ~/.vst/yabridge
are:
~/.vst3/yabridge
because the VST3 specification says that is the only valid place they can go in your home directory, but the VST2 specification does not have anything like that. So for VST3 plugins, we just throw a warning when this situation comes up and then pretend nothing happened, but it's not an ideal situation.I've probably forgotten a few important ones. You can search through the Discord for more discussion on this!
hi Robbert, thanks very much for your detailed response. very understand your points and now I think it's better to add some more directory entries to the daw than paying convenience with magical layers! kind regards!
But yeah, like I mentioned you can symlink entire directories to ~/.vst
. So that way you will still yabridgectl add
the VstPlugins directories inside of your Wine prefix, but your DAW will also automatically find them when it searching through ~/.vst
. That sort of gives you the best of both worlds if you want.
true, that's a good hint. thanks again!
As part of a whole bunch of other breaking changes in yabridge 4.0, this has now also become the new default behavior. Yabridge 4.0's yabridgectl will set up VST2 plugins in ~/.vst/yabridge
by default, just like it sets up VST3 plugin bundles in ~/.vst3/yabridge
. It's still possible to revert back to the old behavior (for the reasons I outlined earlier in this ticket) by running yabridgectl set --vst2-location=inline
.
Yabridge 4.0 now sets up VST2 plugins in ~/.vst/yabridge
by default. You can revert to the old behavior through an option under yabridgectl set
.
Thanks, Robbert! kind regards
salut Robbert and people involved! thanks for this well working vst-bridge! I have finally found some time to test yabridge and it works very nice. the only thing that I found missing when setting yabridge up is the option to define a folder where the .so-files yabridge produces go (be they moved there or copied or symlinked). I know this already from airwave and linvst, so that's probably why I missed it. I'm not telling you have to adapt to these "standards" and maybe you've chosen to handle it differently on purpose. But from my perspective it is a very comfortable option: I would set /$HOME/.vst as link location so that my daw would automatically would find the new vsts.
do you think this is a good feature for yabridge? thanks and take care! christoph