C:\ProgramFiles\VstPlugins

o

C:\ProgramFiles\Steinberg\VstPlugins



Why??????????? please

 

If you're using VST3 it's:

C:\Program Files\Common Files\VST3
or
C:\Program Files (x86)\Common Files\VST3

depending on architecture (32/64 bit)

VST2 let's you specify where you want to install.

 

Also, if you ever install a plugin that's not VST3 and for whatever reason aren't given an option to choose your own VST folder, check here -

C:\Program Files\Cakewalk\Vstplugins

Ironic. Finding this location for the first time is NO cakewalk.

 

You can change your system's default VST paths in the Registry if you want. Some installers ignore it and install wherever they want anyway, but they're a minor amount

The following registry-key is set (win-x32):
HKEY_LOCAL_MACHINE\SOFTWARE\VST\VSTPluginsPath
The following registry-keys are set (win-x64):
HKEY_LOCAL_MACHINE\SOFTWARE\VST\VSTPluginsPath
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\VST\VSTPluginsPath

 

I believe one of the first descriptions in the VST sdk to developers was to put it in "C:\Program Files\Steinberg\VstPlugins"
later, when it spread ed out on consumer pc's they tried it again, this time recommending "C:\Program Files\Common Files\Steinberg\VST2". Nobody paid attention so...

The same is going to happen with VST3, some daws accept VST3 from any location that any person would want too,
It won't take long for developers to mess up again...

 

I'm hardcore against forcing VSTs to be placed in a set folder, such as VST3 tries to do. Simplest reason is that I do not want them on my system drive at all. I fixed it myself via junctions, but it's obnoxious that I have to do that instead of just being free to choose, like I can with VST2.

Same token applies to VST developers though. Friggin let me choose where I want them, don't just dump them where you want. MusicLab products are AWFUL about this, especially the older ones. They try to make up for stupidity by spreading copies of the DLLs ALL OVER the friggin place. I mean like 8x copies crammed all over the drive.

The sensible standard is "Let VSTs live wherever the end user wants. Plugins ALWAYS offer the user a choice during install as to where the desired place is", then you can still have a "default" for people who don't care and just want their stuff to work, but it doesn't force advanced users to hunt down rogue DLLs and symlink across drives just to have their plugins where they want.

 

Doesnt seem to be a VST path in Windows 10 in either location.

 

Those keys don't exist by default in Windows, so you probably just haven't installed anything that created them in the first place. You can try just making your own there, won't hurt anything. I dunno though really, I know nothing about Win 10 other than how much I don't want any part of it hahah

 

You can do it as C:\Vst or C:\x86 and C:\x64 too.

Default directory is ...Steinberg\VstPlugins because vst technology is a steinberg invention. But you can always make your own default folder.

 

Change the defaul vst location in the registry:

x86:
HKEY_LOCAL_MACHINE\SOFTWARE\VST\VSTPluginsPath
x64:
HKEY_LOCAL_MACHINE\SOFTWARE\VST\VSTPluginsPath
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\VST\VSTPluginsPath

 

Am I having double vision? I could swear I have replied to this topic but...

 

Threads merged. @Milton Vega Please do not post more than single thread for one question.