Scaler Freezes when try to save in another hard disk

When i try to save a scaler project outside of “C:\ProgramData\Scaler Music\Scaler 3\Presets\Use”
it creates the save file and Scaler Freezes for ever. I have to force terminate Ableton through task manager. (scaler runs as VST inside Ableton)
Then the save file is 0 bytes after forcing Ableton to close.
I also tried to give everyone full access at the folder that i was trying to save but it had the same behavior.
The path name is d:\Music Projects\27 Mar 2025 Project\New Preset(3).s3p

This happens always i also tried to load a default preset “Dreamy Synthwave” without altering anything at scaler and it does the same thing.

I try to save it to a secondary hard disk (not external).

I also tried running Ableton as administrator and the same happens.

I move between several computers and use one external harddrive for instrument libraries and presets.
When I try to save user preset on external HD instead of deafault folder on C: ( Scaler Music\Scaler 3\Presets\User) the DAW chrashes.

I tried in Reaper 7.22 and Ableton lite 12. both crashes.

edit: Ok, so I see theres no way to open presets that are saved outside of default folder anyway?´ A feature for Scaler 3.1 maybe?

Scaler 3 is super btw!!

.

Win 10
Processor Intel(R) Core™ i7-4700HQ CPU @ 2.40GHz 2.40 GHz
RAM 16,0 GB
Lagring 894 GB SSD KINGSTON SA400S37960G
Grafikkort NVIDIA GeForce GTX 850M (2 GB), Intel(R) HD Graphics 4600 (113 MB)
Systemtyp 64-bitos, x64-baserad processor
ext drive Kingston SXS 1000R/2000G

Hi @omonymos,

I had a similar issue, but on Studio One, with Studio One freezing when I saved the preset.

I wasn’t aware that saving to a non-standard location was the issue but it may well be, as I saved the preset to another location outside of the default Scaler 3 preset user directory.

I also might add that I am not aware of how we are able to use presets if saved anywhere other than the non standard location, when I try and load a preset, I cannot browse anywhere, only choose a pre-determined location including the User location.

Regards,
Justin

I saved a preset in FL studio, than had a Scaler screen freeze. After re-opening FL and scaler the preset previously saved had 0 information in it.

Hello @Lucian89

Just checking, have you installed the 3.0.1 Update?

Cheers.

@Steven,

I am not sure, but this sounds like a similar issue I am having. I tried saving a preset from within Scaler 3 audio version, but I saved the preset to a non-standard location. Am on Studio One Pro 7.

When I saved the preset, Studio One froze or hung and required me to kill it in task manager. When I tried opening the saved preset in Scaler 3 midi (VST3) the preset was empty like @Lucian89 reported.

I am using the latest version of Scaler 3, in my host it says Scaler 3 v1.0.2

1 Like

Hi @Lucian89. Did you try and save the preset outside of Scaler’s default location? Cheers

Yes sorry maybe i was not clear (English is not my main lang). The problem is that when i save a preset outside of Scalers default location everything freezes (Scaler & Ableton).

1 Like

No you’re fine, your message was clear. Thank you :slight_smile:

I just wanted to confirm if Lucian89 also saved the preset outside of Scaler’s default location. All good though, we’re investigating.

1 Like

Hi! I encountered the same problem.

With Scaler 3.1.3 standalone on Windows 11, when I save a preset in the default location (C:\ProgramData\Scaler Music\Scaler 3\Presets\User) or another folder from the same drive (for example, on the desktop), it works fine. But when I want to save it to another drive (real drive as D:\, or virtual drive for Google Drive), it freezes forever.

To replicate it, I just have to create a new project, with or without anything done on it, and try to save it somewhere.

Hi @Ariakan, thanks for your post. We’re currently working on improvements to the preset save/load path system, which we expect will prevent issues like this from occurring. We’re hoping it will be included in Scaler 3.2, but if not, it will definitely be part of a future update. In the meantime, we’d recommend saving presets to the default location. Appreciate your patience and the thorough report. Cheers.

It’s happening on 3.2.0 as well to me. Looking forward to having an actually functional preset browser, in the meantime I’ll set up an automatic backup of the default folder.