Is this the best folder structure for VST plugins

Plugins
1

[Is this the best folder structure for VST plugins]

C:\Program Files\Common Files\VST3 - For64bit VST3 plugins
C:\Program Files\Steinberg\VSTPlugins - For 64bit VST2 plugins
C:\Program Files (x86)\Common Files\VST3 - For 32bit VST3 plugins
C:\Program Files (x86)\Steinberg\VSTPlugins - For 32bit VST2 plugins

2

32-bit plugins won’t be recognized in Gig Performer. You can use something like jBridge to create bridged 64-bit plugins, but they aren’t always going to be stable.

Those 64-bit folders are pretty standard (though I have C:\Program Files\VSTPlugins as my vst2 folder), but it doesn’t really matter as long as the locations are referenced properly within GP (via Plugin Manager > Manage > Set Folders for Scanning).

3

Thanks for the reply. I do have jBridge, but need to reinitiate it. My VST file structure is all over the place and I am trying to get a handle on it by moving them into the common folders. Seems like C:Program Folder (x86) could be relocated in the C:Program Folders\Common directory. Of course with the (x86) in the name description. Once moved I realize I will have a lot of Re-scanning to do in GP5, MidiGuitar2, Sonar, etc.

4

Also missed the fact that GigPerformer scanner shows 32bit files in Red. I didn’t get that at first. Just thought they were incompatible for some reason.

5

But don’t call us — absolutely zero support for issues due to trying to run 32-bit plugins :slight_smile:

6

Thank you. I have used jBridge in the past and it worked fine for the most part. I realize their are potential issues. Just to have access to some old plugins is great.

7

I also realize I have to many plugins’ which makes it a daunting task. If I had it to do all over again, I think I would have gone with something other than the Waves plugins. I like there plugins, I just don’t care for the way they are managed. However I invested to much to make a change now.

1 Like