![]() ![]() I used the names of actual VSTs I owned in the multi-effects folder so you can see what I classify as a multi-effects plug-in I've modeled a directory here with generic names and some randoms. It's a little extra time, but well worth it in one of those OH situations. Then I back-up my installs to an external hard drive every so often. If I ever had to reinstall a plug-in or migrate to a new machine, I know exactly where to find and to place each plugin without having to think much about what goes where. This includes installation codes, user manuals, etc. To keep things straight, I mirror the folder structure with my installs as well. I keep my VST folder at the root of my C: drive. When I need an EQ, I can just go to my EQ folder and select from all the different EQs that I have, same for reverb, etc. It's pretty nice doing it that way if I have an plugin that has a few version numbers or variation that I want to keep: plugin_V1, plugin_V6, plugin_mono, plugin_instrument, plugin_as-effects-version. In that folder I'll put my individual VSTs. Then I'll add a folder for each effect that's labeled by the manufacturer, underscore, effect name. Synths and utilities are basically by manufacturer and VST name. I'll break the effects into categories like dynamics, chorus, harmonics, filters, EQs, whatever makes sense to me. I then break down my sub-folders into three basic folder types: Effects, Synths, Utilities The 32 bit and 64 bit folders follow the same logic, so I'm just going to drill down on the 32-bit folders. ![]() ![]() I can quickly make sure I don't get into any trouble when working with legacy 32's, 64's, or 32's that have been wrapped for 64. I first divide my VSTs to 32-bit and 64 bit sub-folders. You may have another system, but this is what I like: When organizing my VSTs, I tried to follow Avid's ProTools logical breakdown. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |