uninstall/reinstall w/o scan- no luck w/ vst 2,3.Standalone crashes when tinkering w/ midi edit but loads/works. Support ticket time.
1 Like
Crashing frequently for me too in FL studio. Using it for a couple of minutes than screen freeze.
Really weird. I loaded scaler 2 and that worked so i REPLACED it with scaler 3 and it works. (Still crashes if i do anything else.) Can’t load it directly, must replace scaler 2. Still tinkering w/ midi edit. Doesn’t seem right. Updated to latest version,maybe helped, i dunno.
It is crashing for me in FL Studio as well, but works in Reaper.
Scaler 3 crashes while inserting into current FL Studio, Ableton Live, and Bitwig Studio versions. It’s the same story with Cubes 13 Pro.
Ableton gives some info in logs:
2025-03-25T19:37:45.805397: info: VST3: Going to create: Scaler 3
2025-03-25T19:37:48.654926: info: VST3: plugin processor successfully loaded: Scaler Music ‘Scaler 3’ v1.0.2 (cid: {ABCDEF01-9182-FAEB-5363-4D7353636C33})
2025-03-25T19:37:48.655680: info: VST3: plugin supports the IInfoListener interface
2025-03-25T19:37:48.673256: info: Vst3: couldn’t initialize controller with processor state of Scaler 3: not implemented
2025-03-25T19:37:48.673277: info: VST3: parameter count is 2093
2025-03-25T19:37:48.674699: info: VST3: Created: Scaler 3
2025-03-25T19:37:48.674772: info: MemoryUsage: V: 6.3 GB, R: 1.1 GB, P: 1 GB
2025-03-25T19:37:48.704085: info: VST3: couldn’t get controller state of Scaler 3: not implemented
installed, once I entered the license crashed for me as well.
Did anyone find a fix for this? I am experiencing the same issue in FL Studio 21. Downloaded Scaler 3, loaded it into a project, and worked on the song all night without issue. Now this morning, any project with Scaler 3 loaded in the channel rack crashes immediately upon opening. It’s a powerful machine (intel 14700K w/ 64GB RAM), so that’s not the problem. I’ve tried restarting a few times.
I am on MACbook 16" M3pro latest OS and FLStudio latest beta. No crash neither with AU nor VST
I’m on FL Studio 2024 and, if you have a plugin open in Scaler 3 (in my case Analog Lab V) during playback synced with the DAW, any copying or adjusting of chords causes Scaler 3 to eventually crash. If you turn off DAW sync this doesn’t happen, but I figured I’d make it known anyway.
Worked fine for a while, but now just constantly crashing
Can you please share your OS, CPU,RAM, Reaper version?
Can you find an error message in Event VIewer and if so, can you copy it to this shread with the rest of information?
Thanks
Windows 10, AMD Athlon Silver 3050U, 10Gb RAM, Reaper 6.83. Thank you
Your version of Reaper is a bit outdated so maybe you could update it to some more recent. Unfortunately, I don’t have versions earlier than 7.07 so I cannot test 6.83.
In fact, I tried yesterday 7.07 for another issue, but it was not detailed test. However, what I tried was OK and no crash. Normally, I use 7.35
Is there a specific situation when it crashes or it’s random, or maybe while loading Scaler 3?
Did you have a chance to find the error message in the Event VIewer? This could be important.
Thank you. It seems to be mostly related to me trying to work on a song in 6/8 time. Scaler really struggles with this. Just trying to play the progression in the arrange page is rife with glitches and usually crashes trying to drag and drop.Some of the patterns don’t seem to line up to 6/8 time as well. i don’t know if Scaler is strictly 4/4, but if it’s supposed to work in 6/8 it’s struggling. I’m working on a session without any other plugins so it’s not a CPU issue. As far as my version of Reaper goes, I’m concerned to update with so many projects in flux. However, my initial testing of Scaler on a 4/4 session seemed to work okay,
1 Like
Hi. Using Reaper 7.35. Windows 11 pro, 32G RAM 13th Gen Intel Was just checking out the Chill Template, was about to drag the midi into Reaper and it crashed. I hope I did this right
Log Name: Application
Source: Application Error
Date: 3/29/2025 6:39:27 PM
Event ID: 1000
Task Category: Application Crashing Events
Level: Error
Keywords:
User: SMOKYG\sulbl
Computer: SmokyG
Description:
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: 0xc0000005
Fault offset: 0x0000000000318151
Faulting process id: 0x0x6994
Faulting application start time: 0x0x1DBA0FA00E0FF88
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: 6ae2f05e-e332-408c-8ebe-8ba9ca21d9b3
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
1000
0
2
100
0
0x8000000000000000
158118
Application
SmokyG
reaper.exe
7.3.5.0
67df599e
Scaler 3.vst3
1.0.2.0
67e0c215
c0000005
0000000000318151
0x6994
0x1dba0fa00e0ff88
C:\Program Files\REAPER (x64)\reaper.exe
C:\Program Files\Common Files\VST3\Scaler 3.vst3\Contents\x86_64-win\Scaler 3.vst3
6ae2f05e-e332-408c-8ebe-8ba9ca21d9b3
As an update. I still do not have Scaler 3 showing as a instrument in Cubase 14 pro. It shows as a FX (audio). I followed the directions for a clean install, rebooted after each step (delete files, reinstall). Shows correctly in Cubase 13 pro. Is there anything else that I can do to help alleviate this issue? Or will it be in a mid-April update.
When using multiple(!) Scaler 3 instances, Cubase crashes. For example 2 instances.
When you start Cubase the next time, Cubase sends a crash report.
Win 11, PC, Cubase
Scaler 3 in Standalone seems to work fine. When instantiated in Pro Tools 2024.6 via AAX running on OSX 14.6.1 on a Mac Studio M2 Max, the sound from the audio engine is distorted and glitches out. It froze PT and I had to restart the computer. I tried re-installing and it didn’t seem to work. I’ve just reinstalled it again and I can’t even instantiate it in Pro Tools without PT freezing up on me.
1 Like
I downloaded Scaler 3 yesterday and loaded it into an FL Studio 21 project. I worked on the song for a few hours last night without any issues. However, this morning, the project crashes immediately upon opening. Scaler 3 was the only VST used in the project.
When I create a new project and load Scaler 3 in the channel rack, I can open and close the project without error. Additionally, some earlier backups of the project open fine. After testing around 25 backups, I found the following:
- Backup at 15:10 – Opens without issue. Contains only a chord arrangement.
- Backup at 15:26 – Opens without issue. Still just a chord arrangement, but Keyscape is loaded in the main track.
- Backup at 15:57 – Opens without issue. Multiple tracks added with patterns. Keyscape remains in the main track, with the default Felt Piano used in other tracks.
- Backup at 15:58 – Crashes after a few seconds. The project stays open just long enough for me to notice an additional track using Omnisphere.
Any backup saved after this point crashes immediately upon opening.
I doubt resource contention is the issue, as I’m running a 14700K CPU with 64GB RAM, and CPU utilization only reaches about 8% when attempting to open the project. I’ve also tried restarting multiple times, but the issue persists.
For reference, I’m using FL Studio v24.2.2.
SC3 Crash After Multiple Times Dragging Chords / Deleting and Adding Tracks in the Arrangement Tab.
Mac Studio M2 Sonoma Ableton Live 12.1 using VST3
1 Like
Hi Support, the Scaler 3 standalone application crashes on my mac mini M2 , i was loading 2 UHE Hive Instances, in VST3 format. Hive never crashed on me when using it in Abelton Live 8-12 . I am still on Ventura if that matters.