Scaler 3 not recognizing new installed third party VST

Scaler 3 is working great with all my third part VST’s. Yesterday I added a third party VST to my Mac but unfortunately Scaler 3 does not load this VST in the Instruments/Manufacturer list. The VST is loaded in the VST3 and Component folders in the plugins folder. This new VST is also available in the Logic Pro X instrument options.
What am I doing wrong?
Thank you
Robert

Did you rescan your plugins in the Settings, Preferences dialog? Preferences can be accessed with the icon of three short lines in the upper right corner of the scaler window.

Hi, How are you?
I did a rescan of my plugins but still not recognized the new VST. Then I restarted the Scaler 3 app. with Rosetta followed by a complete rescan. This time Scaler 3 loaded the new VST.
I really appreciate your help
Regards,
Robert

I’m having an issue with my VSTs as I do not store them in the default directories, and from my first encounter with Scaler 3, I cannot stipulate a specific directory.

All the more reason to never change the standard locations - especially VST3 - which is managed and set by the OS and stipulated within the VST SDK from Steinberg to be an industry standard location for ALL plugin developers.

I must admit - I do not understand why anyone would need to do this as there is zero benefit whatsoever in installing a VST3 anywhere but in the default location.

S

Unless the user wanted to lump similar function VSTs into easier to manage categories because not all developers follow strict conventions to categorize their tools.

Edit: did I just fall into a baiting?

If you have small SSD with OS, and a lot of plugins, you need to put them elsewhere e.g on the external SSD. This is my case. In Reaper i have several "paths " and it finds them all, but I needed to set them manually.

Just confirming we are adding the ability to add custom VST folder paths in the settings menu - that will be here in 3.1, expected mid to late April

2 Likes

Respectfully - I would love to know what a “small” SSD is - here in 2025. It would have to be something like 64GB (or less) to have to put anything on another drive.

The actual plugin files (.vst3, .dll etc) are tiny. I have 420 VST3 installed right now, and it uses 17GB total.

Now if you are installing VST instruments like say - Spectrasonics Omnisphere and allowing it to install its libraries to your system drive - that is a vastly different conversation.

Most users install the plugin (and only the plugin) to the system drive and install all content libraries to another much larger drive or an external for space considerations.

S

Well, for me, small system drive is 256 GB, but I want it as empty as possible. I have so many applications, instruments and other stuff that I have 80 GB free and I install my libraries and plugins, when asked , on my 1 TB SSD. But I am not asked every time :grinning_face_with_smiling_eyes: Moreover, I want have everything centralized. If not, i don’t know what and where is installed.