How to categorize Windows VSTs (in Carla?)

[JBandi]

Hello,

I have an unusual (?) question, and the search function got me nowhere.

I'm using Reaper (native) + Carla plugin (which works fine), but since there are like 300+ VST plugins in Carla, and no way to put them in a folder or categorize them - if there's such function in Carla I'm unaware of that -, it's getting more and more chaotic to use.

Is there any workaround to this?

Thanks
Andrew

[Linuxmusician01]

Hello,

I have an unusual (?) question, and the search function got me nowhere.

I'm using Reaper (native) + Carla plugin (which works fine), but since there are like 300+ VST plugins in Carla, and no way to put them in a folder or categorize them - if there's such function in Carla I'm unaware of that -, it's getting more and more chaotic to use.

Is there any workaround to this?

Thanks
Andrew

I don't know of such a function. But you can, for instance, filter out LADSPA plugins in the "Add new plugin" window. And you can look for a certain VST by typing in its name at the top.

[JBandi]

That's right, though it does not make things easier - I mean, I have ~300 windows VSTs (I don't have LADSPA or other type of plugins in Carla), so it's kind of hard to keep track of them. What does this "K1Ks" plugin do? Is it an analogue synth, a sampler? Can't remember... and can't google for help every time.

In the meantime I tried an other VST bridge, LinVST, which seemed OK because - theoretically - the bridged VSTs would show up in Reaper's FX list so I could put them in folders. But I ran into some compatibility issues (I think), one or more of the VSTs doesn't like LinVST: after re-scanning the FX folders, Reaper just wouldn't start (it froze in "Initializing" stage). Not having any error messages or logs to trace down the culprit, I had to give it up and drop LinVST.

I just installed Airwave, looks interesting, but as far as I understand, it only works one-by-one, manually, there's no batch processing? Well, it's worth a try, maybe I can just pick a few cool VSTs, who needs that many, right?


Andrew

[JBandi]

*** Hit post reply, but nothing happened - I guess I should've had a notification page about admin approval? - so if it's double post, please excuse me ***


That's right, though it does not make things easier - I mean, I have ~300 windows VSTs (I don't have LADSPA or other type of plugins in Carla), so it's kind of hard to keep track of them. What does this "K1Ks" plugin do? Is it an analogue synth, a sampler? Can't remember... and can't google for help every time.

In the meantime I tried an other VST bridge, LinVST, which seemed OK because - theoretically - the bridged VSTs would show up in Reaper's FX list so I could put them in folders. But I ran into some compatibility issues (I think), one or more of the VSTs doesn't like LinVST: after re-scanning the FX folders (no issues here), Reaper just wouldn't start (it froze in "Initializing" stage). Not having any error messages or logs to trace down the culprit, I had to give it up and drop LinVST.

I just installed Airwave, looks interesting, but as far as I understand, it only works one-by-one, manually, there's no batch processing? Well, it's worth a try, maybe I can just pick a few cool VSTs, who needs that many, right?


(...a few minutes later...)


So, no joy with Airwave. The bridged plugins cause Reaper to freeze first at plugin scan, then at restarting Reaper.

That's too bad.



Andrew

[glowrak guy]

Linvst and airwave wrap windows plugins that have the .dll extension,
and produce a version of each dll that will have a .so extension.
Airwave has it's own paths and config settings, while linvst
uses the existing vst plugin paths from .wine, .vst etc.
Your daw must be pointed to the folder of conversions that
airwave makes. Check it's config file and docs.

Those conversions with the .so extension are for the linux version of reaper.
Those with the .dll extension are for the windows reaper running in wine.

Carla can also use both variants, you might have to enable
the use of windows plugins in Carla preferences, it's off
by default now (I think).

If you have for example, 300 windows vsts with .dll extensions,
and none of them are saddled with pace, macromedia, ilok, or other
invasive/proprietary theft protection schemes, you
can expect around 250 to work in reaper in a wine-staging
that is supplemented with some key over-rides,
and somewhat fewer in the other available linux daws,
which can't (yet) scan and use plugins at the high level that
reaper does. I would expect about 230 of 300 to work
in linux reaper, when wrapped by linvst, and often,
some really desirable commercial and freeware plugins will work well.
(numbers are based on personal experience, having about 120
unique windows plugins, and around of 90 those work in linux reaper
when wrapped by linvst. A dozen or so are commercial cross-platform
products from U-he, discoDSP, and Modartt.
Good times for making music in linux!

There may be some older linux native vsts that are poorly coded
and cause some scanning havoc, so I would move all the non-windows
vsts out of your plugin paths temporarily, until you settle
in on the main plugins you use and convert with linvst.
Add the others back one at a time, restarting your daw/scan
each time.
Cheers

[glowrak guy]

Also, I think when using linvst to add more converted plugins,
you must delete all the previously converted plugins first,
it's just the way things work now. In all your vst paths,
delete all the files with .so extensions
and then rescan all those same vst paths.
Cheers