Scaler 3 Update & Crash Files

Scaler 3 Support Bug Reports
344

I finally had a chance to try Scaler 3.1 and it still has all the same undo-related crashes that plagued the earlier versions. Based on playing around with it this and previous versions I think there is mismatch between what Scaler thinks is in the undo/redo stack and what JUCE thinks is in it. I’ve noticed some undos don’t actually undo anything and if I keep undoing after that it always eventually leads to a crash.

Process:               Scaler 3 [13070]
Path:                  /Applications/Scaler 3.app/Contents/MacOS/Scaler 3
Identifier:            com.scalermusic.scaler3
Version:               3.1.0 (3.1.0)
Code Type:             ARM-64 (Native)
Parent Process:        launchd [1]
User ID:               501

Date/Time:             2025-07-01 13:32:37.7569 -0700
OS Version:            macOS 15.5 (24F74)
Report Version:        12

Crashed Thread:        0  JUCE Message Thread  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000068
Exception Codes:       0x0000000000000001, 0x0000000000000068

Termination Reason:    Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process:   exc handler [13070]

VM Region Info: 0x68 is not in any region.  Bytes before following region: 4332535704
      REGION TYPE                    START - END         [ VSIZE] PRT/MAX SHRMOD  REGION DETAIL
      UNUSED SPACE AT START
--->  
      __TEXT                      1023d4000-104790000    [ 35.7M] r-x/r-x SM=COW  /Applications/Scaler 3.app/Contents/MacOS/Scaler 3

Thread 0 Crashed:: JUCE Message Thread Dispatch queue: com.apple.main-thread
0   Scaler 3                      	       0x102ab4a90 Scaler::Sequencer::NoteSequence::replaceTransforms(Scaler::Sequencer::ActionContext const&, std::__1::list<std::__1::shared_ptr<Scaler::Sequencer::Transform>, std::__1::allocator<std::__1::shared_ptr<Scaler::Sequencer::Transform>>> const&) + 64
1   Scaler 3                      	       0x102b58824 Scaler::Sequencer::TransformAddAction::undo() + 28
2   Scaler 3                      	       0x102526460 juce::UndoManager::undo() + 116
3   Scaler 3                      	       0x102a6a9bc non-virtual thunk to Scaler::Plugin::PluginEditor::keyPressed(juce::KeyPress const&, juce::Component*) + 80
4   Scaler 3                      	       0x10261926c juce::ComponentPeer::handleKeyPress(juce::KeyPress const&) + 216
5   Scaler 3                      	       0x102624d1c juce::NSViewComponentPeer::handleKeyEvent(NSEvent*, bool) + 256
6   Scaler 3                      	       0x1026247e4 juce::NSViewComponentPeer::redirectKeyDown(NSEvent*) + 76
7   Scaler 3                      	       0x102624470 juce::NSViewComponentPeer::sendEventToInputContextOrComponent(NSEvent*) + 560
8   Scaler 3                      	       0x102625144 juce::JuceNSViewClass::JuceNSViewClass()::'lambda8'(objc_object*, objc_selector*, NSEvent*)::operator()(objc_object*, objc_selector*, NSEvent*) const + 100
9   Scaler 3                      	       0x102625284 juce::JuceNSViewClass::JuceNSViewClass()::'lambda8'(objc_object*, objc_selector*, NSEvent*)::__invoke(objc_object*, objc_selector*, NSEvent*) + 32
10  AppKit                        	       0x1947396e8 -[NSView performKeyEquivalent:] + 140
11  AppKit                        	       0x19500e4bc -[NSWindow _commonPerformKeyEquivalent:conditionally:] + 68
12  AppKit                        	       0x194e7302c routeKeyEquivalent + 224
13  AppKit                        	       0x194e70fdc -[NSApplication(NSEventRouting) sendEvent:] + 652
14  AppKit                        	       0x194a7042c -[NSApplication _handleEvent:] + 60
15  AppKit                        	       0x1944c6c8c -[NSApplication run] + 520
16  Scaler 3                      	       0x102530400 juce::JUCEApplicationBase::main() + 192
17  Scaler 3                      	       0x102530320 juce::JUCEApplicationBase::main(int, char const**) + 88
18  dyld                          	       0x190122b98 start + 6076
345

Hi @GrapefruitDream. Appreciate you posting the crash report and context. The dev team will take a look. Cheers.

346

Hi @Ktal, welcome to the forum. Thanks for sharing theses details and sorry to hear you’re experiencing a crash in FL. You should be able to retrieve a crash report from the Console app on macOS or Event Viewer on Windows. If you can share that report here, it will help our dev team investigate what’s going on. Cheers.

347

Hi @tkcrows – welcome to the forum, and sorry to hear about the crashes. If possible, could you share a crash report from the Console app (macOS) or Event Viewer (Windows)? That’ll help our dev team investigate further. Thank you.

348

When I open standalone version chords are not bound even tho the bind sign is turnet on..then i have to turn it off and On again and then it’s ok. this was fixed once but now the bug is back again -.-

349

Hi Tristan,

Thanks for getting back to me. It seems to have worked. I have tried that three times and the last time seemed to have stuck.

350

SC3 - Crash Using Progression / Secondary Scale Module After Multiple Undos

Running the SC vst in Abelton Live, I was creating and editing a progression in the Main Track on the Create Page using Progression & Secondary Scale. i was doing a fair bit of bouncing back and forth to the Browse page. In the process I was adding and deleting chords and using the undo function. On an Undo, the app crashed Live.

Live-2025-07-08-110313.txt (343.7 KB)
SC3.1.04 Live 12.2 M2 Studio Sequoia

351

Hi @jeffreyk - appreciate the detailed report, I was able to reproduce the crash on my end. We’ll investigate further. Cheers!

352

After updating to scaler 3.1 I’m now experiencing a problem where cubase (Pro 14) just shuts down immediately after opening where there is a scaler vst in the project. There are no error messages, it simply shuts down. I have to open with all plugins disabled, disable scaler in the project, save & shutdown. I can then reopen the project. If I subsequently reactivate scaler in the project, Cubase immediately shuts down again. This has now happened twice, it never happened before the 3.1 update. I have performed a clean reinstall (as per instructions in known issues) and Ill monitor the situation, but I have lost confidence in scaler being a stable, reliable product. I’m using Windows 11 pro.

353

Hi @proteus, no this does not sound good. This isn’t something I’ve experienced on Windows 11 using Cubase with Scaler 3.1 but it is something we’d like to look into given you’ve experienced in several times.

Can you check in your Documents/Steinberg/Cubase folder to see if there are any crash reports from these incidents? They may be in a ‘Crashdumps’ folder. If you are able to send these to us we can try to figure out what is going wrong.

354

Hi Tristan

There is a crash dump which I think is the correct data but there is no option to add a file attachment here when I reply

355

Hi Tristan

Ive added the attachment here

Regards

Mark

(attachments)

Cubase 14.0.32 64bit2025.7.8 16.07.40.511.dmp (2.03 MB)

356

Scaler 3 File Crash in ¾ time - file attached

Is there a section to upload corrupted or crashing Scaler 3 files? This file crashes the standalone version of Scaler on every opening.

Scaler Crash

357

Scaler 3 Standalone shutdown

Scaler 3 standalone running under Win 11.
Program starts then immediately shuts down. No chance to do anything.
Event log reports this…
Faulting application name: Scaler 3.exe, version: 1.0.7.0, time stamp: 0x682376ea
Faulting module name: Scaler 3.exe, version: 1.0.7.0, time stamp: 0x682376ea
Exception code: 0xc0000409
Fault offset: 0x0000000000b813a9
Faulting process id: 0x1668
Faulting application start time: 0x1DBF1D2285C1D7E
Faulting application path: C:\Program Files\Scaler Music\Scaler 3\Scaler 3.exe
Faulting module path: C:\Program Files\Scaler Music\Scaler 3\Scaler 3.exe
Report Id: cbf5df55-a774-4cf0-b66f-f49a3b8abd19
Faulting package full name:
Faulting package-relative application ID:

4 hours before it was running perfectly, then closed it and put Win 11 into sleep mode. No further activity.

Unable to find any other information.
Can you help?

358

Hi @Steven As a follow up, after working on this project a little further, SC started exhibiting some odd behaviour (when trying to Edit Chord, removing or adding a note caused SC to change all the notes in the chord so it was something totally different). After closing the project I was unable to reload the project file. Using Live I am able to recreate the file loading each track individually into a new project (which also includes an instance of SC in the template.) Using this approach, the original track holding SC would not load, the project hung trying to load it and required a Force Quit, suggesting it has been corrupted in some way. I can’t send any crash information as it seems Live doesn’t generate the usual crash report in this circumstance.

359

Thanks @proteus we have sent your crash log to the dev team to investigate. It is concerning if you have encountered this multiple times after a clean install. So we’ll see what can be addressed in the upcoming 3.1.1 update.

360

Hi @exVista,

If you did not try this (which works in a huge majority of cases), can you delete
C:\Users[NAME]\AppData\Roaming\Scaler 3.settings and let us know?

361

Hi @jeffreyk. Thanks for following up, and sorry to hear about this experience. If you’re comfortable sharing the corrupted Live project, it would be helpful for our devs. Feel free to DM me if you’d prefer. Cheers.

362

Hi @exVista. Thanks for sharing these details, and sorry to hear the Scaler 3 standalone is crashing on you. To add to Miki’s suggestion, I noticed you’re running version 1.0.7.0. I’d recommend performing a clean install of the latest version: Scaler 3.1. You can follow the steps outlined here. Hopefully that solves the issue for you. Cheers.

363

Hi @Baskervils. Thanks for your post and for including the crash report. I’ve moved it here – this is the best place to upload corrupted Scaler 3 files so the dev team can take a closer look. Cheers.