Solved S1Pro7 Unable to locate VST3 plugins

[Justin]

Studio One Pro 7 scans the selected plugin folder but doesn’t detect the plugins in it. The plugins are definitely in the folder, but they only load into Studio One if I move them to the default location on my C: drive in the Common Files > VST3 folder."

Let me know if you're experiencing this too!

 

[Trucky]

Unlike soundsets, plugins don't require much disk space.
I always use and recommend using the default locations to all my clients.

 

[Lukas]

Hi and welcome to the forum!

Studio One Pro 7 scans the selected plugin folder but doesn’t detect the plugins in it. The plugins are definitely in the folder, but they only load into Studio One if I move them to the default location on my C: drive in the Common Files > VST3 folder."

...but they're not VST3 plug-ins?

 

[Vocalpoint]

Studio One Pro 7 scans the selected plugin folder but doesn’t detect the plugins in it. The plugins are definitely in the folder, but they only load into Studio One if I move them to the default location on my C: drive in the Common Files > VST3 folder."

Let me know if you're experiencing this too!

All VST3 plugins from all vendors are designed to install automatically to an industry standard folder without any user intervention:

C:\Program Files\Common Files\VST3.

This specific location path does NOT need to be added to the VSTPlugins tab in S1 either - it is scanned by default by the application.

Finally - it is not possible to install a VST3 manually - unless it is a plugin without an actual installer and you are dragging and dropping files here and there.

What is the plugin you are having issue with?

VP

 

[Justin]

Unlike soundsets, plugins don't require much disk space.
I always use and recommend using the default locations to all my clients.

View attachment 279

Because I'm all ITB and have a lot of plugins, I prefer to have all my plugins and sound sets on an external ssd.

 

[Justin]

Hi and welcome to the forum!


...but they're not VST3 plug-ins?

Thank you!

I'm specifically talking about vst3 plugins. S1P7 will scan any folder but it will not detect any newly added vst3 plugins. The only way I can get S1P7 to detect the newly added vsst3 plugins is in the default location. I should be able to move vst3 plugins to any location on any drive but that's not the case. There's not a problem with vst2 plugins. Is it not possible to have custom drive locations for vst3 plugins?

 

[Vocalpoint]

Because I'm all ITB and have a lot of plugins, I prefer to have all my plugins and sound sets on an external ssd.

I think most of us are "all in the box" but if you really want to avoid ANY trouble - like this spirit of this thread - you should install ALL plugins to the default locations 100% of the time.

VST3 plugins have strict rules and by design - they need be followed.

The main rule is: Always let every plugin installer - handle VST3 on it's own. All plugins will end up in C:\Program Files\Common Files\VST3

And no - you cannot have custom drive locations for these - this location is managed by the OS.

FWIW: You are not doing yourself any favors (or gaining anything good) by redirecting any plugins to an external drive.

Content - Absolutely. Plugins - never. They do not take excessive space and should always be left to install to the suggested defaults.

VP

 

[Lukas]

I'm specifically talking about vst3 plugins.

Okay, that's why I was asking whether you were referring to VST2 or VST3 plug-ins.

VST3 plug-ins must be in the VST3 default locations. It's part of the VST3 standard that there are only two system folders where VST3 can be stored.

Plug-in Locations - VST 3 Developer Portal

steinbergmedia.github.io

All custom locations are only for VST2 plug-ins.

The only way I can get S1P7 to detect the newly added vst3 plugins is in the default location.

Yes, that's how VST3 works.

I should be able to move vst3 plugins to any location on any drive

No...

I prefer to have all my plugins and sound sets on an external ssd.

Plug-ins are applications and they should not be installed on external drives. This will only cause problems. If you want, you can store content (sample data) on external drives. But don't do this with executables.

 

[Justin]

I appreciate you being so thorough and answering all my questions thank you