Folders inside the plugin folder

[BScout]

Originally Posted by Eric Lambert

And that never creates an issue when an installer needs to validate the presence of a former version of that plugin?

Nope. Not a single time. Plugins that need to verify pre-existing installations don't base it on the plugin locations. Generally it is either Application Support files or Receipts (prior installations)

[K Roche]

OR one could simply scale way down to say maybe 10 plugins.

OK putting on body armor and hiding under rock
Just feeling a bit mischievous today

[Ben Jenssen]

Originally Posted by K Roche

OR one could simply scale way down to say maybe 10 plugins.

I'd say being able to create sets of plugins in folders could actually help me minimize the numbers of plugins in my menu. Maybe even different sets for different tasks. Different sets for different people, like BScout said, could be useful for some.

[AlexLakis]

Another thing to mention is the stock Avid plugins will always be deposited in the root plugin folder on every startup, so don't try making a sub-folder for Avid plugins as you will just end up with duplicates and that is not good.

[BScout]

Originally Posted by AlexLakis

Another thing to mention is the stock Avid plugins will always be deposited in the root plugin folder on every startup, so don't try making a sub-folder for Avid plugins as you will just end up with duplicates and that is not good.

It doesn't hurt anything but it is clutter. Reason why we leave the Avid plugins as the only plugins at the root level.

But, Pro Tools always picks the latest plugin if there are duplicates (based on metadata when scanning plugins of name and version number; sometimes plugin makers have changed the name with a version change and you end up with duplicate listed: looking at Lexicon who did this between 1.3.8 and 1.3.10 and screwed up opening older sessions.)