@Tristan, It has not gone on the blocklist after those first few times. I didn’t reinstall it. A bigger issue is the S1 crash.
I’m not wasting any more time on it. I’ve deleted the VST3 from my system. For now I’ll just use S3 as standalone or S2 as a plugin and I’ll retest it on the next release. Right now I just don’t trust S3.
Tristan
It would have been good to know to “uninstall/reinstall” v3.1.3 as a potential workaround for this.
The bigger frustration is exactly what you guys are doing over there that would make this an issue in the first place.
One thing I can tell you with respect to Studio One and it’s blocklist process - it is VERY hard to get on this list if a developer is actually following the VERY latest VST SDK spec and coding their plugins correctly.
In all my time using S1 (2011) I think I have seen maybe 3 plugins in total ever end up on the blocklist and the only reasons for this was either they were crap plugins to begin with or the developer got cute and took a number of shortcuts (SDK-wise) when building their plugin.
Starting to look more and more like you guys are not follow the spec and Studio One is getting wise to your shortcomings (codewise)
Here is hoping that whatever is going on with Scaler 3.1.x - it get rectified because being blacklisted in S1 - is a sign of weakness.
S
Add me to the list. I’m on S1 v6.4 and everything was fine until today. I pulled a template I created a couple of months ago that had Scaler 3 as a track. Everything seemed to load fine. I wrote composed a few lines and saved. Did not invoke Scaler 3. After lunch, I come back and on every attempt to load the song I see “Scaler 3 audio blocked”. The main interface loads fine but when I try and load the song, it craps out when it tries reading/loading Scaler 3. I tried rescanning the blacklist. No change.
Finally, I loaded the default blank template and then, with that loaded used the Start Page option to try and load the affected song. That worked and I was able to remove Scaler 3 from the song, save it, close and reload it. I hope this gets resolved soon.
Hi @Lando . Sorry to hear this. Just to be clear, are you saying you are running Scaler v3.1.3 and Studio One has added only the Scaler 3 Audio plugin to the blocklist? Also are you on Windows 10/11?
If Scaler was added to the blocklist, most users have been able to resolve this by resetting the blocklist, then uninstalling Scaler 3, then reinstalling Scaler 3 using the Scaler 3.1.3 installer, then running the Studio One plugin scan again. Could you please let us know if that resolves the blocklist issues for you?
Note we are investigating why Scaler 3 is being added to the blocklist in the first place. This seems to be happening occasionally with either Studio One or Cubase on Windows with Scaler v3.1.2 or 3.1.3.
I have the latest version of Scaler 3 and of Studio One.
I cannot even start up Scaler on a blank page. It automatically crashes - every time.
Any solutions for this?
Thanks!
Your suggestion appears to have worked. I know you’re working to resolve this further, but the question remains. Having made no changes to S1 in over a year, how/why did Scaler 3 suddenly cause problems for a random group of users on various platforms?
Hi @malcolmwebber this doesn’t sound good. Just to be clear, are you saying you have installed Scaler v3.1.3, and now you are unable to load Scaler 3 as a plugin inside Studio One? So you add Scaler 3 to a blank Studio One session and it crashes?
I don’t think there have been any reports of this happening, so if this is the case, first try rebooting your computer, then try a clean install as per the instructions at the bottom of the Known Issues forum page. Reports in this thread seem to be related to opening existing Studio One sessions saved using an older version of Scaler 3.
If you continue to have trouble, please let us know some additional details e.g. your operating system, was everything working prior to installing v3.1.3? When crashes occur, what happens? Does the DAW crash? Do you get an error message? etc.
Hi @Tristan
you say there have been no reports of this happening, yet I have reported that both Scaler 3.1.2 and 3.1.3 crash in numerous ways, all in Studio One, and I have provided event viewer logs and diagnostic crash logs for you.
Just to be clear again, Scaler 3.1.2 and Scaler 3.1.3 are crashing in Studio One:
a) if a Studio One project or song has an instance of Scaler 3 VST2 or VST3 already in that project and we try and open that project, Studio One crashes to the desktop. It can take many attempts of re-opening this Studio One song or project before it may load without crashing.
b) If I drag Scaler 3.1.2 or 3.1.3 onto a new instrument, even starting from a blank Studio One project or song, Studio One will, in most cases crash to the desktop.
I have spent a lot of time trying to diagnose and debug this and have attempted to give you as much information that I can that is causing these crashes. In particular, it seems clear that the crash is strongly related to whatever is involved in first “creating device” when first loading Scaler 3.1.2 and Scaler 3.1.3.
At the time you said no one else had reported this issue and now again you are saying “I don’t think there have been any reports of this happening“ and to answer your most recent reply I have rebooted numerous times, checked and updated Windows 11, checked and updated all drivers (but the only one needing updating was for the GPU - a Nvidia RTX 4060 in my case).
“Reports in this thread seem to be related to opening existing Studio One sessions saved using an older version of Scaler 3“ - no, as mentioned I have reported that dragging Scaler 3.1.3 onto a new instrument in a Studio One song or project that is otherwise blank has resulted in Studio One crashing to the desktop.
Hi @jsljustin . We do appreciate your feedback here and your submitted crash logs are being investigated by the dev team. We are hopeful to have some answers for you ahead of the upcoming 3.2 update.
This latest post however is suggesting they are completely unable to use Scaler 3 in Studio One without crashing occurring which didn’t sound like any prior reports, however this thread has become a little convoluted with a variety of reported issues, so apologies if I was wrong about this.
Your posts seem to generally refer to opening existing projects. How often does Studio One crash when loading the Scaler 3 plugin onto a blank Studio One project? Presumably this is related to your other crash reports in which was the current investigation into your crash logs should provide some insight.
Hi @Tristan
thanks for your reply.
I think that the logs I submitted were related to the instance where I was trying to show a friend how I use Scaler 3 to create chord progressions. So in that instance, I had started with an empty or blank Studio One project and all I did was try and load Scaler 3 VST3 onto a new instrument. This is by definition a blank Studio One project, as it had absolutely nothing else in it except an attempt to load Scaler 3 for the first time. And Studio One hung and then crashed to the desktop.
I can’t recall how many times I tried to redo this, or whether I was even able to get Scaler 3 VST3 to load in a blank Studio One project or not. I think from memory I did end up getting it working, or maybe I just ended up using Scaler 3 standalone. It was a while ago now.
The original crashing that I was reporting was when I tried to open an existing Studio One project that had several instances of Scaler 3 VST3 loaded onto various instrument tracks. At the time that I created the song/project in Studio One, it was using an instance of Scaler 3 that was a version earlier than 3.1.2, but then at the time it was crashing, I had updated Scaler 3 to 3.1.2, and then it crashed, which led me to believe the issue was with Scaler 3.1.2 as the VST3 plugin had been updated, and so loading an older project would have called the current (at that time) version of Scaler 3 - 3.1.2. Hence the title of this thread. But since then, I have updated to Scaler 3.1.3 with both that same existing project crashing and a blank Studio One project crashing as well. Both crashing with 3.1.3 and I even followed instructions on doing a clean uninstall and reinstall of Scaler 3.1.3 with no luck - everything still crashes.
That summarizes my experience to date, but my only solution at the moment is to either use the Scaler 3 standalone, or if I get lucky and can get the Scaler 3 VST3 to work, I do everything I need or want to do with Scaler 3, grab all the midi and then remove Scaler 3 - all instances - from the Studio One project/song. Otherwise the risk is that the project may not open again without uninstalling Scaler 3.
Add me to the list: Scaler 3.1.3 crashing in Studio One 7.2.2 and Scaler 3 Audio.vst3 blocked in Cubase LE 13. 
Scaler 3 often crashes my Studio One as well.
However, what frustrates me the most is that Voicing grouping cannot recognize chord inversions.
This is my question as well. Had 3.1.2 installed for over 3 weeks in August - and then all of a sudden one day - out of the blue - it decides to add itself to the blacklist?
This makes no sense whatsoever.
S
I open Studio One, then try to start Scaler and the whole DAW crashes.
It was working fine until the upgrade. Literally can’t use it now. No error message. Just a complete crash.
I just did a complete CLEAN install and it’s working now. Thanks!
Hi @xpoes. Users seem to be able to resolve the blocklist issue by resetting the blocklist, then uninstalling Scaler 3, then reinstalling Scaler 3 using the latest v3.1.3 installer. Please let us know if this does not resolve the issue for you.
Regarding crashes, when do these crashes occur? Are you able to load Scaler 3 into a blank Studio One project? If you are able to share any Studio One crash logs with us this would b appreciated as the dev team are currently investigating reports of crashes in Studio One on Windows.
I have a zipfile with a Studio One Diagnostic Report for you. A fresh crash with only Scaler 3 as the instrument… Where do you want me to send it to?
Thank you @xpoes I will DM you.
Any luck with it all yet?
I just tried loading a Studio One project song that I really needed to work on tonight, and Studio One Pro 7 crashed to the desktop 4 times in a row. Fortunately I was able to load my Studio One song the 5th time around, and I immediately removed all instances of Scaler 3 so that in future I won’t lose the ability to load my song at all.
Again, I checked the Studio One dump files folder, no dump logs. This is not surprising really, the crashes are not freezes but hard crashes and ungraceful, so I don’t think Studio One has a change to create the dump files as the crashes are hard and aggressive.
I’ve said this before, but Studio One crashes when either trying to create or load device, in this case create the Scaler device.
You may want to install a process monitor on your system. As it monitors activities going on, it might catch what is actually causing the crashes you get. Worth a shot to look at it maybe - Download Process Monitor (ProcMon)