Create custom plugin folder

[Electronic1982]

What Avid should do is simple:
However the AAX plugin folder is organized, is how they appear in the plugin menu

Done.
This is what should be done.
You go into the plugin folder, move the plugins you want into the folders you want, name the folders, even rename the plugins themselves.
Then just open Pro Tools and your Plugin menu appears in the same order as your AAX plugins folder.

Great!

[JFreak]

Originally Posted by Electronic1982

This is what should be done.

Avid core plugins are always copied to root folder, so it would be a mess.

[Darryl Ramm]

Originally Posted by Electronic1982

What Avid should do is simple:
However the AAX plugin folder is organized, is how they appear in the plugin menu

Done.
This is what should be done.
You go into the plugin folder, move the plugins you want into the folders you want, name the folders, even rename the plugins themselves.
Then just open Pro Tools and your Plugin menu appears in the same order as your AAX plugins folder.

Great!

Nope!

You cannot control the "order" of plugins, or any files, within any directory/folder. Natural order of files in a directory is based on internal aspects of the file system.

In addition to being a problem with the core plugins that Janne mentioned, this may also break third party plugin installers and uninstaller that look for plugins in specific locations.

This would also force every user on a shared system to have this same order. That is not going to work in many studios/mix rooms.

Having users moving critical components of the software around to affect how a simple list or tree is ordered in a UI is just not the way to do this.

[Ben Jenssen]

A section in the preferences, then, with two panels; one with all plugins available, and one with how how you want them to show up in the menu w/optional folders/subfolders, and you can save sets to quickly switch between; "Basic, Reduced, Video, Restoration"... etc.

Should'nt be too difficult to produce.

[Sardi]

Originally Posted by Ben Jenssen

Should'nt be too difficult to produce.

I’ve said this exact same thing about what I would consider small changes to the application. I will always preface it with ‘I’m not a coder’ as I really don’t know how difficult these things are in reality, but in my mind, I just can’t picture it to me a massive challenge.

Part of me thinks it’s to do with the ancient codebase that is Pro Tools. Something trivial could potentially break a bunch of stuff. I also think shutting between different development teams probably isn’t ideal as everyone has to get up to speed, learn the intricacies of the application etc. etc.

Again, this is all speculation and ‘I’m not a coder’. I mean, maybe we’re all way off base as to how simple some of this stuff is.


Sent from my iPhone using Tapatalk

[Darryl Ramm]

Originally Posted by Sardi

I’ve said this exact same thing about what I would consider small changes to the application. I will always preface it with ‘I’m not a coder’ as I really don’t know how difficult these things are in reality, but in my mind, I just can’t picture it to me a massive challenge.

Part of me thinks it’s to do with the ancient codebase that is Pro Tools. Something trivial could potentially break a bunch of stuff. I also think shutting between different development teams probably isn’t ideal as everyone has to get up to speed, learn the intricacies of the application etc. etc.

Again, this is all speculation and ‘I’m not a coder’. I mean, maybe we’re all way off base as to how simple some of this stuff is.

Nope you are well behind the batting crease here.

It's relatively simple. Got to be thought out, work with multiple languages etc. But there is just nothing really hard here. The hard stuff in things like this is making it all be configurable obviously/super easily.

[Ben Jenssen]

Originally Posted by Darryl Ramm

Nope you are well behind the batting crease here.

It's relatively simple. Got to be thought out, work with multiple languages etc. But there is just nothing really hard here. The hard stuff in things like this is making it all be configurable obviously/super easily.

I'd guess there'd be no way around having to restart PT after changing menu settings, though. The sub-30 seconds PITA that is these days.

[Darryl Ramm]

Originally Posted by Ben Jenssen

I'd guess there'd be no way around having to restart PT after changing menu settings, though. The sub-30 seconds PITA that is these days.

Absolutely no need to expect any software to require a restart for this. The menu UI systems on Mac and Windows are all easily flexible enough to do this. Many apps are messing in real time with parts of the pulldown menus, if not reordering things they are doing many other things, changing icons/checkmarks shown, greying out options, hiding items, etc. This is all dynamic/real time adjustable, it just takes some coding.

[Electronic1982]

Bumping this along with some others,
@Avid/STG, it's time we really look into a Plugin Menu Editor for Pro Tools