In a perfect world we wouldn't need VST2 BUT some developers dont release their VSTs in vst 3 format and some cracked VSTs have problems with presets in VST3 versions. On top of that, some stubborn developers like Ableton have a DAW in which you can't have VST3.

 

I install to C:\64vst & C:\32Vst, then under developer name.
( I delete most 32-bit DLLs because I don't use them, but I point installers there and move or delete them...except a couple of ones for which I only have 32-bit VSTs)

I also have "hold" folders for every VST folder location ("C:\64vst-Hold","C:\32vst-hold, "C:\Program Files\VST3-Hold" , etc. puts them just below their related VST folder).
I put VSTs that i might delete, or do not want scans to find. (Handy to move those damned slow-to-scan Arturia VSTs there if I am doing a recan that inclused already installed plugins. I will move them back and rescan when i am not using the computer :P )
I put a misbehaving VST3 in the "hold folder" to keep it out of trouble (not get scanned and used by FL Studio), but last update I did not install the VST3, so that folder is now empty. (Again, i will move the Arturia ones there when I want a fast scan that includes recanning already installed plugins).
Also useful: I use the "64vst-Hold" folder for the 3 copies of Alchemy plugin. The one I use cannot edit the patches, but the one that CAN edit can't be used normally (I can't recall why). So i copy the one that can edit over and then when i am done copy the normal one again.

I also have one called "64vst-4 RX7" that i copy some to and let RX7 only scan that folder.
I also have one called "64vst-Waves" where I used shell2vst64.exe to unpack all the Waves plugins. Some I copy to the "64vst-4 RX7" folder, but keep the rest there to be handy. They only take up 2.38 Meg.

Keeping the VST folders near the top of the folder list in the root of the drive help when browsing to install and clean up.

 

What crazy f***ing lives we lead. I just realized that I've been doing this for 21 years. :-|

 

I don't know about Windows, but did you guys ever hear of something called a symbolic link?

On my Mac I have a folder under Documents called VST and below that a folder structure with ./Distortion, ./EQ, /Gate etc. I don't care where VSTs are installed or where I actually install them (some are quite huge, so I place them on another HDD). I just make a symbolic link in my documents VST folder pointing at them.

I just point my DAW to this folder to search for VSTs and I have the folder structure in the (sadly not all) DAW ready to go. Especially great for Ableton.

Actually I even coded myself a tiny python script which finds all VSTs by itself and places a symbolic link into my Document/VST root folder for every VST which isn't already in one of the subfolders, so I just have to move the link into the right subfolder and don't need to search the VST by myself first.

 

Way To much!

 

I got smbo links from all the large program data files bak to my x64 folder.. takes just little longer to load mostly unnoticeable (keep most used plugs without symbo's if on ssd's) its all bout the speed keep yhm used one one fast drives

 

i prefer C:\VST and then structuring

 

I prefer VST2.

CHANNEL - PREAMP - TUBE
COMPRESSOR
DELAY
_BANK B
DISTORTION
_BANK B
EQUALIZER
EXCITER - MAX - ENH
FILTER
GATE - DEESSER
GUITAR-BASS AMPLIFIER
INS._DRUM SYNTH-MACHINE
INS._REAL
_BASS
_DRUMS
_GUITAR
_PIANO
INS._SAMPLER
INS._SYNTH
_BANK B
_OTHER-RARE-SPECIAL
_RETRO-MODULAR-EMU
LIMITER - MASTERING
MODULATION
_CHORUS
_FLANGER
_FREQSHIFT
_PANNING
_PHASER
_SIDECHAIN
_TREMOLO
_WAHWAH
MULTI FX
_AIO - LIVE
_GLITCH - SPECTRAL
_GRAIN - STRETCH - SLICE - REORDER - TIME
_LOFI - 8 BIT - VINYL
PAN._MON-STE-3D
PITCH - HARM
REVERB
_BANK B
SATURATOR - TAPE
TOOLS
_CHORD-ARP-SEQ
_COMPARE - CHECK
_MODULAR - CHAIN
TRANSIENT - DE-VERB
VISUAL-ANALYZER
VOCALS
_DOUBLER - HARMONIZER
_VOCODER

-I use "_" to make sub folder at the top.
-Every plugin (.dll) is inside a folder with the name of the manufacturer except in the instruments, samplers that the name of the folder is the same as the name of the plugin.
-In the main structure, I put only the plugins that I use, for example, 5 plugins of each.If I have installed more I use the "_BANK B"
-The same structure is what I use for installers. Yes, each with its directory. (but in another drive.)

It's a bit of work when you install for example, fabfilter bundle, eventide bundle, ... have to separate each .dll to its directory / category. But then, it makes my job easier for me. If I'm looking for a delay, I know all the delays are there. If I want a chorus, everyone is in their place. I do not have to think and look for chorus in each manufacturer.

 

Last edited: Jan 4, 2019

WAY too many letters to type, i use c:\v

 

didnt kno ...dont use it anyway....
only benefit over vst2 is automated disable when not in use to save cpu ive heard

and again isnt youre vst3 system forced on you and has no good structure ?

 

I use VST 2 in Reaper for instruments, and VST 3 in Adobe Audition CC for FX and Mastering. VST 3 works way better than VST 2 in Audition.

 

but

then it is always near the bottom of folder structure.. How about 64vst, and 32vst...?

 

hm..yeah...worth a try...but you dont need to say x86 or x64 only a * is enough and you can keep it on same thread ..this way saves time on install just copy and paste and at one address attach the * and good is

i bet cause big timer adobe want to push vst3...always looking to make things better for d´future...their so nice these companys
kidding sry