Problem with some plugins after reinstalation.

[MC2]

I installed several new plugins, among others Miroslaw Philharmonik 2 and Vital.
After installing, unfortunately I do not see them in Studio One. And after resetting the plug updates I receive the info "Some Plug-Inss Will Be Updated Next Time You Start Studio One" Philharmonik 2, Vital, Saturation Knob.
Unfortunately, after restart Studio One still cannot be seen, although the scanning shows that it is in the scan. On the disk, the plugins are where the other VST2 or AU are.
Earlier on the same hardware and software configuration (i.e. before I did the reinstall of the operating system) Vital an others was working properly.
What's wrong? How to fix it?
This is on MacOS Sequoia and newest Studio One Pro

 

[Trucky]

Have you checked their status and the Blocklist in Studio One's Plug-In Manager?

I'm running Windows 11 but I've been told that it's best for Mac users to use VST3 versions instead if their available.

Also, can you post a screenshot of your VST Plug-Ins Location settings in Studio One Options?

 

[MC2]

There is nothing on the list of blocked plugins - empty. However, when it comes to plug location paths, these are standard system folders.
I also noticed that the problem does not occur when I run the studio One in Rosetta mode. The question is what to do to make it start correctly?
Folders with plugins:
/Users/merlin/Library/Audio/Plug-ins/ VST
/Library/Audio/Plug-ins/VST

 

[Trucky]

What about my response regarding VST3 versions?

I'd recommend submitting a Support Ticket (see link in my signature) if you haven't done so already.

 

[MC2]

To be sure, I also added a VST3 folder to configuration but it didn't help.
Interestingly, Studio One sees the version AU of the plugin and does not see VST or VST3

 

[Vocalpoint]

I also noticed that the problem does not occur when I run the studio One in Rosetta mode.

I believe this is the norm now for Mac OS - VST2 was discontinued in Mac OS a while ago and running in Rosetta is the only way to use these now

If you want to avoid Rosetta - all plugs must be VST3.

VP

 

[MC2]

I believe this is the norm now for Mac OS - VST2 was discontinued in Mac OS a while ago and running in Rosetta is the only way to use these now

If you want to avoid Rosetta - all plugs must be VST3.

Ok However, the Studio One sees only the AU version. Regardless of whether Rosetta or not, the VST3 version does not see.

 

[Trucky]

To be sure, I also added a VST3 folder to configuration but it didn't help.
Interestingly, Studio One sees the version AU of the plugin and does not see VST or VST3

While the newer VST3 format has a dedicated installation path all VST3 plug-ins must comply with, the VST2 standard does not know an obligatory folder. However, on Apple systems there is a defined plug-in folder within the system's folder structure since the first version of Mac OS X.

All VST plug-in installers for Mac are using these folders:

Format Path
VST2 Library/Audio/Plug-ins/VST
Rarely used: Users/your username/Library/Audio/Plug-ins/VST

VST3 Library/Audio/Plug-ins/VST3
Rarely used: Users/your username/Library/Audio/Plug-ins/VST3

The 'Plug-ins' directories contain both a VST and a VST3 folder as well as folders for other plug-in formats. In most cases, plug-ins installed correctly into these folders should be available in compatible host applications. However, in some VST hosts, scanning of VST and VST3 folders must be enabled in the VST host's settings.

 

[Vocalpoint]

Ok However, the Studio One sees only the AU version. Regardless of whether Rosetta or not, the VST3 version does not see.

As Trucky perfectly noted - Studio One looks to the industry standard VST3 locations - BY DEFAULT.

Would be very curious to see exactly what this dialog looks like on your machine:

This is mine - using Windows and VST3 exclusively. No extra non-standard paths. No "extra" paths to VST3's and - no problems either.

Studio One picks up every single VST3 on my system - direct from this single industry standard VST3 directory (Windows) - which is:

C:\Program Files\Common File\VST3

If you are not seeing these specific VST3 upon a typical plugin scan in Studio One - your plugins are either not in the industry standard Mac location - or you have altered/moved them in some strange way. OR - IK Multimedia does not follow industry standards - which would not surprise me in the least.

Vital - I can confirm - does follow the standards - as I have it here - installed correctly - and without intervention - to my standard VST3 location.

VP

 

[MC2]

As Trucky perfectly noted - Studio One looks to the industry standard VST3 locations - BY DEFAULT.

Would be very curious to see exactly what this dialog looks like on your machine:

Well, in the VST3 and VST Mam and Philharmonic 2 folder in the appropriate version and Vital in the appropriate version.

So the problem is elsewhere ...

 

[Vocalpoint]

Well, in the VST3 and VST Mam and Philharmonic 2 folder in the appropriate version and Vital in the appropriate version.

So the problem is elsewhere ...

Problem is right here:

This VST3 path does not need to be in this dialog. I do not have any paths at all - and my VST3s come flying in with no problem.

Studio One uses that VST3 path - by default. There is zero need to list it here.

The other paths there would be for VST2 only - and if were me - I would only use:

/Library/Audio/Plug-ins/VST

and ditch the very first entry. (while moving anything in there - to the directory above)

After making these changes - head into Plug-In Manager and click Remove Plugin Settings. Answer yes when S1 asks you - and let it restart and rebuild your plugin DB.

If these plugins do not show after all this - they are either blacklisted, non-compliant or do not physically exist in the VST2 path listed OR the standard VST3 path (not needed to be listed)

VP

 

[MC2]

Problem is right here:

View attachment 1347

This VST3 path does not need to be in this dialog. I do not have any paths at all - and my VST3s come flying in with no problem.

Studio One uses that VST3 path - by default. There is zero need to list it here.

The other paths there would be for VST2 only - and if were me - I would only use:

/Library/Audio/Plug-ins/VST

and ditch the very first entry. (while moving anything in there - to the directory above)

After making these changes - head into Plug-In Manager and click Remove Plugin Settings. Answer yes when S1 asks you - and let it restart and rebuild your plugin DB.

If these plugins do not show after all this - they are either blacklisted, non-compliant or do not physically exist in the VST2 path listed OR the standard VST3 path (not needed to be listed)

VP

I haven't had a path for VST3 so far. But after the discussion I added because I thought it would change something. Has not changed.

As for the changes you are writing about, at the moment I will refrain from introducing them, because in parallel I correspond with Support and wait for their verdict (I sent them files with the current configuration, so I will abstain for now with its modifications)

However, I am thinking about the legitimacy of using VST3 plugins in the MacOS environment since all the plugins I have are also in AU versions. And all the DAWs I use also read AU format.
Is there in this specific situation the legitimacy of using VST3 instead of AU?
Leaving only one version can strongly reduce the amount of space on the system disk.

 

[Vocalpoint]

Is there in this specific situation the legitimacy of using VST3 instead of AU?

There is a specific reason when it comes to Studio One.

AU is generally never tested in S1 by vendors as AU is a Logic-only format. VST3 on the other hand is tested relentlessly by everyone.

Your call - but the general consensus - for a long while - to avoid AU in Studio One at all times and roll with VST3 whenever possible.

VP

 

[MC2]

Hmm...
Apparently yes, but for example Iris 2 isotope 2 I install the AU, VSTV2 and VSTV3 version ...
Only the AU version is visible in the Studio. And after checking, it looks like this is the AUV2 version.

 

[Vocalpoint]

Hmm...
Apparently yes, but for example Iris 2 isotope 2 I install the AU, VSTV2 and VSTV3 version ...
Only the AU version is visible in the Studio. And after checking, it looks like this is the AUV2 version.

I want to be clear - Studio One "supports" AU for sure. But that does not mean it is the best choice - and it is not.

And Iris 2 is ancient and discontinued. It would have had a VST2 for sure back in the day - but not sure it ever had a VST3

Would also be very helpful to see what your view of Plugin Manager looks like - here is mine (Win 10):

1 - Plugin types to display

2 - Plugin format priority to use (WITHIN Studio One)

3 - Plugin Visibility. Lightbulb On = show in S1. Lightbulb Off = Hide in S1

VP

 

[MC2]

Iris 2 definitely has a VSTV3 version, because I have a file in the VST3 folder. The same with Vital or Philharmonic 2. Unfortunately, there are no files in the manager.

 

[Vocalpoint]

Iris 2 definitely has a VSTV3 version, because I have a file in the VST3 folder. The same with Vital or Philharmonic 2. Unfortunately, there are no files in the manager.

Can I get a screenshot of your "actual" VST3 folder - showing both the path to it and the files in it?

VP

 

[sintil8]

I have Iris VST 3.

All default directories as per VP has described.

Regards

 

[Davey]

Have a look through the log file "VSTPlugInScanner.log". It's plain text and shows all the plugins that were examined and any errors encountered.

On Windows the file is in "%APPDATA%\PreSonus\Studio One 7\x64"
and you can get to the parent of that folder in S1 by choosing "Help -> Open Settings Folder"

I know nothing about the Mac folder structure but that log file is bound to be in there somewhere.

(It would be useful for S1's Plugin Manager to have a button to open that log file)

 

[Vocalpoint]

Have a look through the log file "VSTPlugInScanner.log". It's plain text and shows all the plugins that were examined and any errors encountered.

On Windows the file is in "%APPDATA%\PreSonus\Studio One 7\x64" and you can get to the parent of that folder in S1 by choosing "Help -> Open Settings Folder"

Good one. Forgot about this file.

Pretty sure the Mac install has the same logging.

VP