Strange behaviour using a bunch of Divisi tracks in one Scaler VST instance. Worked on a project for quite a few hours using a whole bunch of different VST (2 or 3 Ujam plugins, SoundPaint, RealGuitar plugin and a few others). I love the way Scaler is letting me compose using the Divisi feature BTW. I had not used Scaler much and this is getting me back into using the program. Anyways, all was fine last night. I closed S1 (Studio One) and worked on some other stuff. Today, I tried to open the project again but upon opening, Studio One just froze completely, unresponsive. Only way to close was task manager. I opened up other projects that didn’t have Scaler and they were fine. I tried multiple times but no luck in getting Studio One to work with this project. So I uninstalled Scaler, opened the project and of course Studio One opens this project fine but when clicking the track with Scaler vst on it, it of course says plugin not found (because it’s uninstalled). So I re-installed Scaler, added another vst track ok and opened up my preset I had saved on that track and it worked fine on this new track. I just deleted the track I was having the problem with and all is well now. Just reporting this in case anyone else comes across a similar issue. I reckon the original Studio One track it was on somehow got corrupted, I will check the log files to see what I can see there with Windbg. Probably just a one-of.
Now this is happening in another project I started this weekend. Same thing. Close the project. Reopen and everything is just freezing up. No way to get out of it. The Scaler 3.2 overlay comes up and that’s it. Boom. It’s done. No escape, no closing. Have to use task manager every time to just close Studio One. And this is only when working on an instrument track in Studio One with Scaler 3.2 instrument VST on that track and working on a composition, adding some vsts and tweaking a bit and at some point. It just does this. Hard to work on new stuff this way…
Anyways, not sure if it does the same in Standalone, I could give it try but I wanted to try & use my DAW to possibly expand on sound and capabilities at some point. I can offer some diagnostic files if it helps.
Ok, I tried opening Scaler 3.2 standalone but for some reason, it was stuck trying to open the prior project files I was working on with Studio One and even froze in Standalone mode. So, I have uninstalled it, removed all the Scaler 3 folders that were created (renamed my presets so I don’t lose my work) and reinstalled and rebooted and it seems to be opening up ok now. I put the preset folders back to where it was originally and even opened both of those projects and everything seems to working as it should in Standalone (for now). We shall see where this goes!
Sad face 
, still crashing/freezing Studio One. Oh well, back to experimenting.
I’ve had a couple of corrupted projects but they are from earlier versions of S3. However, I still have some problems in Studio One with the plugin being blocklisted randomly, which I think is a timeout, and with one project where reloading it causes a crash to desktop when Studio One tries to load S3
So I’m almost exclusively running S3 as a standalone for now. I take the song so far then just drag all of the MIDI into Studio One.
It’s a bit annoying but I’m sure they’ll sort the problems eventually.
Yes, same here. I can still drop any tracks in an S1 project and continue on with that although it kind of takes away from being DAW integrated but for now, it’s all good.
I am having the same issue with Studio One exactly as you described it. I uninstalled, deleted pref files and tried again. It worked for a little while and then again froze the DAW. Had a busy week but might send a note to Customer Service.
Thanks @VocalMike, yes it’s quite annoying but just a bug of some sort, hopefully they can get to look at it at some point.
Wow - this is still going on? I haven’t had any issues here so far with v3.2 - however I have not really hit it hard yet.
What OS, version of S1 are you guys using?
S
The title says it all - 3.2. on Windows 11
What version of Studio One? And there are 15 different versions of Windows 11 out there…
S
The latest of everything. All up to date.
Not sure what to tell you. Same here and all working just fine.
Something is different - that is for certain.
S
I’m using the latest which is 7.2
Hi everyone, based on our testing and feedback from Studio One users, freezing issues should now be resolved in Scaler 3.2.1.
If you experience any issues after updating, please let us know with as much detail as possible so we can investigate further. Thanks.
Hi Steven.
I see the solution is to install 3.2.1.
I had already done that, this is the version I am working with.
So are you saying, just try a reinstall again?
The issue was happening on prior versions of Scaler and I have been watching this thread quite often (and was trying the beta version as well) and after I had installed the beta, I did not have any of these issues.
So I had installed 3.2.1 final of course and for some reason, the issue had returned.
Anyways, I can try another reinstall and see how it goes.
I have not used it that much over the past week so I am not sure if the problem is still there and I wanted to include those dump files in case there was something significant the developers might have seem.
Thanks for the reply.
Dan
Hi Dan, thanks for the follow-up.
We’ve seen responsiveness in Studio One improve for many users in 3.2.1, but in your case (and for some other users) it may be related to something project- or setup-specific.
Just to clarify: if you’re already on Scaler 3.2.1 and are still seeing the issue, I’m not necessarily suggesting a reinstall, unless you’d like to try a clean install.
Am I correct in understanding that the issue originally occurred when other plugins (e.g. UJAM, SoundPaint, RealGuitar) were involved?
Also, does this happen in a new blank project, or only in existing ones?
(Apologies if this was already mentioned and I missed it.)
Cheers
Hi Steven.
Actually, Scaler 3 is being used on a separate track by itself with no other plugins being used on that track other than the sounds from Scaler 3. So it does not involve anything else on that track in Studio Pro.
But yes, the original issue (from last year, before 3.2.1) seemed to involve using other VSTS but in this case, it is not. (I don’t remember exactly what I was using at the time).
This is a new project, the only other tracks I have in the project are Tonalic tracks.
Thanks.
Dan
Same think here… overall after quite a lot of time since the release scaler 3 is a bit “plug and pray”. Unfortunately I have stopped using it for that reason. If you don’t just use it for very simple things like find a bunch of chords etc. then it’s a matter of time when something will break. I was quite a while optimistic that the issues will be resolved but my conclusion is that unfortunately the complete rewrite of the code base was quite a mistake… I’m just expressing my opinion, as a disappointed user. I expected much more, unfortunately. To the team, please don’t get me wrong I don’t mean this in a bad way. I’ve been a developer all my life too, and okay, sometimes things are so chaotic that there’s just no chance… it has happened to all of us 
I had all sorts of problems with S3 as a plugin in Studio One (now Fender Studio Pro) to the extent that I was using the standalone instead. But most of those problems seem to have dropped away with the recent updates so I’m back to using it as a plugin again.
So it’s getting there. There are some UI things that I really don’t like but they mostly are design decisions rather than bugs so they are unlikely to change and I can put up with them. I’ve not found much that breaks in the latest version but I have raised my eyebrows a few times at some odd functionality or at not being prompted when I am about to overwrite a file etc.
I was a dev too (retired now) so I understand how much work goes into this stuff and how difficult it is to please all of the people all of the time. Maybe for Scaler 4 they can employ someone who understands that there are more than two colours available to them…. 
I’ve got a couple of new songs on the go and I’ve even managed to interest my (classically trained) wife in songwriting. I generated a few backing tracks with just piano chords and a simple bass line and now she’s trying to work out a lead vocal for them. It’s so quick to do!