Scaler 3.1 Error 2 scanning plugins and crashes when eporting to wave file

Scaler 3 has been crashing regularly when exporting to wave file since 3.0. I have put in support tickets and always sent to forum for solution, so here I am. Also got an ERROR 2 message when I added Waves Central path and STEAM path for Omnisphere and Trillian. This is all on the standalone version. My DAW is Studio One 7.2. I haven’t tried 3.1 in Studio One yet. I upgraded to 3 for the standalone version. I am on Windows 10. Is anyone else having these problems? I have had nothing but trouble and major waste of time since I upgraded to Scaler 3. Any real help would be very much appreciated. Thank you.

Hi @Beelmon,
Please delete:
Mac → /Users/[NAME]/Library/Application Support/Scaler 3.settings
Win → C:\Users[user name]\AppData\Roaming\Scaler 3\Scaler 3.settings

This should fix your problem

Hi Miki,
Thanks, but I do that all the time and it does not fix the problems. I wish it did.

I am sorry to hear this. Yes, Omnisphere is quite a “big one”. I addde a few tags - maybe other users of Omnisphere and/or Studio One read this. Hopefully someone has the fix. Yes, you can try 3.1.

I just noticed you had Scaler 2 Support instead of Scaler 3 Support, so I changed it.

Thank you Miki. I hope so too.

Hi @Beelmon I believe both of the issues you mention are listed on the Known issues forum page which provides additional info and ETAs for fixes.

Error 2 when scanning for plugins is usually on account of Windows permissions issues. This can usually be resolved by performing the plugin scan when running Scaler 3 standalone as an administrator. So right click on the Scaler 3 executable and choose run as administrator and try the plugin scan again. Let me know how you go as occasionally other steps are required.

The crash on audio export is something that has been known to occur when using two or more 3rd party plugins. This is will be resolved in the upcoming 3.1.2 update.

1 Like