I don’t know if you saw my other post, but my vst3 installed in a weird folder inside of program files. Do a search for vst3 and find the scaler vst3 and move it to common files where it belongs.
Then a scan inside fl studio will work
Thank you for your question: I now know what sandboxing in Bitwig means.
You are right : the behaviour was different with Bitwig, and not a crash like other DAWs, but everything worked ok after I rebooted.
For what it’s worth, I’ve found that the VST3 of Scaler 3 is more stable than the AU. I’m running on a Mac (13.7.4) and using Studio One, however. The AU may be better in Logic. But either way, I recommend doing stability tests with the two plugins, and see if that helps.
After loading Reaper in Offline mode and removing Scaler 3, I can then load a new instance of Scaler 3 vst within the session and it works (but I have lost all the scaler info created), it’s a temporary solution if I want to carry on work, but again, losing the scaler session with all the compositions makes it very difficult.
So it seems there is no VST conflicting with Scaler, moreso something within the build over time causes a corruption.
Really hope this gets addressed.
I’m using Bitwig on Mac and I have the same. Scaler 3 (VST3) first was very slow but now crashes.
How do I go about totally getting rid of everything Scaler installed, then install completely a fresh Scaler 3?
Crashing every time I launch in standalone mode on OSX Sonoma 14.7 as well. Rebooted and reinstalled, reinstalled without scanning plugins, etc. and I see the screen for a fraction of a second then get the crash.
It worked fine the first time I launched, then after quitting, hasn’t worked at all since. Plugin in Logic seems to be fine though.
Seems JUCE might be an issue.
I saved my crash log but don’t know how to post it to the forum.
Time Awake Since Boot: 130 seconds
System Integrity Protection: enabled
Crashed Thread: 0 JUCE Message Thread Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Termination Reason: Namespace SIGNAL, Code 6 Abort trap: 6
Terminating Process: Scaler 3 [3005]
Application Specific Information:
abort() called
When I open Scaler 3 in Cubase 14.0.20, then it crashes instantly?
1 Like
Almost same here.. It loads normally, can be used a few minutes, but then crashes occasionally with anything, usually drag chords…
1 Like
FWIW, I’ve found the Scaler 3 VST3 much more stable than the AU. I’m in Studio One Six on a Mac Ventura. Crashed a lot using the AU, hardly at all with the VST3.
I made a small arrangement with 4 tracks, one of the track uses a 3rd party VST3 (Softube Model 80). I saved this arrangement as a user preset.
Now everytime I try to load this preset, Scaler 3 crashes and simply closes without any message. It happens in standalone mode, as well as in FL Studio 24 (in this case, Scaler 3 AND FL Studio crash simultaneously).
Loading the stock presets seems to work normally, however.
Similar use case but in reaper. At some point a certain plugin causes Scaler to crash upon reloading the session
Same boat here. This is happened when i used external vsts and also an external effect in one of them. When i saved the scaler project it created a file 90+mb witch means that it streamed in the save file arbitrary memory data and when it tried to load them back it crashed…
Also i noticed before saving the session that for some “magical” reason the channel column that i had the external effect showed 4 effects instead of 3… so probably thats why it happened.
I will try to recreate the issue.
Update : no need for the preset to use a 3rd party VST to crash at some point on loading in FL Studio 24.
This time I just saved a 1 track 16 bar progression with only 1 internal sound, can’t open it anymore, makes Scaler 3 crash immediately… 2 hours of work lost…
Unfortunately I think this plugin is not usable in its current state. Like if at some point it corrupts the file.
I can provide the .s3p file in case a developer would like to analyze what’s wrong.
Agreed, considering I can reload the S3 VST in my reaper session (after deleting the corrupt S3 VST) then I can carry on…but all the S3 session data is obviously lost as I have to remove that plugin instance to continue…
All
Yesterday - while using SC3 in standalone mode - I was testing a nice little chord progression WITH Spectrasonics Keyscape loaded as a single Instrument source for the Main Track.
I saved this little idea as preset and exited Scaler normally.
When I try standalone again today - I get a quick flash of the Scaler 3 UI and then it disappears.
The Event Log and Reliability Monitor in Windows 10 22H2 records the following event data:
At first glance (based on the Keyscape.vst3 reference)- it appears that Scaler 3 thinks that Keyscape needs to come for the ride again - as it is clearly trying to load it OR it is trying to reload my single test preset from yesterday - and cannot.
Ideally - it should be opening in a default state (empty) and not trying to load anything.
This issue is repeatable, and the standalone is essentially unusable at this point.
Hope the dev team can take a look.
S
1 Like
The standalone does seem to start up with the most recent project loaded, which can take quite a while on my system if I have several weighty VSTs loaded. I have not found a way to say “start up empty” but I’m sure we’ll get one in a future update.
If there is a file with settings in SC folders, maybe that deleting it works
Do a copy of it anyway before deleting, in case that SC3 doesn’t recreate it
I found settings.pref in C:\ProgramData\Scaler Music and opened with Notepad
In my case, it contains the text below
you can try to delete (after having saved the file) some part that references to Keyscape, if it is there
1 Like
BTW, @davide
the fact that SC3 installs itself in a Windows protected folder can be the reason why presets and changed settings are not saved?
Took a deep dive into this file - no mention of Keyscape etc.
But I did figure out how to kill that preset - I just deleted the Scaler3.settings files and standalone works again.
Won’t be saving anymore presets in Standalone any more.
S
1 Like
Cool
It reminds me when my old TV didn’t work, and a slap on the case fixed the issue 
1 Like