Fender Studio Pro 8 Released

[stanft]

Sure. Search my posts here and on Steinberg forum. Check their latest post about Cubase CPUs handling, the audio engine problems and so on.

I was just wondering, as my experience is the complete opposite. Cubase 15 runs super stable and problem-free for me. I haven't had a single crash. I start Cubase in the morning and close it in the evening. Studio Pro, on the other hand, has crashed on several occasions.

I agree with you that Studio Pro is built much, much better from a usability perspective and everything feels cohesive. But I simply can't use it as long as Presonus/Fender don't finally fix the delay compensation. It seems as if the whole system behind it got messed up since the introduction of the dropout protection system. And now there are various problems, all of which have been documented and confirmed by support. But... they are not being fixed. Probably because this requires a major overhaul of the audio engine, too.

[Iernesto77]

I've been using the Cubase 15 trial for almost 60 days and have experienced many annoying bugs: from the cursor disappearing and audio driver disconnections to piano roll notes taking a long time to appear. I was really enjoying Cubase, but I just couldn't stand these bugs. I finally upgraded to Fender Studio Pro, and everything works relatively better. I also much prefer the visual appearance and less menu diving compared to Cubase.

[Crossinger]

I've been using the Cubase 15 trial for almost 60 days and have experienced many annoying bugs:

I hear you. I'm currently on the fence if I should ditch Studio One (7) in favor of Cubase 15 Crossgrade.

No software is without bugs, but my biggest gripe with Studio One is the return of bugs in areas that seemed to be stable (regression bugs). E.g., why the hell do we have bug fixes in ProEq3 again and again since 2024? Hell, it's an equalizer. It should simply do its job and then never touch its source code again.

This usually doesn't happen with Cubase and other competitors. New bugs: yes (of course). But if an area is finally fixed & stable one can trust on it for years to come.

[electro]

Cubase is the #1 DAW where nothing you can imagine is impossible. One clear advantage Studio One has since 7.0 is Ableton Link support.

[Housemus]

Cubase is just an old clickfest that gets in the way instead of our of your way, but FSP and Cubendo share a history and have a lot of resemblance.

[jamcat]

Minus the clickfest

[Iernesto77]

I've been using the Cubase 15 trial for almost 60 days and have experienced many annoying bugs:

I hear you. I'm currently on the fence if I should ditch Studio One (7) in favor of Cubase 15 Crossgrade.

No software is without bugs, but my biggest gripe with Studio One is the return of bugs in areas that seemed to be stable (regression bugs). E.g., why the hell do we have bug fixes in ProEq3 again and again since 2024? Hell, it's an equalizer. It should simply do its job and then never touch its source code again.

This usually doesn't happen with Cubase and other competitors. New bugs: yes (of course). But if an area is finally fixed & stable one can trust on it for years to come.

I agree that no software is without bugs, but I've experienced some truly frustrating ones on my computer. I really wanted to like Cubase and know anything could be possible in this DAW. I'm just making music with Studio One 8 for the time being using it. I should mention that I've only been using it for a few days.

[Resonant- Serpent]

Just check the Cubase forum. A lot of bugs revealed in the lastest update, and at least a dozen that I know of that weren't fixed from previous updates/versions. So disappointing.

[BONES]

Cubase's lack of reliability was the motivation for me to move to Studio One. I was sick of losing work and having to remember to save every two minutes. I've probably been using Studio One for around 5 years now and I have never once lost any work. Yes, it crashes now and then but it's always when I am closing a song, never while I'm working.

why the hell do we have bug fixes in ProEq3 again and again since 2024?

Because it has to run reliably on thousands of unique, individual set-ups and no amount of beta-testing will ever uncover every possible problem every single one of us might encounter. Just because you read about a bug fix in a particular feature doesn't mean it was a problem for everyone, it is most likely something that only a handful users were having issues with. ProEQ is the only EQ I ever use and I've never had the slightest problem with it, for example.

This usually doesn't happen with Cubase and other competitors. New bugs: yes (of course). But if an area is finally fixed & stable one can trust on it for years to come.

What problem(s), specifically, have you been having? I have several but I get that they are things that only seem to apply to the way I use the application - specific plugins and the like - and I understand that if it's not widespread, it may not be addressed. But overall I think they have done a great job over the last few years in making Studio One/Pro much, much more resilient. I had it crash when I closed a song the other day and I reckon it is the first crash like that I've had all year. A year ago I was having similar crashes up to half-a-dozen times every day.

[Crossinger]

What problem(s), specifically, have you been having? I have several but I get that they are things that only seem to apply to the way I use the application

First of all, I'm not talking about crashes. I completely agree with you that Presonus has developed a very stable and reliable product in this regard in recent years. I can actually only remember a single crash with v7 and I'm pretty sure it was the plugin's fault and not the DAW.

No, I'm talking about the subtle inconsistencies that don't work reliably as they should. And these things don't happen all the time, but every now and then, but I can't see any pattern why. Here is a selection of “revenants” that I have, where some of them already appeared in older versions, but were also included in more recent release notes:

• Muted tracks during mixdown: Tracks occasionally become inaudible during mixdown, despite not being muted (requires cancel/re-attempt). This happens randomly since v5 until today.
• Custom Micro Views in the Mixer: under some circumstances, my custom configurations are not saved in the song (generally, they are).
• Fades not working in audio events which are processed with Melodyne. This happened first in v6, and Personus and Celemony fixed it back then. In the meantime, I didn’t use this scenario again, but recently someone on the studiooneforum.com wrote that it’s back.
• ProEq: Especially in v6, it was a construction area (and I was affected by some of the issues). I’m always tracking release notes, and with v8, we have ProEq as a strong contender for bug fixes again.

Perhaps I am biased because I have been working in software testing in the enterprise sector for over 20 years. And as I already wrote: I do not expect 100% bug-free software (there is no such thing). But I have an expectation that once fixed areas will also be secured afterwards (by test automation or other measures) so that the errors do not recur.

You will probably reply: these are all banalities and you don't use them anyway, and you don't care. Fair point! However, this attention to detail is not merely a preference; it is the foundation of trust in professional software. And that's what I currently miss from Presonus/Fender.

[Resonant- Serpent]

The delay compensation issues, especially the ones that affect hardware synth inputs, is my biggest issue with v8. They even broke the Aux inputs, which is how they explain in their own tutorials on how to route hardware synths. I'd have to go all the way back to v6 to fix this, but then I'd still have to deal with the render/buffer pdc issues.

https://studiooneforum.com/threads/be-a ... ails.1916/

[BONES]

You will probably reply: these are all banalities and you don't use them anyway, and you don't care. Fair point! However, this attention to detail is not merely a preference; it is the foundation of trust in professional software. And that's what I currently miss from Presonus/Fender.

I was going to say that I've never experienced any issues with mixdowns, although I used to occasionally experience one where I'd open a song I had been working on and one of the channels would be louder than it should be and once it started to do that, it would always open like that until you lowered the volume manually and re-saved it. But they fixed that years ago. I've never used Melodyne so I'll take your word on that but I've never had any issues with ProEQ and, as I said, it's the only EQ I ever use (although I hardly ever use EQ at all these days).

I'm a terrible beta tester because my tolerance for bugs is very high, probably because my expectations are very low. Things occasionally not working properly doesn't bother me in the slightest. As long as I don't lose work I'm happy to put up with a lot of little niggles. Or maybe it's that I spend 8 hours a day with After Effects, which is mostly a piece of shit, so after that nothing seems nearly as bad.

[Crossinger]

I'm a terrible beta tester because my tolerance for bugs is very high, probably because my expectations are very low. Things occasionally not working properly doesn't bother me in the slightest. As long as I don't lose work I'm happy to put up with a lot of little niggles. Or maybe it's that I spend 8 hours a day with After Effects, which is mostly a piece of shit, so after that nothing seems nearly as bad.

Your approach is probably way healthier than mine. „Attention to detail“ is my occupational disease. But I guess you are right: sometimes it’s better to see the big picture and forgive the minor glitches.

[BONES]

Yeah, but I'm not like that with everything. My OCD is triggered very badly in a lot of situations - if something is one pixel off properly centred in a graphic I am working on, it will drive me nuts. I suppose it's what I am often banging on about here - the process doesn't matter, it's all about the result - so as long as I can get the work done, I'm not overly worried about the little issues that inevitably pop up.

[dastewart]

I did "evaluate" Cubase at the start of the year since I was getting fed up with certain aspects of Studio One (yes, I'm still on v6 so that's what it's called) but hit a showstopper pretty early on with the fact that you can't replicate Studio One's concept of having a bus for a folder.

With my years on Studio One I've got into the habit of having nested folders, e.g. "kick out" going to "kick" folder going to "drum" folder, or LH grunge guitar going to "grunge gtr" folder, going to "rhythm gtrs" going to "electrics" folder and just having the routing all working for me via the buses in the folder.

Cubase doesn't have that combined folder/bus concept and when I asked about it on the Cubase users forum I couldn't even get my point across at how useful this kind of thing is. I guess you don't miss what you've never had.

I decided that was enough of a showstopper to stop evaluating Cubase but I did have it long enough to know that the Studio One render bug (it moves things by 1 sample which can kind of screw things up when you mixdown stuff) isn't replicated in Cubase. Or Reaper for that matter.

And this bug/feature still exists in Fender Pro v8 - I asked people to check.