SB has not given us a single clean update – i.e., one that does not introduce new bugs – in years. This pattern started circa version 10 (I’ve been using Cubase since version 7.5).
Most of my ‘workflow’ now comprises workarounds from all these new bugs. The forum is full of posts concerning this trend.
Despite this worrying trajectory , I was nonetheless very encouraged after reading the rather long list of bug fixes in 14.0.30, and posted the following (2nd post in this thread):
Having invested a lot of money in SB products, I obviously want them to succeed. However, if they fail to deliver on what they’ve advertised, then it’s their customer’s duty to let them know how we feel.
Hallo, ich suche immer noch, aber vergeblich, nach der Möglichkeit, im Noteneditor per "alt"Taste, merkierte Noten mit der Maus in einen anderen Takt zu kopieren. So wie in CB 13 Pro möglich war.
Vielleicht hat jemand die Möglichkeit im 30ger Update entdeckt. Danke
Hmm, I just tried that, and it worked fine (Cubase Pro 14.0.20).
What I did was to 1) draw in some notes, 2) lasso-select them, 3) alt-left-mouse button drag them to the next bar, and 4) release the mouse button. The notes were successfully duplicated.
I’m running Windows 11 24H2 on an AMD Ryzen 7 8745HS system (Radeon 780M Graphics | 32GB RAM | RME UCX audio interface).
You’ve never worked in ‘real’ IT before or have any clue what actually goes on do you??
Sorry but a single user with ONE instance of an issue, not even remotely close to a ‘bug’ until there is a clearly reproduceable procedure. And even then the ‘bug’ may be with a particular combination of hardware (looking at all you Windows users), and it could be that hardware causing the issue.
The issue with the 2GB files is quite obviously already being looked at by Steinberg.. That means someone has posted up enough info and data they can recreate whatever scenario causes it.
But sorry a handful of people, with single isolated incidents, are not ‘bugs’. If the entire/majority of the forum were seeing this, your point would be valid. Until then, you have NO idea whatsoever, and are just sitting here blowing hot air and wasting space.
You are pulling your hysterical theory out of your rear at this point.
You obviously have not been doing this for very long at all if you’re under the impression every major software rollout should be nothing but roses and champagne.
WTF?!? Why is everyone so rude these days? Couldn’t you make your point using civil discourse instead of resorting to histrionics?
Nobody is threatening your existence. I certainly am not. You’re safe. Take it easy.
There are truly serious problems in the world that warrant your kind of passion. Please identify one and throw yourself into it. Given your considerable fury, the world could be an Eden in just a week.
Can we please all calm down and refrain from creating another post in this thread which is about communication culture?
Kindly move to the Steinberg Lounge if you like to continue your exchange.
This thread is a not a good cross section of data to help you determine a level of confidence as to whether or not you should upgrade. Your situation will be unique – your hardware, plugins, projects, work pressure, clients, etc. – are all unique.
If you are in the middle of a deadline RIGHT NOW, it is always wise to be cautious. There is NO reliable way to 100% predict whether or not any given update - minor or major - will introduce regressions or issues that will ultimately affect your unique situation, without YOUR OWN testing.
HOWEVER, having said that, I find Steinberg updates to be very reliable. Someone else might say the opposite.
My suggestions to you are:
If you are literally in the MIDDLE of a hard deadline and your deadline is imminent, and your project is working fine RIGHT NOW, then I strongly suggest that you WAIT for any update from Steinberg, other plugin developers, and driver developers (and even postpone OS updates TBH). Don’t mess with a working system in the middle of a professional deadline. It’s just common sense, simple as that. Client comes first.
If you have a small break with enough time to potentially troubleshoot, or the client deadline pressure is NOT imminent, then you need to decide the level of pressure YOU have and make a judgment call based on your own personal tolerance for risk. Again, in my case, I find Steinberg updates to be very reliable, and I tend to go for point updates with decent confidence… BUT very important note: I also have several DAWs in the studio, I’ve been doing this for decades, I know my risk factors, so if something weird happens, I can pivot and use another machine if needed. That rarely happens. YMMV. On major releases (as opposed to point updates), I do wait for a while before putting it into production.
If you are CURRENTLY experiencing a bug that is causing you problems, and you see that the release notes of the new update show that the bug is fixed, then that might be a good motivation to install the update sooner rather than later… but again, you have a unique situation and only you can determine the pros and cons and your tolerance for risk.
See suggestion 1.
Use common sense.
Don’t trust vague forum reports of bugs when people complain about issues that they haven’t experienced themselves AND/OR if they haven’t provided a detailed, repeatable recipe to show that the problem is indeed a problem, rather than user error or just a general gripe. The average “noise” level in forums is NOT a reliable barometer… look more closely at the QUALITY of the bug reports and legitimate confirmations… not the vague complaints.
See suggestion 1.
Good luck.
P.S. I already updated and I’m happy. Many thanks to Steinberg. But see suggestion 1 again!
Does the update fixing any of the issues that are necessary or critical for your work? If not then you can easily ignore it. If yes, then you have to think if it’s worth the risk.
For me, this update is not worth the risk. It doesn’t fix any bugs that are occuring on my computer. I may try it at some point because I’m stupid, but just in case I downloaded installation of a previous version from Steinberg’s website. I can only hope that moving back to previous version will not mess up anything (I’m not very optimistic about that). I have also Cubase 13 installed in case of a catastrophy.
There’s no upside in installing a version that doesn’t fix something that matters to you, and there is always a risk you’ll be hit by some regressions.
Cubase 14 may have a new mechanism to show performance, give us more detailed data and I agree with this new functionality. More would be better, in my point of view, this function does not affect the behavior of the meters, because even though they have greater sensitivity in this version 14, they end up consuming more energy and having easier drops than the older versions. Working on this last night, I realized how much easier it reaches the processing limit compared to version 13. Same design, same buffer settings, etc. I think the new specific function is good, as long as it is stable like the other versions. This issue needs to be fixed in the next update.
Yes, that’s exactly what we are doing, fixing a bug that occurred in 14.02 that made the work quite tedious.
I’m very aware that we don’t do updates easily while executing a project from a client.
I am hesitating to update for the above reasons.
Also, if I can’t update due to the nature of my work for the client, I will probably never get a chance to do so.
And if that happens, I will be plagued with annoying bugs for the rest of my life…
However, Sterinberg has a tendency to create very annoying bugs for me since Cubase 13 or so…
I have to be really careful about updating… Oh, God.
As far as I remember, I never had to be so careful with updates until around 12… Where did Sterinberg go wrong?
I wonder if Steinberg finally knows what happened in version 10.5 with Cubase audio system. It’s kinda weird that their regression tests passed such a terrible issue. Comparison of 10.5 with 10 looks awful. So if a user of this forum narrowed it down then it should not be as hard to go through commits which were made after the release of version 10.
