3.0.1 Update & Crash Files

[Steven]

Hi everyone.

Firstly, thanks to everyone who has provided feedback—it helps us improve Scaler 3.

We’re preparing a 3.0.1 update for release next week, which will include stability improvements and some additional enhancements.

Most users experiencing stability issues have managed to resolve them, often with a reboot of their machine.

If you’re still experiencing issues, please upload your crash files to this thread, along with details of your setup (e.g., OS, DAW, or standalone version) and any steps to reproduce the problem. This will help us better address the issues you’re encountering in the 3.0.1 update.

Thanks.

[Rob-Rob]

Hi,
I’ve rebooted and my machine is usually very stable without any problems, running Ableton Live, only Scaler 3, no other apps open or plugins running. I did some basic chord explorations, changing main chords, selecting scales etc. I have not been able to run Scaler 3 more than 10-20 min in several sessions. DAW transport is running while I use Scaler 3.

Ableton Live 11.3.41

MacOS Monterey, 12.7.6

Model Name: MacBook Pro
Model Identifier: MacBookPro18,1
Chip: Apple M1 Pro
Total Number of Cores: 10 (8 performance and 2 efficiency)
Memory: 16 GB

Crash Report:

Translated Report (Full Report Below)

Process: Live [1389]
Path: /Applications/Ableton Live 11 Suite.app/Contents/MacOS/Live
Identifier: com.ableton.live
Version: 11.3.41 (2025-02-05_f95eb4fae9) (11.3.41 (2025-02-05_f95eb4fae9))
Code Type: ARM-64 (Native)
Parent Process: launchd [1]
User ID: 501

Date/Time: 2025-03-28 08:47:19.7065 +0100
OS Version: macOS 12.7.6 (21H1320)
Report Version: 12
Anonymous UUID: 44BB0DE1-4178-5E7F-455E-6E05D8AE1080

Sleep/Wake UUID: 1EB327CB-D1DC-468F-8310-1FFDE11FA8AE

Time Awake Since Boot: 3700 seconds
Time Since Wake: 670 seconds

System Integrity Protection: enabled

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

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000000000000f0
Exception Codes: 0x0000000000000001, 0x00000000000000f0
Exception Note: EXC_CORPSE_NOTIFY

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

VM Region Info: 0xf0 is not in any region. Bytes before following region: 105554592661264
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
UNUSED SPACE AT START
—>
MALLOC_NANO (reserved) 600058000000-600060000000 [128.0M] rw-/rwx SM=NUL …(unallocated)

Kernel Triage:
VM - pmap_enter failed with resource shortage
VM - pmap_enter failed with resource shortage
VM - pmap_enter failed with resource shortage
VM - pmap_enter failed with resource shortage
VM - pmap_enter failed with resource shortage

Model: MacBookPro18,1, BootROM 11881.81.4, proc 10:8:2 processors, 16 GB, SMC
Graphics: Apple M1 Pro, Apple M1 Pro, Built-In
Display: Color LCD, 3456 x 2234 Retina, Main, MirrorOff, Online
Memory Module: LPDDR5
AirPort: Wi-Fi, wl0: Apr 6 2022 05:55:54 version 20.90.45.0.8.7.118 FWID 01-e7138ff2
Bluetooth: Version (null), 0 services, 0 devices, 0 incoming serial ports
Network Service: Wi-Fi, AirPort, en0
USB Device: USB31Bus
USB Device: USB31Bus
USB Device: USB31Bus
Thunderbolt Bus: MacBook Pro, Apple Inc.
Thunderbolt Bus: MacBook Pro, Apple Inc.
Thunderbolt Bus: MacBook Pro, Apple Inc.

[squitsysam]

Faulting application name: reaper.exe, version: 7.3.5.0, time stamp: 0x67df599e
Faulting module name: Scaler 3.vst3, version: 1.0.2.0, time stamp: 0x67e0c215
Exception code: 0xc0000409
Fault offset: 0x0000000000b5a70d
Faulting process id: 0x209c
Faulting application start time: 0x01db9e8496178c88
Faulting application path: D:\ReaperDirectory\reaper.exe
Faulting module path: C:\Program Files\Common Files\VST3\Scaler 3.vst3\Contents\x86_64-win\Scaler 3.vst3

Can load up reaper in offline mode, remove scaler 3 and the session is recoverable, but all the scaler 3 session info is gone, it’s a temporary fix for me. Activating a new instance of scaler 3 works. So it seems that the build simply corrupts over time, it’s less about other plugins conflicting with it.

[flexoffset]

Standalone version. OS X M2 Pro Mac mini w/ Sonoma 14.7
It launched the first time, then when I was finished, I quit the app and now it won’t launch.
Crashes immediately on startup and throws up the ‘report to apple’.
Is there any way to completely remove it? Re-installs don’t work, reboots don’t work.
Scanning for plugins, not scanning for plugins… nothing works.
I think if I could trash the prefs I might have some luck.

Crash log attached as a *.txt file.

scaler3_crashlog.txt (59.2 KB)

[Phommed]

Scaler 3 VST3 crashed hosted in VCVRack standalone 2.6.3 VCVHost, when it received the start of a clock signal (24 ppqn)

[17029.395 fatal adapters/standalone.cpp:49 fatalSignalHandler] Fatal signal 11. Stack trace:
/Applications/VCV Rack 2 Pro.app/Contents/MacOS/Rack: fatalSignalHandler(int) +0x28
/usr/lib/system/libsystem_platform.dylib: _sigtramp +0x38
/Library/Audio/Plug-Ins/VST/Scaler 3.vst/Contents/MacOS/Scaler 3: SyncedDelay::processBuffer(juce::AudioBuffer<float>&) +0x430
/Library/Audio/Plug-Ins/VST/Scaler 3.vst/Contents/MacOS/Scaler 3: Scaler::Sampler::SoundManager::processBlock(juce::AudioBuffer<float>&, juce::MidiBuffer&) +0xe4
/Library/Audio/Plug-Ins/VST/Scaler 3.vst/Contents/MacOS/Scaler 3: Scaler::Playback::PlaybackEngine::processTrack(juce::AudioBuffer<float>&, juce::MidiBuffer&) +0x448
/Library/Audio/Plug-Ins/VST/Scaler 3.vst/Contents/MacOS/Scaler 3: Scaler::Playback::PlaybackEngineManager::processBlock(juce::AudioBuffer<float>&, juce::MidiBuffer&) +0x128
/Library/Audio/Plug-Ins/VST/Scaler 3.vst/Contents/MacOS/Scaler 3: Scaler::Plugin::PluginAudioProcessor::processBlock(juce::AudioBuffer<float>&, juce::MidiBuffer&) +0xb14
/Library/Audio/Plug-Ins/VST/Scaler 3.vst/Contents/MacOS/Scaler 3: void JuceVSTWrapper::internalProcessReplacing<float>(float**, float**, int, JuceVSTWrapper::VstTempBuffers<float>&) +0x384
/Users/richardsmith/Library/Application Support/Rack2/plugins-mac-arm64/VCV-Host/plugin.dylib: VST2Wrapper::process(int, int) +0x7c
/Users/richardsmith/Library/Application Support/Rack2/plugins-mac-arm64/VCV-Host/plugin.dylib: HostedVST::_MCStep() +0xe8
/Users/richardsmith/Library/Application Support/Rack2/plugins-mac-arm64/VCV-Host/plugin.dylib: HostedVST::_MCWorker() +0x54
/Users/richardsmith/Library/Application Support/Rack2/plugins-mac-arm64/VCV-Host/plugin.dylib: void* std::__1::__thread_proxy[abi:v15006]<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct>>, std::__1::__bind<void (HostedVST::*)(), HostedVST*>>>(void*) +0x40
/usr/lib/system/libsystem_pthread.dylib: _pthread_start +0x88
/usr/lib/system/libsystem_pthread.dylib: thread_start +0x8

Full crash log:
Scaler3VCVRackCrash.txt (134.0 KB)

[hampelican]

I’m having an issue whereby if I go to the arrange page, hold shift and scroll, the app crashes. This happens in standalone mode or hosted in a DAW (in which case the whole DAW crashes). It happens every time without fail.

scaler 3 crash report.rtf (220.7 KB)

[DucksOnQuack]

Audio detection apparently manages to eat the Ableton Cpu usage, only when trying to use that feature, and it takes a while for it to render the chords after trying to detect them. Only scaler 3 eats up the DAWS CPU by more than 100 percent, take it off then its back to normal 1 percent.

Ableton Live 12.1

Windows Pro 11

Nvidia 3060 Ti
AMD Ryzen 7 3700X 8 core
16 cores total, threaded
Game Strix B550-F gaming (Wi-Fi)
Memory: 32 GB

[rezeik]

It worked right after I installed it, but now the standalone version crashes right after run it.
The AU plugin version can be run.
I’ve attached the log output by Mac OS when it crashed.
scaler3crash.txt (52.8 KB)

Apple M4 Pro RAM 48GB
MacOS15.3.1（24D70）

[flexoffset]

Exactly my issue. Your JUCE thread looks like mine. Our crashes seem to be the same.

[Funksta]

It’s Scaler because Reaper and Studio One on my Intel system does this as well. I tested it from the lowest buffer to the highest on my RME and it performs worse the lower you go. It’s bairly useable at 1024 samples, forget anything under that.

I run a 13900k, x64gb of Ram, NVME drives, Windows 11, RME interface, it taps my CPU out 100% using detect audio. Something isn’t right with the feature. You have to remove Scaler or force quit as it will keep your CPU and Fans running flat out.

On the plus side I havn’t suffered from any install problems or crashing yet.

[eruelas]

My Scaler 3 crashes every time on standalone version, even after restart, It worked fine once after installation, but after quitting and trying to reopen, it never opened again. It opens in Ableton 12.1 fine so far. I am working on a PC running Win11.

[jeffreyk]

This is similar to the Cubase and dragging chords bug already posted in the main Support thread.

Dragging on chords in arrange view causes Live to crash. Was able to repeat immediately after rebooting Live. Tried to attach the Live report in .ips format which is not accepted here.

Mac Studio M2 Sonoma Ableton Live 12.1 using VST3

[Unlistenable]

Crash when recalling User Template that includes Keyscape. Studio One 6.6. MacBook Pro M1.Rebooted after installation

Crash Log attached
Scaler 3 Crash Log - User Template.rtf (88.1 KB)

[TurdCity69]

I have a Mac Mini m2 Pro. Running sequoia 15.3.2. Scaler 3 corrupts/disrupts opening and closing Pro Tools sessions. It happens 50% of the time. I sent crash logs to AVID. Did not affect my system. Only Pro Tools. I can use Scaler 3 but I have to remove it each time. Thanks!

[AngelCabreraMusic]

I am so sorry Scaler 3 does not run for Macs OS High Sierra 10.13.6
Following all the videos around Scaler 3 I think it can be adapted to High Sierra 10.13.6
WA with the time made InstaChord possible to run in High Sierra 10.13.6
So I bouhgt it
I am a Scaler obssesive since its begining
Would pay for Scaler 3 easy
But my eMac Mid 2011 is a high value I am not going change

Hope Scaler people can do the upgrade Scaler 3 to High Sierra 10.13.6
If not, I will keep on happy with my Scaler 2 and Scaler Simple

By The way. I use Scaler 2 but I have both (Scaler 2 and Scaler)
Now I was to check my Scaler (first) and now change to a demo expired
I bought it from Plugin Boutique.

Not that big issue, but would like to have both working.

Thanks

[tonedef_scaler]

When I lassoed and dragged/dropped a large set of chords from the C section to a sketch, the standalone Scaler 3 crashed to desktop.

Attached is a Windows 11 crash dump.
Scaler 3.exe.8868.dmp.zip (6.6 MB)

[davide]

That is a big and fixed in 3.0.1 and in your Scaler Music account now.

[ZincT]

Is there a change log anywhere for 3.0.1?

Thanks

[davide]

It’s a silent update so not officially but here goes.

• NEW Chord Panel Display (shows notes and chords on MIDI input)
• FIX Bound area not reverting to white keys when turning of Keys Lock | Chord Notes/Extensions/Scales Profile
• FIX Crash when dragging multiple chords to Sketch Page when chords extend past row limit
• FIX Crash when adjusting velocity of individual notes with multiple chord clips selected.
• Improves stability