submap folders for VSTi in Plug in VST root map

[janamdo]

Is it possible to see/make a maptree in MULAB voor VSTi instruments
e.g
Bas
Gitaar
Drums
Composing
Synths - spacesynths (subsubmap)
etc

[pljones]

In the VST Plugin Manager, there's a column "Group". When you click on an existing entry, it asks you what group you want to assign it to and offers also "New group". You can organise your plugins this way so that when you go to select them, they are in subfolders by Group.

Is that what you're after?

[janamdo]

Yes,thanks ..i am overlooking this

Now i can organise the plug inns:
X-Wheel of Fortune 4 as composing tool

Jan

[tomica]

its true that we can group vsts in mulab but...

i would like mulab to have the option of recognizing the folder structure itself
because my vsts are all well organized by groups (each group has its own folder) in my vst folder already
and still mulab doesnt recognize that
so i have to organize them again everytime i install mulab

btw, is it possible to somehow backup the way i grouped vsts in mulab
and then simply import it when i install mulab again?

[pljones]

so i have to organize them again everytime i install mulab

btw, is it possible to somehow backup the way i grouped vsts in mulab
and then simply import it when i install mulab again?

Just copy the VstPlugins.xml file from your old Settings folder to your new one.

[tomica]

yesssssss
i figured something like that must be possible already :]
thank you!

[MuTools]

i would like mulab to have the option of recognizing the folder structure itself
because my vsts are all well organized by groups (each group has its own folder) in my vst folder already
and still mulab doesnt recognize that
so i have to organize them again everytime i install mulab

There will come a Plugin Manager function something like "Set Group From Parent Folder".

[pljones]

I wonder how clever it's going to need to be. I generally preserve the original folder structure as well as placing the plugin under the appropriate folder, so we get:
VstPlugins\Effects\Compressors\Foo Effects Ltd\CompressorMax\CompressorMax.dll

I'd actually want the Effects\Compressors part used, rather than anything else... I'd suggest a "Levels beneath main folder" count. Zero would work as the current system does (i.e. group populated with nothing), then each increment would take one more folder downwards -- I'd use "2" to get "Effects\Compressors" as above.

But then, I'd quite like to strip "Effects"... so another count of "Leading folders" to strip would be nice...

[MuTools]

Indeed, it's not a straightforward thing, as already discussed previously in this forum. (please do a search)

The problem is that many vst plugins are in a subfolder of their own which makes that simply using the folder structure is quite useless, imho.

That's why i think MU.LAB's 'Group' system is better.

But i understand there maybe a need for such "Set Group From Parent Folder" (or "Get Group From Parent Folder")

Maybe the "Get Group From Parent Folder" should indeed (cfr pljones remarks) have a parameter that indicates which parent folder to use.

E.g. "Parent Level" = 1..N

where 1 = the immediate parent, 2 = the parent parent etc...

This function would operate on the selected plugins, so you can select a bunch of related plugins and apply this function.

In the future it will also be possible to simply select a bunch of plugins and set the Group for all these plugs in 1 go. This will certainly help too in organizing your plugs.

[mickeh]

There will come a Plugin Manager function something like "Set Group From Parent Folder".

That sounds great!

I would love that too!

[robenestobenz]

The problem is that many vst plugins are in a subfolder of their own which makes that simply using the folder structure is quite useless, imho.

I really think this varies from person to person. For example, I've got about 300 plugins at a guess, of which only about 4 are in a folder of their own.

For payware plugins this is usually the case, but for the majority of freeware or donationware which don't use installers I'd imagine the opposite is true.

[pljones]

Even most payware apps (I've used) still think living in "C:\Program Files\VstPlugins" (itself) is okay and will live where you ask them to. Very few I've found insist on their own folder. (Even then, it's usually the last level they insist on, which fits my naming scheme anyway! )

[MuTools]

I think many plugs come with additional files, e.g. graphic files, doc files, patch files etc...

That's why it's understandable that they create a subfolder (maybe in C:\Program Files\VstPlugins) to group all this files together.

Anyway, thing is that there is a wide range of possibilities where the plug is located.

And so it's good that MU.LAB's Plugin Manager abstracts from this, imho.

Adding a "Set Group From Parent Folder" function should cover the situation where you have a lot of plugs grouped in a single subfolder.

[mickeh]

Something that would be very nice as an addition to the above mentioned would be some kind of matrix were i as a user could add my faourite preferences to each intrument, like:


lead bass pad fx
------------------------------------------------
synth A X X
synth B X X
synth C X X

etc.
(OK, so the forum script doesn't allow me to put the "X":s where I want to, but hopefully you get the idea).

and use this as a search criteria when adding a new VST(i) in my song.
After filling this out I could search for lead synths and Mulab shows me them after my preferences.