Scaler 3 fails to open up in Logic, Ableton and Maschine Mk3 software and only works in standalone mode.
I am running a Mac Studio Ultra M1, 128 ram, 8 TB ,OS Sequoia 15.3.2.
Does anyone have any suggestions please?
Kind regards
2 Likes
Same issue. Won’t open in Ableton or Logic for me. Haven’t tried Maschine yet.
2 Likes
Hi @Ray587 Do try and reboot your machine after install. That should do it.
1 Like
I have uninstalled, installed and reboot for times. And still the same issue, What else can I do?
mines not opening up either I tried reinstalling and restarting.My issue started with repeated crashing using logic pro
MacBook Pro m2 96 gb ram 8 TB OS Sequoia 15.3.2.
1 Like
Can you please collect some crash reports?
2 Likes
Coming back here to say it also doesn’t open in Maschine 3. In addition, standalone crashes every time I try to save a chord set.
2 Likes
This program acts as if it was a non -ready beta version..
Dear developers, you need it overhaul, and upgradeit very quickly,it is useless at this stage
for a serious job because it is not reliable in this state.
-2x times runned in Standalone mode but since then no more.
-After several systems starting, sometimes works in the Daw, then not.
tested as plugin under 2 different DAW-s
1 Like
Wanted to post a link a this thread I found as this helped me get Scaler 3 to open in Logic, Ableton and Maschine (current versions of all DAWs on an M3 MacBook Pro running Sequoia 15.3.2). Scaler not opening - #2 by Steven
I’m still having the issue of Scaler 3 crashing every time I attempt to save a chord set. @davide is there a link to a thread with the fix to that as well?
1 Like
I’m experiencing the same issue. I was loading for a few days, but then all of a sudden, it stopped loading altogether in Logic.
Can you post more information (CPU, OS, DAW) and, if possible, crash report? These are the things that can help to detect the problem. The team is fast when needed to fix problems.
I have this too.
MBP M1 13.6.2 Logic Pro 11.0.1
Scaler was working and I was building an arrangement using multiple MIDI outs. I put the computer to sleep by shutting the lid without closing Logic (something that has never caused a problem in the past) and when it woke up, I only got a partial window like #2 by Steven above. I was unable to see ‘Editor’ view as an option in the window frame. I tried the remedy in that link, but it did not work, even in other projects.
At various points along the way, the project would not load at all, and I had to solve this by forcing it to open the ProjectData file from an earlier backup the project package.
Worryingly, it seemed to also knock out other third-party plug-in GUIs in the same manner (I have been at this for three hours and cannot remember at what point I discovered this though), although I managed to fix them by toggling Core Audio and changing drivers (which incurred a couple of crashes along the way, although because the stage does not seem to be to do with Scaler itself, I did not keep the crash reports), but Scaler did not come back. I tried various restarts and safe mode et cetera, and tried importing the assets of the project into a template, which would typically lock Logic (no crash reports at this point or later).
I did the usual various combinations of restarts and resets, Plugin Manager rescan/reset preference trashing and all that, and somewhere along the way, Scaler came back in fresh projects – sorry, there did not seem to be a specific eurika moment that I can report.
Then, by successfully importing everything but Scaler from my original project into a new one, I figured out that it seemed to be this particular instantiation of Scaler – I could get a fresh instantiation to work alongside the assets, but if I then just tried to import the original instance of Scaler, then it would lock up again.
This is particularly frustrating, because all my composition/arrangement eggs were in this now-corrupt basket and I had only been saving and backing up at Logic level, not in Scaler itself. My Time Machine seems to be glitching and I cannot get a very recent version of the project – although it is set to hourly intervals, it is jumping back to yesterday; obviously, a different issue and my problem, but just in case someone suggests this.
I don’t think that Logic stores third-party plug-in project-specific settings in a human-readable form… So, if anyone has any ideas of how I could regain my Scaler content without also importing the apparent corruption, I would be very grateful.
Update: I have had much better stability more recently (now on 3.0.1) and have run a Logic session for several hours without a crash.
Being a bit paranoid after the above, I have been saving incremental versions as discrete sessions every hour or so. I have also been saving Scaler’s settings as incremental presets.
Useless? That’s a strong word. It’s not even close to useless. I use it in my workflow every day. Yes, it’s still being worked on and will improve just like Scaler 1 and 2 did. There could be a hundred reasons it’s not opening for you which is why crash reports are essential. Make sure you’re completely cleaning all traces of it before reinstall. Personally, with Bitwig, I had to reinstall the DAW (from which I surmise there was probably a loose file in the cache, and what I did was overkill) so I’m not suggesting you reinstall your DAW to be clear.