Hi,
today i was just saved a preset and after that when i try to load it to scaler 3.1 it crashes.
This is happening in standalone and in Ableton.
Attached the preset in case it may be usefull for debuggin.
1 Jul 2025.zip (30.7 KB)
Hi @omonymos. Appreciate you reporting this â Iâve tested the preset and can confirm it causes a crash for me too. Iâve logged the issue with our dev team and included your preset, along with a crash report from my end. Cheers.
Add me to the chorus of folks with this issue. This has now happened before and after the update with separate created presets. Standalone Scaler 3 crashes when I try to load it, and the entire Ableton project becomes unusable, giving a âserious program errorâ message (attached) when I open it.
Iâm attaching the most recent preset and error report, and a screenshot of the Ableton error message. Ableton Crash Report 2025-07-08 225602 Live 12.2.1.zip (1.8 MB)
Ableton Crash Report 2025-07-08 225937 Live 12.2.1.zip (2.7 MB)
After SW Chords.s3p.zip (43.8 KB)
Iâve also made a folder with the Ableton project in question, and a âsafeâ version pulled from the backup earlier that day for reference on what else is loaded in the project. I also put a previous occurrence of this issue in the folder, but donât have those project files to attach because I deleted them before pinpointing this as the issue.
My system is a MacBook Pro M3 with 64GB running Sequoia 15.5, and my Ableton is 12.2.1, with the most recent update of Scaler 3
I hopefully donât have to spell out why taking out a whole project is a pretty huge concern, but itâs making me hesitant to use Scaler 3 at all, and I love the program!
Hi @jgoose welcome to the forum. Sorry to hear of these issues youâre encountering.
You mention âwith specific user presetsâ. So are you saying these issues only occur after selecting a preset youâve made via the preset menu at the top of the screen? So if you load an Ableton Live project containing Scaler 3, but do not manually load a saved preset in Scaler 3, you donât have this issue?
If so we can certainly take a look at these preset files and try to find out what is going wrong. Are you hosting any 3rd party plugins in these user presets?
Basically yes, only specific user presets, and only a fewâ Iâve made a number of presets that give me no problems at allâ both with and without hosted VSTs. Itâs just been these handful that create this issue, but they seem to be completely random, so it feels a little like a ticking timebombâ especially since once it happens, I canât open that preset, or the project it was loaded in, to figure out what the heck happened.
I am like 90% sure this most recent instance is all Scaler instrumentsâ (I canât open it to confirm)â if I remember correctly, I was actually about to load a 3rd party VST, Nexus in this case, when it crashed, but I donât think I even got a chance to actually open the VST before the crash, so Iâm pretty positive it was still a Scaler-stock instrument when it crashed and stopped opening. I believe all of the corrupted presets were originally created in an instance loaded in Ableton, and they all have maybe 2 to 3 expressions of a main chord setâ thatâs about all I can think of that they have had in common.
Thanks @jgoose that is interesting. Are you able to share any of these presets here so we can investigate? If you have trouble uploading here as a zip file you may need to link to a cloud storage service of some kind. You can DM me the link if youâd prefer.
Happy to- they should all be linked in my original post, but just in case, everything is uploaded to Scaler 3 Ableton Bug - Google Drive
Iâve had the problem a couple of times before that (twice if I remember correctly) but donât have the files from those, after doing a clean install of both programs
Happened again, and now Scaler 3 wonât open in standalone form at all. I copied all of the non-scaler tracks over to a fresh Ableton project and they all open fine, but the original project crashes Ableton with the same âserious program errorâ the second I open it. I know 100% this time, Scaler was exclusively using internal instruments. Unfortunately Iâm going to have to delete Scaler 3 from my system until this gets sorted out, hopefully soon, because this is just beyond frustrating at this point.
I added all the error messages logs, my most recent preset, and my project files to the cloud in a new folder, along with the preset log and the preferences file, both of which show theyâve been updated since the crash. Jul 17 Crash - Google Drive
Hi @jgoose if Scaler 3 is only not opening standalone this is likely on account of the standalone state file. This should be resolved by deleting the following file: /Users/[NAME]/Library/Application Support/Scaler 3.settings
Note that we believe to have discovered the cause of your initial error which likely also led to your standalone issue and will be releasing a Scaler v3.1.1 update very soon addressing this and several other issues to improve overall stability and operation.
You can bookmark the following forum page using the forumâs bookmark feature to be notified when this update is released: Scaler 3 Latest Version - #6 by davide
Hello,
My Scaler 3 crashed after loading a specific state file, one I was working on long time, in stand alone mode.
Could somebody help me to make it work again, and what I need to do?
Thank you,
Kind regards,
Marko
Hi @MARMIL86 - welcome to the forum, and sorry to hear youâre experiencing that.
Weâre aware of an issue where certain user presets or saved states can cause crashes. This will be resolved in version 3.1.1, which weâre aiming to release as soon as possible.
The 3.1.1 beta successfully opens the preset that OP attached, which was causing a crash, so hopefully it will open your state file too - keeping all your hard work intact. Cheers.
OK, thanks, how Scaler 3 is updated? By downloading installer somewhere, or some other way?
This is fixed in Scaler 3.1.1. Please see latest version thread and download the 3.1.1. installers either at Plugin Boutique (My Account) or Scaler Music (My Products):
I may confirm that it works fine now!
Thanks a lot!