one of the major issues with Windows (10 & 11) is the constant updates from Microsoft on the Edge application and anything (now) for AI (co-pilot, etc). also their apparent move from forever supporting backwards compatibility.
so a couple of things to regularly check - what updates have happened on your machine since you last had everything working? have you re-run the redistributables that your application are dependent on? for 99.9% of the time, re-running my Cakewalk redstributables after an Edge update - fixed. apparently MS is loading some DLLs which interfere with the normal app calls rather than versioning them to preserve backwards compatibility. my Sketchup program occasionally also has to have them re-run - mainly when co-pilot is getting all kinds of new “features” (i’ll never use and try to turn off).
as a note: i’m on Windows 11 running Cakewalk as my main DAW. and it’s stable. i also run SO (free version), ProTools (free), Audacity (free), and a bunch of apps/plugins (which have standalone and plugins) – mainly i’m a fan of using the standalone apps to do the creation work and then bring the output (MIDI/audio) into the DAW project. keeps the DAW project from potentially getting messy while trying things out.
While MS Edge DOES perform roughly two updates per month - exactly none of them have anything to do with updating Redistributables or anything else that operates at the OS level.
If one sticks with the normal “Patch Tuesday” Windows updates (which also have nothing to do with Redistributables) - you should be just fine.
Any oddball behavior with Scaler and Studio One and Win 11 - is unique to this specific combo. Odd man out right now - “could” be Windows 11 - but I am also aware of many Win 11 users on S1 6.6 (but NOT using Scaler) that are not having any issues whatsoever.
Finally - there are 3-4 possible “flavours” of Win 11 out there too - right now - ALL of them have their issues and not all of them will be tested with Studio One 6.6 - it is very important to remember this distinction.
The Windows comments on here are a complete red herring regarding this problem.
Mac users have the problem. Some Mac users have reported the 2.9 Beta has fixed it, some not. Windows 10 users have the problem. All but one or two of those still have the problem with 2.9 Beta.
I’ll share my specs regarding Scaler 2 and Studio One Pro 6.6:
Windows 11 Pro 23H2 (build 22631.3374)
Studio One Professional 6.6.0.99237
Scaler 2.8.1 VST3
I believe that I have the same issues as everyone else: cannot change internal sounds; the hissing noise; lots of UI redraw and event issues (e.g. about box will not display; dragged chords do not repaint properly; Pads and Mod tabs do not display properly; etc.)
Hi All, we’ve feature locked for Scaler 2.9 and devs have done as much as they can with issuing a fix for the S1 6.6 issue. Seems to have worked for most users but I assume something will also come from PreSonus.
If you are keen on getting 2.9 early please access or ask for access to the Scaler 2 Beta Group here.
I am in the Scaler Beta group as well and do not see the v2.9 beta. I upgraded to S1 6.6 on Windows 11 and am hoping the beta would fix the issue as well
It’s very disappointing you are not going to fix this in 2.9 for those of us it still affects. Presonus are showing no signs of making any further changes at their end. They are adamant that they are in the right and are using the latest VST3 SDK. I no longer have any VST2s on my system and I won’t be breaking that rule for Scaler so I’ve rolled back the Studio One version for now.
I don’t know if you have any contacts at UHe but they had the same problem with Hive and have fixed it for all S1 users not just a few. Maybe they’ll tell you how if you ask them nicely (and maybe complement them on CLAP…)
If I want to change to another internal Scaler 2 sound, like String Ensemble, Scaler 2 stays on Felt Piano, no matter which sound I chose. And also the problem that if I drag a chord to the pattern strip, I only can drag one chord, and the graphics are doubled, and that’s it. Running Studio One 6.6. Pro, WIndows 11 Pro.
Wow, a full system rollback of Studio One so you don’t have a single temporary VST 2 on your system?
I use a ton of mixed vsts, can I ask why the hard rule? Maybe I’m missing something.
Thanks
It’s not exactly a full system rollback. I just re-installed a previous version of S1.
VST2’s are deprecated and S1 has the option to disable the VST2 “service” within the software. A couple of years ago I seriously pruned my VST2/VST3 collection to get down to a couple of dozen plugins. It makes me more efficient. Sticking with VST3’s is a logical extension of that.
Davide’s dev team need to address the problem rather than half-fixing it and hoping Presonus will do something. Studio One is not exactly a niche product so Scaler 2 needs to be compatible with it. If that means delaying V2.9 then that is what they should do imho.
Can I please have access to this fix as well - the vst2 (dll) works passabley but is still not quite right but the vst3 is unusable in Windows 11/S1 6.6 - I’d be happy to test. Thanks.
[quote=“jon404, post:58, topic:15917, full:true”] It’s not exactly a full system rollback. I just re-installed a previous version of S1. VST2’s are deprecated and S1 has the option to disable the VST2 “service” within the software. A couple of years ago I seriously pruned my VST2/VST3 collection to get down to a couple of dozen plugins. It makes me more efficient. Sticking with VST3’s is a logical extension of that.
[/quote]
Did the same here - not quite as ruthless as shutting down the VST2 service - I instruct S1 to completely ignore several standard VST2 locations so none of these plugins are scanned or ever appear in S1.
With VST3 being the way forward - several vendors have exposed their truly weak coding methods - the worse of them being Universal Audio.
Instead of actually - you know - doing the work and offering their users “real” VST3 versions of all their plugins - they have crafted a weird “stub” system where they install a set of stub files to the industry standard VST3 location BUT these stubs point to the actual VST2 plugins. So even if you are on a crusade like me to eradicate ALL VST2 plugins in the DAW - these guys make it impossible.
I have just 4 other VST2 plugins that are not yet VST3 - so I now use symbolic links to allow those 4 into the Studio One party.
