• Hi and welcome to the Studio One & Studio Pro User Forum!

    Please note that this is an independent, user-driven forum and is not endorsed by, affiliated with, or maintained by Fender. Learn more in the Welcome thread!

Fender Studio Pro 8.2.1 - Discussion Thread

Just to even out the field of opinions here. I'm also in the camp of not updating operating systems. My win10 and my win11 machines are locked down tight. There are no updates happening unless I engage them manually. I currently run 23H2 win11 and 22H2 win10. I only update, when it's crystall clear that the OS version is prohibiting an app of importance for me to work. All the talk of security risks leave me unimpressed because in my experience with computers, the number and severity of issues because of updating by far outweigh the issues I had because of not updating ...like a thousandfold probably. "Never touch a running system" comes to mind.. I even have Windows Defender shut down completely and no other third party app to replace it because it just slows down various processes (including the scanning of plugins by FSP startup), that's how much I don't care about security risks. Did not have had anything bad happen for more than a decade.. yes same strategy in win7 and 8. Must be the luckiest man alive. My OS's are stable, run smoothly and are optimized for audio work.
So no need to worry too much madFloyd, there are people out there who are supposedly doing it far worse than you.
Same and on 23h2. 26H2 for the most part is not really any different to 24h2 and 25h2 just extra bloat and more AI crap. Supposed to be a slight improvement for AMD systems from 24h2 onwards after the thread scheduler mess but I wouldn't know. The only reason I updated to 11 was because of the CPU I run and the fact Presonus removed backwards compatibility on older WIN10 versions. Never had a single issue running locked systems from 1998 onwards with solid drivers.

Nothing is 100% bug or issue free when it comes to updates, your either lucky and it works or your not and at the mercy of fixes or more updates. Far to many hardware configs over user systems to put blanket statements out what ever camp your in IMO. That's not a dig at you or anyone else by the way :) For me by the time things are forced like removing backwards compatibility or out dated hardware it's new DAW system time built round the latest build. Constant updates for the most part never improve hardware unless it was bad or very basic on release, some things improve ofc. Audio Driver for example. In these cases updating is a good thing.

I think you have to do what your comfortable with or what makes you feel better about it would be my advice. At the end of the day if software hardware drivers or anything else offer zero performance upgrades then what's the point in updating for anything other than security. Never had issue's with security to be honest but I run stripped out versions of Windows with as much bloat gone as possible.

All that aside. I recently serviced and put 25H2 on my old 9900K system and it works np. That one isn't locked down as much. Just the app bloat removed for the most part as I wanted to try it with minimal tweaks other than the basic BIOS and DAW tweaks for low latency. It's a nice way to check a newish OS out. The one good thing I find about Windows now is you don't need to lock them down as much as the old days. It just depends what level of bloat you want in there and do you really need it.

In short from my old 9900k to 13900k locked systems over the last 10 years I have never had a single issue other than backwards compatibility removal from Presonus or bugs that came with updated software from DAW's and plugins. I jumped to Windows 11 with the 13900k for obvious reasons.

Just my personal findings over the last 10 years or so with Windows DAW builds so take it with a pinch of salt. The good thing is Fender Studio and the former Studio One have always been solid minus the bugs or work arounds that cropped up etc. Nothings perfect.
 
I have a bunch of PCs here, and the majority are pretty modern systems that Windows 11 is absolutely at home on. But I do have one old box that I did change to Linux (just for fun, really) but was happily running Win 11 23H2 on an Asrock mini-ITX 170 mobo, an Intel i5 6500, and 16Gb of DDR3 RAM. It had a TPM module installed to address the security compatibility for Win 11, but it ran very comfortably and could handle a decent load on Studio One Pro 5. I don't think I ever upgraded that box to SOv7, but I've no reason to believe it wouldn't have worked. Sure, there would have been no chance of a 100-track orchestral piece, but not many of us need that! It sits in a corner now, unneeded and unloved, but maybe I'll try SP8 on it one day just for laughs!
 
I've noticed this with a few apps recently. I don't think it's specifically an FSP problem, though it may be contingent on certain software routines.
DaVinci.png
Studio One 7.png
 
I examined the path with my Julian tools and found that the appearance of the <scaler 3[DOT]vst> appearing twice in the path causes the win registry parse to choke once & then flag an exception.
What path are your referring to?

Checked the standard install here and there are no multilevel paths etc - from what I can see - Scaler 3's installer is conforming to all known rules in the VST3 area.

VP
 
Yes, as long as it works you can continue using it.

You’ll find the official statement on top (red text) of their website:

Thank you! I forgot all about the color toolbar back in maybe Studio One 6. I just downloaded it, placed it in the scripts folder, and it's up a running. Good stuff! 🙏🤘
 
Back
Top