Hi Tristan
Just to clarify, this has happened twice (before a clean install). Ive now performed a clean install and will monitor the situation
Regards
Mark
Hi,
Yes, that worked. Thanks
1 Like
Scaler 3.1: Crash in Cubase (PC, Win 11)
Cubase 13.0.51 64bit2025.7.12 19.49.25.080.dmp (1.0 MB)
When closing the Cubase project
@proteus would you mind confirming that this is the correct crash log? Upon investigation it appears this crash was caused by a different plugin: DecentSampler, not Scaler 3.
Hi @Leander – thanks for your post and for including the .dmp file. I’ve moved it here, as this thread is the best place for our devs to monitor and diagnose crashes. Cheers.
1 Like
Hi Tristan
That seems to be the latest one, ive attached an earlier one just in case (the next in descending date order). Its odd if it is actually another plugin causing the crash because it went away when I disabled scaler and never happened again as long as it remained disabled. The instant I re-enabled it, Cubase crashed.
Regards
Mark
(attachments)
Hi support Ive Updated scaler 3 to 3.1.7 but it still crashes Studio 1 and s1 is telling me scaler is the problem so much so that I can only use the stand alone version are there any fixes?
1 Like
Hi @robinoz, sorry to hear about the crash you’re experiencing. We’re planning to release an update soon that includes important stability improvements. You can bookmark the Scaler 3 Latest Version thread to be notified of updates. Thanks for your patience. Cheers.
Hi, I’m a Studio One user (latest version 7.2.1) on Windows 11 and as soon as I load an instance of Scaler 3 (3.1.0.4 latest version from Scaler Music) Studio One crashes.
The same happens for the audio version of the plugin.
The standalone version runs fine.
Thanks to everyone at Scaler for continuing an open dialog as you work through bug fixes and updates. I wish other companies adhered to the same level of standards.
I am still however continuing to experience crashes in Reaper on a Windows 10 computer.
Reaper has always been stable for me with this set up and Scaler 3.1 has been significantly more stable (than earlier versions). But when I start to click and drag select in the arrangement window it still crashes itself and Reaper entirely.
Faulting application name: reaper.exe, version: 7.1.4.0, time stamp: 0x660ea0bc
Faulting module name: Scaler 3.vst3, version: 3.1.0.0, time stamp: 0x68597105
Exception code: 0xc0000005
Fault offset: 0x00000000006e5ca2
Faulting process id: 0x2200
Faulting application start time: 0x01dbf9ccc79e077e
Faulting application path: D:\REAPER\reaper.exe
Faulting module path: C:\Program Files\Common Files\VST3\Scaler 3.vst3\Contents\x86_64-win\Scaler 3.vst3
Report Id: 8fde1ce4-a540-4131-a0ba-e9310204611b
Faulting package full name:
Faulting package-relative application ID:
I’m not going anywhere but I thought I’d try and do my part to help.
If there is a better crash report to look for let me know where to find it.
Thank you.
Hi all,
Scaler 3.1.1 is now available. This update includes a number of improvements and important fixes, and we strongly recommend it for all Scaler 3 users.
You can download the 3.1.1 installers from Plugin Boutique (under My Account) or from Scaler Music (under My Products).
For full details, see the latest version thread for the complete changelog.
Cheers.
Hi Steven
I’m afraid the update still crashes Ableton 12.2.1, I was just moving a chord from the current scale to the main track. Report attached
Ableton Crash Report 2025-07-23 170808 Live 12.2.1.zip (3.0 MB)
Hi @lynnfield72, sorry to hear you’re experiencing this, and thanks for sending the crash report. We’ll take a look.
I don’t want to sound like a broken record, but did you perform a clean install of version 3.1.1? Since you’ve had a few issues before, I’d recommend doing that.
Moving a chord from Section B to the Main Track definitely shouldn’t cause a crash (and doesn’t for me in Live 12.2.1 on macOS). Is the crash repeatable on your end? Also, does it happen in other DAWs? Sorry for all the questions – just want to get to the bottom of this for you. Cheers.
Hi Steven
Yes it’s a clean install. It hasn’t happened yet in Logic or Reason. Ableton has crashed twice since my post, so I’ve uninstalled Scaler.
Thanks
Ian
Thanks for getting back to me, Ian. The devs will take a look at the crash report you’ve supplied. Cheers.
Scaler 3.1.1 Stand-Alone Scaler Still Shuts Down/Aborts Quickly
I downloaded and did a clean install of Scaler 3.1.1. but still the Stand-alone version opens with the hourglass and quickly shuts down. I have Windows 10.
Hi @PeterKHewer. Thanks for your post and sorry to hear you’re still experiencing this issue.
Could you please check the Windows Event Viewer to see if any error is logged around the time Scaler shuts down? That information would be really helpful for our dev team as we investigate further.
I opened Scaler 3.3.1 stand alone just a few mintues ago. It closed quickly with the hourglass still showing. Perhaps the probklem that I have the large Omnispere VST3 as my Scaler sound engine. As you can see below Omnisphere is mentioned on line 2 of the Event Log which is pated below.
I hope this helps. I am going to use the Scaler Plugin and set to the internal sound engine. Perhaps this would eliminate Omnisphee from the Stand-Alone load of Scaler 3.1.1 Otherwise it would be good if you could tell me how delete Omnisphere from being in the opening instantiation of Scaler 3.1.1
Please let me know what you suggest. I hope this helps and the event log below.
Log Name: Application
Source: Application Error
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: DESKTOP-BNQBE5U
Description:
Faulting application name: Scaler 3.exe, version: 3.1.1.0, time stamp: 0x687e79ba
Faulting module name: Omnisphere.vst3, version: 2.8.7.0, time stamp: 0x66e8aa5c
Exception code: 0xc0000005
Fault offset: 0x000000000063d394
Faulting process id: 0x10dc
Faulting application start time: 0x01dbffce67194435
Faulting application path: C:\Program Files\Scaler Music\Scaler 3\Scaler 3.exe
Faulting module path: C:\Program Files\Common Files\VST3\Omnisphere.vst3
Report Id: eaf4f257-3f98-489b-968e-81b125a81ab4
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns=“http://schemas.microsoft.com/win/2004/08/events/event”>
1000
0
2
100
0
0x80000000000000
267428
Application
DESKTOP-BNQBE5U
Scaler 3.exe
3.1.1.0
687e79ba
Omnisphere.vst3
2.8.7.0
66e8aa5c
c0000005
000000000063d394
10dc
01dbffce67194435
C:\Program Files\Scaler Music\Scaler 3\Scaler 3.exe
C:\Program Files\Common Files\VST3\Omnisphere.vst3
eaf4f257-3f98-489b-968e-81b125a81ab4
Hi, I’ve been unable to reload FL Studio projects I made with Scaler 3.0.1. I’ve installed the 3.1.1 upgrade, no change. I completely removed and reinstalled FL Studio and did a full fresh plugin scan in it, no change. When (re-)scanning for plugins with Scaler 3, it stops with scanning VST3 plugins with "Error occurred while scanning your plug-ins! (Error 2), then terminates. Because the error is in front of the window showing the currently scanned plugin, I don’t know which one it terminates on.
I’ve looking for logging of Scaler 3 scanning plugins, but haven’t found it.
Edit: I’ve deleted the files listed at the top of this thread. Doing some further testing it turns out adding a Scaler 3 instance to an empty FL Studio project now crashes it without further input.
This is a typical Windows event after FL Studio crashes while loading a program with Scaler 3:
Faulting application name: FL64.exe, version: 25.1.1.4879, time stamp: 0x68766825
Faulting module name: ntdll.dll, version: 10.0.26100.4652, time stamp: 0x6c6bd922
Exception code: 0xc0000005
Fault offset: 0x000000000012e163
Faulting process id: 0x1E90
Faulting application start time: 0x1DBFF9CC6A12B56
Faulting application path: C:\Program Files\Image-Line\FL Studio 2025\FL64.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 8160b925-036a-4971-b67b-38e2f5d52854
Faulting package full name:
Faulting package-relative application ID: