@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.