Loremaster
Registered User
Joined: 23 Jan 2009
Location: Germany/Mannheim
|
 Posted: Fri Apr 02 2010 12:40
VST chaos problem |
 |
VST scan works well with a complex directory tree but often fails to get the right plugin name. On a huge library of 200 and more plugins, everyone goes mad. There are for example 20 VSTi named "Container" or "Container - SynthEdit" and 15 VSTfx named "Effect", many synths and effects are categorized "Other", some plugins are listed surprisingly twice and some are named with suffix ".dll". How can it be? Wherefrom the name and category information is taken? In addition some plugins are using the same name for different products confusingly (e.g. dirtbox).
Why don't simply get the filename without suffix ".dll" or include a customizable database name field and categorize exactly like the directory tree including subfolders as subcategories?
Advantage: Everyone could organize plugins at one's own option. If someone favors sorting by device type (e.g. wavetable synth, additive synth, hybrid synth etc.), he can do this. If someone favors sorting by main task area (e.g. pad synth, bass synth, atmo&fx synth etc.), he can do this. If someone favors sorting by developer (e.g. Angular Momentum, Big Tick, Native Instruments, Spectrasonics etc.), he can do this. Additionally each category and subcategory should be sorted alphabetically.
Some hosts like Cubase are using this highly recommended method.
I know how to create a new category inside MT, but a subcategory (marked by slash or backslash) don't create a seperate menu instance like the following screen out of Cubase. Also you can see, there are no "Container".
After reorganization of my directory tree, the chaos inside MT is unchanged. A deep-scan by dll-names wouldn't be perfect (many names are abbreviated or ugly looking underscore-constructions), but most dll's can be renamed without loss of functionality. The best deep-scan solution would be getting the subdirectory-name, the plugin directly is stored in (in this case, dll-renaming wouldn't be necessary).
@Yannick: I think, an updated MT2.7 of this little feature change would be great. Also it's a suggestion to MT3.
ADDITIONAL OPTION: Rebuilding the hot presets of a synth on a more popular synth would help to compensate huge VST-libraries, but it's a hard and time consuming job. |
|
|
Home/News
About
Download
Plugins
Tutorials
Register
Registered Users
Community
Music
Compo
Links
Forum
VST chaos problem
Log in
Profile
FAQ
Back to top
