Scaler 3 Update & Crash Files

After a few more Scaler 3 session attempts I got back into the immediate crash at startup of standalone Scaler 3 that I and others were seeing on earlier versions, so this is still not fixed on v1.0.5. This happens when deserializing the state of the session that was saved at the previous closing of the app and persists until the /Users/[NAME]/Library/Application Support/Scaler 3.settings file is deleted.

Call stack of the offending thread:

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 [78964]

Application Specific Information:
abort() called


Thread 0 Crashed:: JUCE Message Thread Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib        	       0x182d33720 __pthread_kill + 8
1   libsystem_pthread.dylib       	       0x182d6bf70 pthread_kill + 288
2   libsystem_c.dylib             	       0x182c78908 abort + 128
3   libc++abi.dylib               	       0x182d2244c abort_message + 132
4   libc++abi.dylib               	       0x182d10a24 demangling_terminate_handler() + 320
5   libobjc.A.dylib               	       0x1829b93f4 _objc_terminate() + 172
6   libc++abi.dylib               	       0x182d21710 std::__terminate(void (*)()) + 16
7   libc++abi.dylib               	       0x182d216b4 std::terminate() + 108
8   Scaler 3                      	       0x104691d20 Scaler::Plugin::PluginAudioProcessor::deserialize(juce::MemoryBlock const&) + 420
9   Scaler 3                      	       0x10418fbcc juce::MessageQueue::runLoopCallback() + 352
10  CoreFoundation                	       0x182e548a4 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 28
11  CoreFoundation                	       0x182e54838 __CFRunLoopDoSource0 + 176
12  CoreFoundation                	       0x182e5459c __CFRunLoopDoSources0 + 244
13  CoreFoundation                	       0x182e53138 __CFRunLoopRun + 840
14  CoreFoundation                	       0x182e52734 CFRunLoopRunSpecific + 588
15  HIToolbox                     	       0x18e3c1530 RunCurrentEventLoopInMode + 292
16  HIToolbox                     	       0x18e3c7348 ReceiveNextEventCommon + 676
17  HIToolbox                     	       0x18e3c7508 _BlockUntilNextEventMatchingListInModeWithFilter + 76
18  AppKit                        	       0x1869ca848 _DPSNextEvent + 660
19  AppKit                        	       0x187330c24 -[NSApplication(NSEventRouting) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 688
20  AppKit                        	       0x1869bd874 -[NSApplication run] + 480
21  Scaler 3                      	       0x10418a86c juce::JUCEApplicationBase::main() + 192
22  Scaler 3                      	       0x10418a78c juce::JUCEApplicationBase::main(int, char const**) + 88
23  dyld                          	       0x1829ec274 start + 2840

It is a little bit better now…

I send my crash report via email because it is too long. I did a complete reinstall. Davide send the information. It still crash after ca. 40 sec. Of chords.

Has anyone here had Scaler 3 standalone crash before it opens. I have tried numerous reinstalls, turning off my Apollo Duo interface, and things I don’t remember at the moment. Nothing at all has worked. It crashes at start up and that’s it. The program runs in Studio One 7 but runs clunky there too. Anyone with the same or similar experience?

I’ve gotten into this instant crash on startup state numerous times. So far I’ve always been able to fix it by deleting Scaler’s settings file as Davide describes here.

Hi,
I have tried to delete that file as well, but there is no file to delete.

Just upgraded to 3.105 ableton 11 (latest, but not 12) Mac M1 Pro with updated seqoia, everything running stably for over a year (once i ditched Universal Audio lol), now while playing around with Scaler 3, my DAW rashes, sometimes immediately after re-opening the app. I ran through all the basic reboots, haven’t done a “clean install” as it installed a fresh copy when i got the update. The old version remains on my machine as well (not for long, if I can get 3 stable). 16 gigs of RAM, 50 gig or more available on an SSD Thunderbolt 3 drive. What can be done? I was pretty excited to give 3 a try, as many of the improvements are why I stopped using 2.

Scaler 3 crashes so much it made throw my computer against the wall now i have a new mac and it crashes lafter 2-4 actions. I have to keep saving then i lose track of what i did . Sad but we still here

SC 3.105 Crash / Clean Install / Standalone

Playing around with chords in the Main Track. Highlighting, extracting voicing. Applying voicing. Preceded by several Undo’s. One performance track and one bass track created.

Mac Studio M2 Sonoma 14.2
Scaler 3-2025-04-21-151833.txt (33.9 KB)

Scaler 3 version 3.0.5 Crashing in Ableton Live 12 Standard (window 11 Pro)

Hi @pettydavis, welcome to the forum, and sorry to hear you’re experiencing issues. I’ve moved your post to this thread as it’s the best place for tracking Scaler 3 crashes. Could you please share a crash report here? Cheers.

I made the update of the current version which is 3.0.5 and the third party plug-in feature works better than the last version but the current issue that exists is that it’s still randomly crashing my Win11PRO PC. I viewed my “Event Viewer” and saying that for every error the faulty path is scalar 3. I did the deleting of the certain paths that were mentioned in this form by other users and it works temporarily but when there is a new update the issue continues to persist. It seems to me that it’s only a quick fix and not a long-term solution.

1 Like

In 1 hour, Standalone Scaler crashed 3 times on my Windows 10 PC .

This is insane, and it doesn’t seem to have a specific reason. I’d be just moving some notes and testing chords, and it just crashes…

1 Like

Hello @soulbrix ,

Did you try do delete C:\Users\jasic\AppData\Roaming\Scaler 3\Scaler 3.settings? This helped me a few weeks ago.

Also, did you do the clean install? If deleting the .settings file does not work, you could try this one.

Hi @Gemini-musician. Sorry to hear you’re still experiencing issues. Would you mind sharing a crash report? Cheers.

Same here, using both Standalone and as a VST within Reaper. The crashes result in instant closing of the program / Reaper and are unfortunately making it unusable. I can’t keep losing work like this. Until they (hopefully) make it far more stable in the next update, I’ll be using Scaler 2/other composition tools. It’s a shame because it has real potential from what I’ve seen so far.

Hi @soulbrix, sorry to hear you’re still experiencing issues. I’ve moved your post (and @BredS’ reply) to this thread as it’s the best place for tracking Scaler 3 crashes. Could you please share a crash report? Cheers.

Thanks @Steven - where can I get the crash report? Is it a log produced by the app itself?

So where’s the update already need to be able to drag midi please!!!

Hi @soulbrix

On Windows, you can view Scaler 3 Standalone crash reports using Event Viewer:

  • Press Win + R, type eventvwr, and hit Enter.
  • Go to Windows Logs > Application.
  • Look for errors with Source like Application Error or AppHangB1.
  • Double-click an entry to view crash details — look for entries mentioning Scaler3.exe as the faulting application or module.
  • You can copy the details into a .txt file and then upload here.

Hope that helps and thanks for your support. Cheers.