After updating from 14.0.32, it always crashes after a few minutes…
Timo has advised against installing this update, it is broken.
That they haven’t pulled it down from the website and SDA baffles me, though.
Roll back to .32 for the time being.
1 Like
Unbelievable that it’s still available for download with no warning notice.
1 Like
Not completely reproduced correct. Timos wording is different:
“That said, I officially confirm that there are at least 2 issues in relation to Dolby Atmos projects, which is why at the moment
I strongly recommend not to install the 0.40 update in case you work with Dolby Atmos.”
The thread opener doesn’t mentioned the use of Dolby Atmos.
3 Likes
It would be useful if something like this would be displayed in the News area in the Cubase startup dialog so you don’t have to go digging in the forum. I’ve also experienced those crashes.
1 Like
Well you are right. But to make it only makes matters worse for SB.
If atmos is broken, the update is broken. It should be pulled untill they fix it.
Besides, I don’t work with atmos and I got issues when I installed this update. An otherwise ver stable project got corrupted while idle, which had never happened before.
2 Likes
So….you can ignore all the atmos replies….if you’re not using atmos…. 
Appears your crashes are perhaps due to something else.
If no replies ….what I suggest is walk over to one of your other computers, install Ver .40 there as a test (away from your normal setup, plugins, interface etc etc).
Does it crash?
That’ll be a convenient way to begin a process of narrowing down the issue.
I went back to the previous version. Everything is stable now. I’m not using Atmos — it’s caused by something else. But I don’t have time to keep installing different versions on different computers to check whether they work or not. These are paid programs, and we pay for them to be stable — they’re our tools. Steinberg shouldn’t release “beta” versions, because that just disrupts our work. They should release properly tested builds instead.
Thanks everyone for the feedback. Wishing you all great productions! 
4 Likes
I agree. While less than ideal, I get that you can have unforeseen bugs when introducing new features in whole new versions, cause it’s a lot of different systems and hardware and software interactions to cover.
But a maintenance update breaking things up and introducing bugs is something unacceptable and a telltale sign that there is something wrong with SB’s internal processes.
This shouldn’t happen AT ALL.
4 Likes
Agreed, it maybe has ‘a lot’ to do with the streamlining/combining of this Cubase and Nuendo maintenance releases together?! It is concerning!
Ever? On every single computer configuration on planet earth?
My five Cubendo14.0.4 systems seem fine atm….tips on how to break?
Well obviously in computers where 0.32 was free of the problems .40 showed.
Maintenance updates shouldn’t introduce new bugs man, cmon.
Hey, my philosophy regarding software is what it is….
…if 12,000 of us had cubendo .32 installed with zero issues …and all 12,000 have bumped up to .40……resulting in 63 people having issues in .4 that weren’t apparent in .32…..it simply is NOT from a defective-testing method before release by Steinberg.
Will sb gather & analyze info to potentially reflect in a next update? Of course.
But to blanket state “this shouldn’t have happened”….my response is….get real….11937 users are fine. How-the-heck would any human on the planet KNOW or test for the “63-users” issues…before release…..considering the infinite variations in underlying systems?
A maintenance release of any software for any system by any company in the history of software on planet earth WILL introduce bugs for a percentage of users.
This isn’t earth-shattering info is it?
My opinion of course…which, hey, I’m not changing 
2 Likes
“Nuendo is the premium solution for audio post-production.” (from their website).
Atmos is an essential feature in many post-production workflows. 14.0.4 broke Atmos, seemingly for everyone, implying that this was not tested inhouse at all before release. This is core functionality for Nuendo, not some minor feature. I realise we’re in an era of low expectations from software companies, but we really should expect better than this!
4 Likes
I disagree.
Maintenance releases are not something we are supposed to wait until we are out of work so we can update and test it. It is supposed to come and fix the damned things that were broken in the first place.
There is absolutely no excuse, in my opinion, for a maintenance release taking a stable version and making it unstable and unusable in a system that otherwise had no major changes (definitely none in hardware, and at most a minor windows update).
Not to mention that there are MAJOR issues with .32 that were not addressed, loud freaking pops in the beginning and end of events with ARA on them is the most horrifying example for me.
So not only it is a late, substandard maintenance update, but also a broken one.
Nuendo is expensive and markets itself as “premium”. I’m working here, not making beats as a hobby.
Steinberg needs to up their practices regarding maintenance and bug solving, this is not earth shattering either.
OH! and i forgot to mention: the only, but very important, fix that was relevant to me was the return of the fader to the previous value if a first automation point is deleted, and that was not fixed at all. Seems like a joke.
4 Likes
You do understand that you are paying Steinberg for their product, Steinberg is not paying you chief. Correct?
1 Like
I think the thing to remember here is that the underlying systems seem to not have been the case here, that there indeed was a problem that affected all users. Since that is the case it would seem that if the feature(s) had been tested on any system it would have been found.
Secondly, I think there is something to be said for any DAW having core functionality on a very fundamental level, as well as some types of work having core functionality. In other words when some of us bring up issues with the automation system for example we aren’t talking about something esoteric, we are talking about something that is core to any DAW. Stuff like that should work, no caveats. Because it is core to a DAW. With Atmos it is the second category where people who work with immersive need specific features to just work, and Atmos is clearly a large and key functionality.
Lastly, as annoying as it sounds, there probably are larger things to consider as well. For example; are there features that are more key to how your product is perceived? If there are you probably should give them special attention.
So while I agree with you that no release will be 100% bug free, updates should probably be just improvements, and if there are problems introduced they probably shouldn’t be with major functionality.
2 Likes
The op was a complaint of crashes on .4 that didn’t happen on .32….on his system….and hey, maybe 90 other systems or whatever. If 11890 systems have no similar crash…. it simply remains invalid to me….to me….to state that this “shouldn’t have happened”. There is no guarantee yet even WHAT is going on with op situation culprit-wise.
Atmos…..so some kind of bug got past sb….it seems to appear that sb has confirmed working on a fix. I believe they have a post somewhere around here if I’m not mistaken.
Riding them that it “shouldn’t have happened” is a concept I reject. This stuff will happen….imo.
I thought you were making a general comment. That’s why I replied like that.