FR: add path-option to scan for plugins

Scaler 3 Feature Requests Implemented
1

I put my VST2 plugins in a dedicated VST2 directory, so in Scaler 3 they currently don’t show up :frowning:
Cheers, Marcel

2

It seems there are different problems when it comes scannig and using VST´s: I tried VST 2 and 3 in different directories, including the default ones. A few VST 2 and 3 are recognised, others not, even if they in the same directory! It seems Scaler 3 expects special properties to scan and include a plugin correctly. And even if a plugin seems being recognised correctly during the scanning process this does not mean that it is listed as own instrument in the end (using Windows 10 and Mulab 10 here).

3

They are going to add custom VST paths in a future update.
I expect they will also improve the scanning process so that fewer VSTs fail.

4

Scaler 3.1.0.6 adds support for specifying custom VST folder paths.