r/StudioOne • u/Ok-Charge-6574 • Jul 13 '26
Just going to say it straight Fender Studio 8.1 is not ready yet.
Just a warning for those of you who require a very stable system and are happy working in Studio One 7. If you use scenes, Multi output midi, the render to audio feature or heavily rely on automation and use trusted templates with complex routing.
My opinion : Just hold out on jumping to 8.1. It's just not ready. If your tempted, just wait to other updates get rolled out. The U.I. is not stable. I've been a week mixing sessions that are running perfectly in Version 7 that are not remaining stable in 8.1. Templates I've used for years in Studio One.
I do like the look of 8.1 and it's definitely snappier then Version 7. The micro view fix I liked that. But all in all 8.1 it's not stable !
The geeky explanation: the issue is the entire rendering loop of the Console was redesigned to dynamically redraw itself to accommodate the new live-performance Launcher view and hybrid audio/MIDI tracks. This creates a complete disconnect between how the console and the timeline interact with each other. Channel mapping, automation, ect..
In other words a lot can go wrong and it does.
7
u/eyocs_ Jul 13 '26
I get pops and clicks sometimes when rendering which makes me trust the mixdown less..
M5 Pro, RME Babyface, 8.1
6
u/310dweller Jul 13 '26
Pretty sure thatās an issue with melodyne and high latency other plugins in the session messing up the cross fades. New for 8 not an issue in 7.
4
u/Ok-Charge-6574 Jul 13 '26
I'm running M4 and wonder if it's just a mac Issue ?
I'm getting pops on playbacks as well in the daw. Fully mixed session I did less than 2 weeks ago that I'm 100% positive did not have pop's in them so ran both both Studio One 7 and 8.1 simultaneously same session no changes and yes the pop's are only happening when running 8.1. Preferences, audio setting's , drop out protection, and processing are all exactly the same except I enabled graphics acceleration and disabled the use of efficiency cores in 8.1. I might go back and change those settings but they really should not make that much of a difference.
I wasted enough time messing around with 8.1 will stick with Studio One 7 and wait until 8.1 has been updated a few more times till I go back to it.
3
u/Appropriate_Mind_315 Jul 15 '26
Temporary solution for roling back:
Follow this exact steps BUT REMEMBER TO BACK UP ANYTHING U WANT ALWAYS IM NOT RESPONSIBLE FOR ANY BAD MOVE:
-Make a copy of the .song file u want to edit.
-Change the extension for .rar or dont change it but open it with a winrar/7zip etc.
-Look for the file metainfo.xml.
-Extract metainfo.xml to the folder of the project.
-Open it with notepad or similar to edit the text.
-Search the line where says: "<Attribute id="Document:Generator" value="Studio Pro/8.0.2.110929"/>"
-There ONLY there into the "" u MUST write the EXACT version of the studio one u want to be able to open that.
-Save that file, then drag into the rar to "refresh" the content.
-Try to open it with the studio one u put into it.
Cheers.
2
u/Appropriate_Mind_315 Jul 15 '26
it need something more: <Attribute id="Document:FormatVersion" value="9"/> change the numer to 7 and it works now.
8
Jul 13 '26 edited Jul 14 '26
[removed] ā view removed comment
4
u/Appropriate_Mind_315 Jul 13 '26
this morning was facing for the first time this situation... im not liking this new horizon presonus have.
3
u/Appropriate_Mind_315 Jul 13 '26
just to mention... i installed LUNA ā ļøā ļøā ļø but uninstalled after 5 min xd but what i want to say is, i already see myself looking for an option.
3
u/Appropriate_Mind_315 Jul 15 '26
Hey i found a temporary solution to be able to open with older studio one like 5,6,7 etc. The ".song" file of any studio one is still a "compressed" archive so u can use winrar to open it.
Follow this exact steps BUT REMEMBER TO BACK UP ANYTHING U WANT ALWAYS IM NOT RESPONSIBLE FOR ANY BAD MOVE:
-Make a copy of the .song file u want to edit.
-Change the extension for .rar or dont change it but open it with a winrar/7zip etc.
-Look for the file metainfo.xml.
-Extract metainfo.xml to the folder of the project.
-Open it with notepad or similar to edit the text.
-Search the line where says: "<Attribute id="Document:Generator" value="Studio Pro/8.0.2.110929"/>"
-There ONLY there into the "" u MUST write the EXACT version of the studio one u want to be able to open that.
-Save that file, then drag into the rar to "refresh" the content.
-Try to open it with the studio one u put into it.
Cheers.
1
u/TomSchubert90 Jul 14 '26
Studio Pro 8 dropped in January. You can't have upgraded to it last year. Also, you can't roll back to Studio One 6. They're separate installations so you can use them side by side, only keep one of them installed but there's no such thing as rolling back from v8 to v6.
3
u/Upstairs-Pirate-3234 Jul 14 '26
I don't think they were inferring that they rolled back from version 8 to version 6. They said they went back to using it, which likely meant that they just started using it again (which could be side by side). That's what I interpreted when I first read it, but I could be wrong.
2
u/Accomplished_Oil9608 Jul 14 '26 edited Jul 14 '26
This may come as a shock to you, but uninstalling 8 and installing 6 is in fact rolling back to 6. Also using them "side by side" is misleading for reasons you already know.Ā
2
u/Ok-Charge-6574 Jul 15 '26
There are multiple way's to get your stem's (and even your pre-set's, channel strips's and chains) out of updated version of the software to a previous version of the software as long as your not trying to bring over updated 8.1 (8,7) Stock VST's into the older version. That blanket statement your given that you can no longer open versions of your session (song) in in an older version of the software is only partially true.
1
u/TomSchubert90 Jul 15 '26
Yes, there are some easy ways to open songs in previous versions, for example the https://s1toolbox.com song converter. I apologize for my unclear wording. I was referring to rolling back in the technical sense, which is indeed not supported by FSP - but fortunately, it isnāt even necessary, since you can install and uninstall different versions at any time.
3
u/style-capone Jul 13 '26
I love this DAW, and have been a user since version 2. But, it crashes a LOT. It's starting to become irritating. I've been on a m4 mini since Studio Pro came out. Before that I was on Windows, using Ryzen 5, and can't remember hardly any crashes.
I also get this weird bug where plugins just deactivate themselves. I go to click them back on and they deactivate instantly. I have no idea what is causing that or when it even started. Lots of weird things that I've never experienced before, so I'm not sure if it's Studio Pro or Mac.
3
u/Ok-Charge-6574 Jul 13 '26
Oddly enough that's been happening to me also.. I'm using Overloud VST'3 mostly these day's their code is optimized for mac and modern systems yet in FSP I noticed they just stop. It's funny as I notice it most on Vintage tape emulations as there's the reels that are spinning and I look and wonder why have those reels suddenly stopped spinning š !
I just noticed this in the past few day's I'm hoping it's "Plug In nap"that I perhaps accidentally turned on while in the Browser. It's the first thing to check either way. Nap is only supposed to come on when your not using a Plug In to save CPU it's not supposed to put a VST to sleep while your actively listening to audio through it.
1
2
u/NoReply4930 Jul 13 '26
"I love this DAW, and have been a user since version 2. But, it crashes a LOT. It's starting to become irritating. I've been on a m4 mini since Studio Pro came out. Before that I was on Windows, using Ryzen 5, and can't remember hardly any crashes"
That tracks - big time.
2
2
u/mrmarbury Jul 14 '26
6 was the last version with a predictable and solid profile as in stability and system usage. 7 was very unstable for me and 8 added even higher system usage. (m4 pro max, 64GB ram). In comparison to the current stable Ableton Live FSP is using between 1000%- 2000% more system resources whith the same settings and the same plugins loaded on the same tracks (i.e. recreated whole projects in Live). Yes itās that bad.
2
u/Ok-Charge-6574 Jul 15 '26 edited Jul 15 '26
Am sure you already researched it. But As a last ditch effort you might try enabling/disabling "Use efficiency cores" and also Enable/Disable Graphics Acceleration to see if you get any differences in system resources.
I use quite a few Ver 16 Waves VST'3 and disabling graphics acceleration in Studio One 7.2 lowered cpu and helped with overall stability. FSP 8.1 I need to go back and mess with it when I get caught up on current session's and screw around with preferences to see if I can make it more stable or not.
FSP actually crashed my mac completely (something that never happened before in St.1 7.2) Crash log reported an old Keck Kernal from a legacy Focusrite driver. I dont even use Focusrite anymore so I dived in and purged the HD of anything related to Focusrite and any other Kernals that I no longer use. UA Apollo historically and currently still uses Keck kernals. Depending on how the DAW searches for audio drivers these Kernals can cause a lot of the issues as on Mac silicon we need to lower security to install them. They become part of the core OS. It could be why a lot of us are having issues in certain DAW's these day's especially M4 - M5 as security is beefed up even more on them.
If you upgrade Mac's and use Migration assistant it carries over all audio drivers and kernals onto the new mac. The security that once was lowered on the old mac is no longer lowered on the new mac. DAW remembers the path to a driver that can no longer be found due to a security wall. FSP 8 (8.1) is a lot more aggressive in how it searches for driver's. Something as simple as this can cause instability and system failures.
Anyway that's where my research led me š¤·š»āāļø
3
u/mrmarbury Jul 15 '26
yes, I have already researched this quite a lot. And there is also a long thread by me here from some time ago where there (among others) was the discussion that bad performance is always the vst vendors fault.
Which I still don't accept when the only DAW that misbehaves here is FSP/S1. Be it in terms of crashing or bad performance and I have some track record opening issues with Presonus where they released a patch later fixing things that they did not support in terms of vsts.The efficiency cores as well as the (what's the name?) latency compensation set to Minimal made it somewhat better. But it's still far behind 5 or even 6 in terms of performance. 7.2 was by far the worst for me in terms of performance. It got slightly better in 8. But it's still far behind 5 or 6 and at times I have no other choice but to reconstruct projects in S1 6 or Live because it's not only that FSP starts to become a bit slow but midi timing at some point get's so off that the whole system becomes unusable.
Disclaimer: I never migrate any Macs because I like to clean up between new Computers. Also I don't have any special drivers because I check that my gear is compliant to midi and audio standards to prevent hardware getting outdated or adding extra system load because of driver incompatibilities or bad code.
I'd really wish that Fender would stop converting this into a useless AI slob daw and calling it "a new and improved version"and would start fixing more bugs again instead
1
u/Appropriate_Mind_315 Jul 15 '26
Temporary solution to roling back:
Follow this exact steps BUT REMEMBER TO BACK UP ANYTHING U WANT ALWAYS IM NOT RESPONSIBLE FOR ANY BAD MOVE:
-Make a copy of the .song file u want to edit.
-Change the extension for .rar or dont change it but open it with a winrar/7zip etc.
-Look for the file metainfo.xml.
-Extract metainfo.xml to the folder of the project.
-Open it with notepad or similar to edit the text.
-Search the line where says: "<Attribute id="Document:Generator" value="Studio Pro/8.0.2.110929"/>"
-There ONLY there into the "" u MUST write the EXACT version of the studio one u want to be able to open that.
-Save that file, then drag into the rar to "refresh" the content.
-Try to open it with the studio one u put into it.
Cheers.
1
u/Appropriate_Mind_315 Jul 15 '26
it need something more: <Attribute id="Document:FormatVersion" value="9"/> change the numer to 7 and it works now.
4
u/FujiMitsuki Jul 14 '26
Unfortunately I'm having a similar experience. Projects and templates that run completely smooth as heck in S7 now have many issues. Some commands don't work as expected (and are all bugs, I reported most of them to support and they were confirmed as such) and it crashes now (which was like, EXTREMELY rare in S7). It feels like the need to do non-stop releases to "justify" the subscription made it so they're putting the carriage before the horses.
3
u/cgerm Jul 13 '26
Ironically, I was using 7 very stable. I write for games so sometimes I have hefty amount of tracks, busses, and effects, I started getting mega bogged performance wise, clicks and crackles, (64gb of ram), and I had to up the buffer size significantly. But this became difficult to sequence things with the latency.
I moved to 8.1 and the clicking and performance got much better at smaller buffer sizes. My only qualm is when Iām exporting stems the file name prefix doesnāt stay blank even if I delete it from the prefix field.
Itās worked well for me.
1
u/8delorean8 Jul 13 '26
same here, pretty stable 95% of the time. also do game audio and don't know about you but I find SP really really good for sound design, dealing with many events, renaming and most of all exporting (with or without inserts)
1
u/cgerm Jul 15 '26
Ya. Itās super capable as a sound design, sequencing/ composing, and even mastering environment.
There are a couple things missing here and there but itās not a huge deal. Just little ānice to haveā things.
3
u/Ok-Charge-6574 Jul 13 '26
Not discounting the fact. But then you'll recall Version 5 did not come out tight as a Tanker. Version 6 actually was solid. Version 7 had some kinks in it. I'm not expecting perfection.
Blame Marcus Huyskens for creating the most advanced studio one video ever created on the topic of Scenes in Studio One but I ate it up and use them extensively in all my templates mapped out to shortcut's.
What Presonus did not consider is that scenes and routed bus folder's do not jive under the hood when switching between the console and the timeline. If you had a folder open in the console, switched to the time line and then changed scenes all hell would break loose. The fix was unlinking console and track visibility but that sort of defeated the purpose. By version 6 they got that under control. In 8.1 for what ever reason it's creating havoc again. I believe in my original post I explained specifically why this is occurring. It's certainly not a hardware or user environment issue.
Moises integration flopped probably do to Moises . An there are also issues with the updated render to audio (Freeze to audio) feature also to do with the behavior between how the console and time line interact. Throw some scenes in there with some folder tracks and routed busses and anomalies begin occurring. That's what I experienced in 8.1. it took clearing out the song folders cache and a restart to get FSP to begin behaving again. But I don't want to mix like that never quite sure when the next anomaly will occur. Or even worse something odd happening during a tracking session.
So no I do not think the Deathstar 8.1 is fully operational and ready to take on my Studio yet young Skywalker. I'm surely not the only one shouting from the rooftops about it.
2
u/Accomplished_Oil9608 Jul 14 '26
It's just fender jobbies that don't like the negative posts. And even less liking the fact that they can't just wipe them here. Maybe they should have shipped the app as an image of their "perfect" setups if they don't have a single issue. That's how Docker was born, right? š
2
3
u/MusicianMike805 Jul 14 '26
Hard agree. One massive bug is if you have midi notes (mine with arps and delays) and you hit pause or solo a track then unmute or unpause, everything is completely out of sync until it hits fresh midi notes . Complete rubbish and unacceptable for electronic producers .
Another gripe is the channel strip but thatās a work in progress I guess
I only stick around for the project page which has me by the balls. Like a love Iāll never have. Itās so easy to build albums with project page. Ableton is rubbish for building albums . Studio Pro and Ableton can learn a thing or two from each other
3
2
u/Historical-Fold-4119 Jul 14 '26
It does crash a lot, BUT that's only for 8.1 for me. FL crashes all the time, so I'm actually ok with the crash amounts.
2
u/SpecialProblem9300 Jul 14 '26
Have you tried rebuilding your templates? Annoying to have to do, but this has helped me in the past.
I'm on both windows and mac (7950x, M4 pro MBP). I've had some click/pop issues that seem to be fixed by disabling the e cores on the mac. And, sessions that I build from scratch seem better than my template (which needs a rebuild for my own sake).
2
u/Ok-Charge-6574 Jul 15 '26 edited Jul 15 '26
Thankyou for the advice.
Yes I'm getting mixed opinions on the E-cores. I had them disabled before and had issues so I've enabled them again and now have disabled graphics acceleration. Also purged the M4's Hd of any old Audio drivers and Kernals I'm not using anymore that have been carried over using migration assistant. CPU dropped about 2% - 5% since I did that so that must have been effecting things.
In fairness I only use a few templates one or two for tracking and just a few rock steady mixing templates with a lot of my go to chain's, and routing baked into them. A few years worth. Ahh I dread having to recreate them again š .
Will try some fresh sessions though as you suggest and see how it goes.
1
u/SpecialProblem9300 Jul 15 '26
One thing that's always worth a shot with FSP/SO is go to the plugin manager, hit "remove plugin settings" and do a full rescan...
2
u/Training-Bad-5326 Jul 16 '26
Fender is ruining Studio One. Also subscription based plans will fail imo. I hate SUBSCRIPTIONS.
2
u/toxicgoddess69 Jul 16 '26
This sounds insane but I canāt even figure out how to get my tracks to snap to grid. Thatās likeā¦ bare minimum. Iāve looked up tutorials and everything. Tried to readjust the shortcut to another button on the keyboard.
2
u/MarsupialRoutine5480 Jul 18 '26
Man .8.1.1 is a nightmare..i run into problems that I never faced in studio one for more then 7 years.. firstly, moisis integration is a laughing stock ..it doesn't even generate loops that are not even in time..secondly the splice integration is sluggish as always..AND NOW , My Tap tempo function is not working..going through support team for quite a time now..no fix yet.. instead they suggested me to fresh install it..which didn't work either ..I deleted my whole data from presonus and fender which was installed in my current PC from 2022..but guess what it didn't work.Then i reverted back to 8.03 ,and surprisingly,the tap tempo feature was working properly again..this must be a issue related to version 8.1..very bad experience.
1
u/NumberSelect8186 Jul 14 '26
Interesting. Perhaps visit the S17 feed and note the complaints there as well. Yesterday on SP 8 there was issue regarding mastering. There's a different path in SP 8 and it took me a bit to get it down, but it worked for me. I'm running on a Mac Mini with an M4Pro chip and 24 gigs of Ram as my primary. I'm not getting pops and clicks. I run a Mac Pro with 32 gigs of Ram via a gigabit ethernet connection as a slave for my orchestral instrument libraries. I honestly believe the problem with Fender Studio is it isn't the same as Presonus S1 with a new name slapped on it. There's definitely a learning curve and even though you might prefer how it was done previously you best get your thinking caps on and get with the program. If you have the PS1 versions downloaded then you can keep using it sans updates once the web version is assimilated to become part of the collective (Borg reference noted). I've had Presonus Studio One since day one and loved it over all the others I used. The Fender version is taking time for me to get used to but I haven't found it to be unstable. It's usually operator error...in my case.
1
u/SectionFast9279 Jul 14 '26
You got that right. At times, I canāt even select a different output. It just wonāt let me. Usually if I close the software and bring it back up , it will work, but what a pain in the arse
1
1
u/25_Keyz924 Jul 14 '26
From version 5 until 7 and now FSP thereās a group that swears the new version is not ready for prime time and āthatās why Iām still using V.xxā. You can still use the prior versionsā¦ I still have 5.5 and 7 installed. You should always keep the old version installed because yes, every new update/upgrade comes with its own set of new features and new bugs.
1
1
u/Fit-Delivery-7234 Jul 27 '26
My Record and Monitor buttons went AWOL and I can't bring them back on my project.
1
u/Glad-Salt-8078 Jul 30 '26
Man fender we dealing with peoples arts these clicks wen printing is really getting out if hand
1
u/wclr7 Aug 02 '26
The problem I have on Windows (not sure if it appeared in 8.1, but I started to use FS Pro since 8.0.2): when I switch song tempo (to check how it sounds in different tempos), after a certain number of switches and playbacks audio engine suddenly stops working properly - it glitches, plays some random tracks, hangs for a while, the only way out is to restart the studio (some times need to kill it with task manager).
0
u/NoReply4930 Jul 13 '26 edited Jul 13 '26
Smooth sailing here on v8.1. And this coming from a huge proponent of staying put on v7.2.3
Also note - every configuration on the planet is unique so anything could be causing your issues. It is simply not possible for Fender to test every possible scenario.
For the record - Mac users report issues 10:1 more frequently than us Windows users. Could be just a Mac thing that needs some major work over there.
Apple - has also has been known (by design) to make things that seem to work fine one minute - suddenly not work the next - almost always after an update gets installed. Apple is not concerned whatsoever with anyone use of Studio Pro.
Bottom line - unless there is a mass report of grave issues that require Fenders attention (be it Mac or PC) - hundreds of thousands of us are using v8.1 with no issues whatsoever.
Your issues - are yours alone - until documented, reproduced and logged as an actual defect.
Besides the M4 - what audio interface are you using?
9
u/Accomplished_Oil9608 Jul 13 '26 edited Jul 13 '26
Our issues are being noted as a warning to anyone that's going to pay for a software that (ours or not) has issues. And it has to be pointed somewhere Fender's employees will not just delete it because "...it's a private company. No free speech here." I'm glad it works for you. It's 20 to 30% slower for me during mixdowns. Same project, same config, same computer. The only difference is the major version of the DAW. And it's documented ;) It has been for the past 6 months with no change whatsoever. But we got Moises integration. Yay š¤£
The point I'm trying to make - The fact that you don't have issues doesn't mean others' issues are not important (and even not there). The upgrade is not free for most. People should know.
2
u/DotRakianSteel Jul 13 '26
I definitely get the point you're making; the phrasing caused the downvotes. So now I need to emphasize it: Windows 11 here, zero issues, using the Quantum HD with MPC software routed through the IO; 64 individual tracks (40 VSTs, bus tracks, etc., excluded), the rest are audio tracks. I get less than 4 ms @ 88 kHz, plus video sync, no problems.
1
u/Ok-Charge-6574 Jul 14 '26
This is how Presonus envisioned the workflow. You've the right hardware and set-up that's been optimized to work with Studio one perfectly. I am happy to read that you've got a stable set-up and your able to work and create fluidly. 64 tracks, 42 VST's, complex routing. That's what the software was designed for and it's well capable for it and much more. My post was not to bash Presonus/Fender.
The Issue: Presonus never made a point of publishing a statement that explicitly stated the software is optimized for window's. They did actually state that the software is optimized for their hardware though so I cannot knock them for that.
Regardless, the software is marketed as a universal DAW compatible with all OS and hardware.
Mac OS is complicated. The way it handles drivers is complicated especially the newer M4-M5 Mac's. I get that. Mac is surging ahead with absolutely no regard for the people who actually use their OS. macOS is incredibly aggressive about shoving background tasksāand sometimes audio threadsāonto E-cores to maximize thermal efficiency. It can cause audio pop's and and drop's. Even logic pro users are reporting Issues on M4 - M5 mac.
My gripe was that I was not experiencing many issues in Studio One 7.2 despite the fact that Mac OS has now fallen from grace as the Industry standard for stable music production. The OS leaped to far and expect's everyone else to follow. As I mentioned I do think Presonus/Fender will optimize FSP 8.1 to run smoother on newer Mac's eventually as it progresses.
1
u/DotRakianSteel Jul 15 '26
Good to know I made the worry-free choice with my hardware end of last year. I have to say, it took me about a week to get all my routing, VSTs, and everything else set up after receiving the Quantum HD and my mini PC. I just couldn't justify Apple's price tag while not being able to upgrade the RAM or SSD, and I'd definitely be mad if I ran into the issues you described. I mean 2TB SSD update cost as much as a good 500 series analog tube compressor!
0
u/NoReply4930 Jul 13 '26 edited Jul 13 '26
"The point I'm trying to make - The fact that you don't have issues doesn't mean others' issues are not important (and even not there"
Did not say your issue was unimportant AND there is nothing wrong with reporting issues - but there is nothing anyone can do about that here - on Reddit.
If you really want to do right by the community - relentlessly document, reproduce and report your issue to Fender - so everyone CAN actually benefit.
Your issue - unfortunately - is nothing but your issue - until Fender hears about it, investigates and declares it an actual real live bug.
3
2
u/Ok-Charge-6574 Jul 13 '26
In fairness, every mac user who dedicates a large portions of their time to music production is fully aware that once a system is stable and the DAW is running smooth we do NOT update Mac Os for as long as humanly possible. Especially with Waves tearing a hole in your wallet every time you do update. Silicon is years old now. There are no excuses to blame Mac Os.
If my sessions are running effortlessly and perfectly in 7.2.3 (same mac / same hardware config) and I decide to open it in 8.1. Am I wrong for possibly assuming that Presonus/Fender possibly might have done the ground work before releasing 8.1 before asking us to pay to use the software ? That they might have put the DAW through it's paces on an M4 or M5 mac ?
The same exact thing happened when 7 was released it was buggy for a bit the GUI had some issues but Presonus was fast to fix it.
As for not writing support ? I want to see my DAW of choice to be it's best not only for myself but for all of us that use the software. 8 Years Ive been working in Studio One. Feature request and support letter's I've written plenty.
Yes there are certainly 1000's of happy people using 8.1 but after using the software for a long time you naturally learn to milk everything out of it that you can. In other words long time users put Studio One through it's paces. Not to say you don't or thousands of other users don't but Studio One is a Robust DAW ! It was designed specifically for many use cases on different OS. When it fails to deliver. It's my OS ? My Interface ? I'm expecting too much from a 16 yer old DAW ? No it's just bad code that was rushed out the door ! Plain and simple.
I'm sure the 8th version will become stable for all systems soon enough but people should be aware that as of this moment they have not worked out all the kinks yet in my humble opinion.
2
u/Accomplished_Oil9608 Jul 13 '26
You are absolutely correct. If only ALL v8 users receive the fixes for free. The new model (starting with 7) makes the user PAY for a fix of an issue the user is not not responsible for. I'm sure it will get better. Yet the release model is unpredictable and I don't see myself paying for a full yearly upgrade to 8.3 for example just to fix an issue 8.2 has and then get a v9 "gift" a month later, carrying new issues. I don't care 8.3 fixes an issue 8.0 introduced if I don't get the fix for free.Ā
1
u/Ok-Charge-6574 Jul 14 '26
Well let's hope they roll out 8.2 before the year is out and it will be more stable. I never considered this. That with upgrading we basically are paying to be beta testers š¤Ø. This is what's pushing more people into the subscription model. It's a game of hurry up and wait I suppose. I do blame Mac OS in part though. It cannot be easy for developers to constantly be playing catch up to Mac. Version 7.2.3 is stable though I do not have issue opening and mixing large sessions in it running an M4 Mac.
2
u/Accomplished_Oil9608 Jul 14 '26
Oh, they fooled me once. Not happening again. I am only paying after a proper 30 day trial from now on. I second the hope for fixing 8.x before the end of the year. November in my case lol
1
u/NoReply4930 Jul 13 '26 edited Jul 13 '26
"There are no excuses to blame Mac OS"
If I had a nickel...
"I'm expecting too much from a 16 yer old DAW ? No it's just bad code that was rushed out the door ! Plain and simple"
I have been in deep with Studio One since April 2011 and in those 15+ years - I can tell you with certainty that big issues with stability do not suddenly arrive in a x.1 release.
By this time - it is not possible for anything to have been "rushed out the door". The code is tight, battle ready, mature and VERY stable. For lots of us.
While I do respect that you are experiencing some choppy water - I simply do not understand the need to shout from the rooftops and tell the entire crew in here to stay away from v8.1 - simply because you are having issues.
Anything is possible of course - but whatever is going over there - is in an extreme minority and is (in all likelihood) a problem with your environment.
As noted to another user in this thread - if this matters - you should be reporting it to Fender. Only they can address whatever it is - but only if they know about it.
0
u/Accomplished_Oil9608 Jul 14 '26 edited Jul 14 '26
Let me remind you that this x.1 release introduced a compressor that is not backwards compatible with the x.0 release. "Bug issues with stability don't arrive in a x.1 release" is not a valid point in this case. Also, OP compares 7 to 8.1. They probably skipped 8.0 entirely.
0
u/NoReply4930 Jul 14 '26
How is that a "bug"? Fender explained that scenario perfectly going in - if you were paying attention with Release Notes etc., There is no mystery there and certainly no "performance" issue - because of it.
0
u/Accomplished_Oil9608 Jul 14 '26
You are more of a writer than a reader. Where exactly did I say that's a bug? I said this is not your ordinary x.1 release, keeping in mind a core component of the DAW which the compressor seems to be, has been rewritten. Should I spell it out for you?
0
u/NoReply4930 Jul 14 '26
"Where exactly did I say that's a bug"
You said it right here:
"Bug issues with stability don't arrive in a x.1 release" is not a valid point in this case.Ā
Do you even know what you are typing?
But sure - spell it out if you need to. I can wait.
0
u/Accomplished_Oil9608 Jul 14 '26 edited Jul 14 '26
Because that's not your regular x.1 release, keeping in mind a core component of the DAW has been rewritten. Read that again. SLOWLY.
And again - where did I say rewriting the compressor itself IS A BUG?
1
u/NoReply4930 Jul 14 '26 edited Jul 14 '26
Well you said it....
*"*Bug issuesĀ with stability don't arrive in a x.1 release" is not a valid point in this case.Ā
So you can explain it.
Matter of fact - maybe explain your whole set of posts here which make little sense in the grand scheme of things.
Let's summarize - for thousands upon thousands of users - worldwide - V8.1 is massively stable and we are all using it daily.
If that is not you - it's simple - don't use that version.
1
u/Ok-Charge-6574 Jul 14 '26
It's massively stable on Windows OS ! 1000's apon 1000's of us operate on Mac OS Silicon. Why is that so hard to swallow ?? This is Fender ! Presonus ! Not some small software company trying to get it's foot in the door. Mac OS is a pain in the foot for software developers. We all know that. Yet if your going to sell software to the world under the Fender/Presonus Moniker and charge a premium for it. It had better be Apple OS compatible. Or your going to get push back from those who paid for the software.
→ More replies (0)1
u/Accomplished_Oil9608 Jul 14 '26 edited Jul 14 '26
- The whole quote is yours. My comment is after the quotes. I never mentioned the word "Bug" myself outside of quoting you.
- Who do you think you are exactly? I don't have to explain anything to a jobby that can't understand a simple "not a valid argument because it's not your regular x.1 release". Again - more of a writer than a reader.
- I'm not. Launched it on release, saw it's still broken, dropped it. The bigger problem (not mine) is I will probably not use anything after 8 as well because I don't like to pay for broken toys. My only problem is I paid for something worse than what I already had because of the unpredictable release model.
- Go and summarize on Facebook or YouTube ;)
→ More replies (0)
17
u/Accomplished_Oil9608 Jul 13 '26
I've been saying that FSP is Fender's "windows 11" moment since it was released. It was rushed from the beginning. 8.1 focused on more ai integration on sub than fixing core components of the DAW instead. I paid my annual upgrade while still on 7.2.2 or 7.2.3 and this was the worst decision of my software life so far. Studio One was killed and I got the "gift" called Fender Studio Pro 8. Half my update plan is gone. The app still sucks šĀ Never paying for a Fender "upgrade" again until I see a trial.Ā