Scaler 3 Update & Crash Files

[Steven]

All good, @Deva.

How to Find Crash Reports on macOS (via Console)

• Open Console
  Press Cmd + Space, type “Console”, and hit Enter.
• In the sidebar , go to “Crash Reports”
• Look for a file with the name of the app that crashed (e.g. Bitwig_2025-04-08-123456.crash).
• You can either: click the Share button to export the file, or just *copy the text and paste it into a .txt file (or directly into your message if it’s short)

Cheers

[Defender]

Having crashes opening up previous saved files on Mac. Report attached.
CrashReport.rtf (51.7 KB)

Also some previously saved files now won’t load, and Scaler just sits there with the spinning ball (have waited u till 30 minutes). Is there anyway to get these files open? Would hate to lose the work. I think that they ones that produce the spinning ball all have the Dune 3 VST3 loaded.

[Gemini-musician]

I updated my WIN11PRO PC (Ableton Live 12 Standard) to version 3.0.1 and crashing persists. Was able to find my crash file:

If you see this, provide feedback about it.

[Herbert]

Hi. I was able to use Scaler 3 standalone for about 3 days at the beginning. Now Scaler 3 always crashes when I want to start it. The update 3.01 does not work either. I deleted the settings.pref file before the new installation, restarted the computer 2 times. Scaler 3 works as a plugin with Logic Pro. I send the crash report with me. Best regards, Herbert
Scaler 3 Crash Standalone.rtf (60.4 KB)

[Justin]

+1

– pretty much the same (plus my plugin crashes reported in another thread).

but no crash log in DiagnosticReports

M1 MBP 13.6.2

[TC242HH]

My plug in is crashing all the time since the update…

[Steven]

Hello @Justin, check out this post which should help you locate a crash report. Thank you.

[Steven]

Hi @TC242HH, sorry to hear that. Just wondering, did you perform a clean install prior to installing the update? Regardless, if you wouldn’t mind sharing a crash report we’d appreciate it as they’re very helpful for us to identify issues that some users are experiencing.

[Unlistenable]

Tried to use the shift - mouse gesture (wheel) feature to scroll through chords on the main track and experienced immediate crash. First experienced crash in Studio One but the standalone version crashes as well. Attached is the crash file. I am on an M1 MacBook Pro and was using a Magic Mouse. Running version 3.01 (clean install as recommended). Experienced the same problem when using one of the included templates in stand alone mode.
Crash Log - Scroll.rtf (280.5 KB)

[Steven]

Hi @Unlistenable, thanks for providing the crash log. I’m on a M1 MacBook Pro as well and couldn’t reproduce this, but we will certainly look into the log you’ve provided. Cheers.

[Justin]

Thanks Steven. I’m afraid that it is not registering anything in Console.

[SNC]

I am running Cubase Pro 14. It has never crashed. Since adding Scaler 3 it has crashed three times in ten minutes, always immediately after I press a function in scaler 3 (e.g. muting or unmuting a track).

[TC242HH]

Logic ends up without any report. It just close down. So the standalone version as well since 3.01.

[davide]

Welcome to the forum @SNC Have you restarted your machine? If so follow these instructions:

Install the latest version (in your account scalermusic.com)

Mac - Clean Install:

• Delete the standalone state file in this folder: /Users/[NAME]/Library/Application Support/Scaler 3.settings
• Delete the personalised files in this folder: /Users/[NAME]/Library/Scaler Music/Scaler 3
• Delete the shared user files in this folder: /Users/Shared/Scaler Music/Scaler 3
• Reinstall.

PC - Clean Install:

• Delete the standalone state file in this folder: C:\Users[NAME]\AppData\Roaming*Scaler 3.settings*
• Delete the personalised files in this folder: C:\ProgramData\Scaler Music*Scaler 3*
• Delete the shared user files in this folder: C:\Users\Public\Documents\Scaler Music*Scaler 3*
• Reinstall.
  Users may also remove the actual plugin binary files for VST/VST3/AU/AAX. However if you reinstall with your DAWs closed, these should be overwritten when reinstalling.

[Steven]

Hi @TC242HH. Yeah that’s what happens for me, then I open Console and can see the crash reports. AUHostingServiceXPC is the Logic report and Scaler 3 is for Standalone. Then the respective ‘Translated Report’ can be copied and pasted into a .txt file.

[Dxnnydxn]

As the title suggests when trying to resize chords in the arrangement view instant crash in standalone, fl studio,Luna etc

I tried the scaler 3 1.0.4 still happening after clean install

[Steven]

Hi @Dxnnydxn, thanks for your post. We couldn’t reproduce this so could you please provide a crash report?

[MusicTilly]

Not sure if reported elsewhere. Found one example, but said fixed in latest release. I believe I am on the latest version.

I do have a short video to show case, once I work out how to share. Here is the screenshot of the lasso as the blue circle of death appears and then crashes. No error messages.

[Steven]

Hi @MusicTilly, thanks for your post. Couldn’t reproduce this one, are you able to provide a crash report?

[rcook]

I haven’t been able to pin down the exact steps to get my project into the state, but I’ll share what I know. I have a REAPER project containing a track with an instance of “VST3i: Scaler 3 (Scaler Music)” on it. I have a sequence of chords and when I drag to select it crashes consistently. I don’t know what is special about the project.

OS: Windows 11
REAPER v7.35 (x64)
Scaler 3 v1.0.3.c53a073

This is the error message from the Windows event log:

Faulting application name: reaper.exe, version: 7.3.5.0, time stamp: 0x67df599e
Faulting module name: Scaler 3.vst3, version: 1.0.3.0, time stamp: 0x67e6efeb
Exception code: 0xc0000005
Fault offset: 0x000000000067e395
Faulting process id: 0x3C50
Faulting application start time: 0x1DBA8D55439420D
Faulting application path: C:\Program Files\REAPER (x64)\reaper.exe
Faulting module path: C:\Program Files\Common Files\VST3\Scaler 3.vst3\Contents\x86_64-win\Scaler 3.vst3
Report Id: 25a00e52-6404-441a-b96d-8017a90fec17
Faulting package full name: 
Faulting package-relative application ID:

Looks like a null pointer dereference or similar.