Thanks for the reply on the subject and the input.
I totally agree that a 'load license file' option can be useful whatever the OS is. Moreover, file dialogs are the nuts and bolts of software applications, and MUX is already using such.
I use wine-staging and linvst. After reading countless problems and all sorts of workaround by people, I found that linvst is the simplest way IMHO. It's as close as plug and play as it can be. I run Bitwig 2.4.3 Linux, installed using the Bitwig Debian package.
Bitwig Linux does not recognize dll files: true. And this is where the simplicity and 'magic' of linvst comes into play. For each dll a same linvst shared object (.so, the equivalent of .dll) is copied under the plugin's name. Bitwig naturally sees the .so and loads it. In turn the .so will load the VST .dll with the help of wine. For instance:
Code: Select all
-rw-rw-r-- 1 mevla mevla 10912768 Nov 26 05:44 MUX.dll -rwxr-xr-x 1 mevla mevla 93056 May 27 2019 MUX.so*
Aside from Linux plugins (including all u-he), I run all Melda production plugins (approx. 104 or so), most Rob Papen synths, all Voxengo audio processing, most Tone2 synths, all Sugar Bytes, Synthmaster One and 2, most IK Multimedia, several Image Line synths, many Sonic Charge, all Psychic Modulation and Fathom. Since I do not have any Windows ties, I do not have any previous Windows VST that I must run. It means that when I try a VST demo and it does not run well, I simply drop it, no questions asked. When it runs fine I then consider how useful an addition it can be to create music.
I haven't really tried to run MuLab. I'm OK with Bitwig and trying to know and use it very well, and Harrison Mixbus32C for mixing exported tracks.