Nuendo 13 users, PAY ATTENTION!
Nuendo 13 is STILL riddled with bugs! A new version is out, but if you’re stuck with Nuendo 13, you’re screwed.
Steinberg won’t release updates for older versions — they FORCE you to upgrade or deal with the bugs FOREVER!
What the hell are we supposed to do about this???
Which bugs are you referring to?
My two cents:
Although i would love if SB (or any software dev) fix all the bugs in an update, i think it is a dilemma for them.An ugly one actually.
They need to introduce new features to be competitive and stay ahead. If they would only focus on bug fixes they make their current users happy.but loose their position abd possibly new users.
That said, i don’t have any show stopping bugs in Nuendo that are fixed in N14. They did introduce ‘changes’ that are highly welcome and i gladly pay for it.
Another thing of note, the update price is small. Compare it to the yearly €500,- support fee from Avid’s PT (who also don’t always fix show stopping bugs, and there are plethora in PT). So you may consider an update, with very nice new tools and workflows (+ bugfixes), to be cheap in comparison.
You are not wrong to ask for bug fixes and perhaps SB should do a small fix update to 13, but I don’t see a big issue (at the moment at least).
I think that you need to at least list the bugs you are referring to.
Better still, report them one at a time with a detailed explanation of how to reproduce them. A developer can only fix what is 100% reproducible . I understand that this can be frustrating for a user because there are definitely issues which crop up ‘intermittently’ and are highly context specific. Its true of every piece of software…
Additionally we have to be careful what we call ‘bugs’. Results/outcomes/behaviors that the user doesn’t expect, or find ideal might not be ‘bugs’. I’m not saying this sort of thing is what your are referring to, but an ill conceived engineering decision on the developers part, does not a bug make!
All that said, the ‘Paid Upgrade’ is about the only model which produces a regular income other than a subscription ( where everyone is on the latest version and fixes are just rolled out incrementally). And the “S” word isn’t popular!
I would hope significant bugs are addressed between major versions. I dont experience any showstoppers though I have a LOT of wishes for enhanced operation 
So again, what bugs are you referring to?
My N13 and 14 have zero bugs in my workflow.
Just an fyi 
Same, and the bug he refers to in another thread is not present in N13.0.51 either, so not sure.
EDIT: Actually, I did have a bug in N13.0.51 where my default CR presets were duplicating themselves, but that’s the only one I can think of; fixed in N14.0.20 as well.
Which bugs? When you say “riddled with bugs” that means a LOT of bugs.
It’s not perfect, but it’s very stable for me. Can you elaborate with details?
I don’t feel screwed at all, but again, please share what’s going on in detail.
Join reality, share your bug reports with details about your system, your OS, your drivers, your plugins, your settings, etc., and explain exactly what you were doing that caused a bug to manifest itself, and maybe someone can help you out.
If it is a rare bug, and you DON’T detail your situation, I can guarantee no one will do it for you.
And clearly, plenty of people are getting along just fine with Nuendo. So clearly, they are not running into the same situation as you.
So if you have a situation that is “riddled” with bugs, maybe take some time detailing what is happening and maybe you’ll get to the bottom of the problem. Perhaps it is indeed Steinberg’s fault. Perhaps it is a driver’s fault. Or a plugin’s fault. Or your computer hardware, etc., etc… have you ever even submitted a crash report to find out what might have caused a crash?
All software has bugs. And no developer can test for every scenario that a user might encounter.
Steinberg is NOT trying to rip you off. Steinberg is NOT trying to force you to do anything. It is in their best interest to release the best software that they can, especially in this very crowded market with intense competition from other developers. Yes, they are human beings who make mistakes like everyone else, so things will slip through.
But it’s not helping much when you post open-ended vague proclamations of tons of bugs and ascribe motives to Steinberg to force you live with bugs forever. That’s nonsensical. If enough people actually experienced that, Steinberg would already be out of business.
I’m not knocking that you might have problems, but I’m suggesting you take the time to be part of the solution.
If you are sincerely trying to resolve your problems, then start with explaining your bugs with lots of details, and someone here will likely try to help. This forum is filled with nice, intelligent people who often try to help each other, not to mention Steinberg staff jump in here too, not to mention Steinberg’s support channels. You have options to help get to the bottom of your situation. Good luck!
Well said
a bug I have is the peak overload bug since Cubase 12, it was there after my Cubase 13 upgrade too, tried cross grading to Nuendo 13 and its still there. has that been fixed?
Tomer_Salman Does have a point though, I buy programs I feel are finished, if people are having issues, they should be addressed, especially since I am not a beta tester. I’m a customer.
there are people who use this type of software for business, and they have to hope for a stable environment too.
the issue I mentioned has left me with enough uncertainty, that the last project I’ve moved past a few tracks was years ago. it just hasn’t been stable enough to be reliable. it was always a fight to get past the peaking and noise and sound drops when it happened. after years of chasing answers on forums, started with the updates to fix it to no avail, and found doing things like turning cores off and such the only answer. I have about 5 plus programs I have been using, and by Nuendo 13 finally getting a fairly reliable Cubase 12. I never had to do it with any other program. not nocking the software at all, I’m still here, still consider it worth it, but we’re buying a tool here. it should at least be stable in the same light as the average DAW would be. doesn’t chase me away, yet seems only fair.
You joined one hour ago? What am I missing here?
What exactly are you talking about? Can you post a link to a topic discussing this bug?
No, it is not and while I use the software every day; I certainly would not want to be locked into a rent-seeking pricing model, whereby I cannot simply just suspend or cancel a membership, without having to be paid up, until the end of a given period, only to then need to restart on a given day in the future and subsequently be charged for part of a cycle that I cannot use because, heaven forbid I wanted to go on a holiday.
Look, i still have a machine that runs Nuendo 11, and it is working every day without a “hickup”.
And that Nuendo 11 pays my bills and makes me profit.
So realy i dont understand your post.
I too, have an instance of N11, running with the old eLc, and it’s working great.
I only just realised the other day, that there are actually horizontal scroll buttons, in the project page because they were never highlighted in that version but yes Steinberg release solid apps and DO not leave iterations or the application stranded, without adequate support.
Maybe I am detecting the possibility that people, while updating their apps, have trouble keeping their OS in check and wonder “why all the bugs”?
No software is bug free. And apps like Nuendo and others in a similar class are very complex, with thousands of users and many different use cases. It’s not practical to expect absence of any bugs.
A ‘finished product’ therefore is one that has passed the full QC suite that checks the core functionality and the most common use cases, and where no show-stopper bugs are remaining, but there are a number of known issues that will be addressed over time.
Most users can expect to use the software successfully. Nothing is guaranteed.
Some users today expect cheap perpetual licenses which they can load on just about any hardware, along with other apps, that will work without major bugs, and where any bugs get fixed without paying for support contracts, or subscriptions. And by the way such support should be 7x24 and prioritize their specific use case, however narrow it may be.
Unfortunately that’s not a sustainable business model. So let go. You get what you pay for.
Ever since the tech industry lured users with ‘freemium’ there’s been a distortion of what people should be able to expect unfortunately.
One way of reducing bugs in an app is to restrict which hardware it runs on, and what supported use cases are. There are still apps in other fields, where you have to buy the software and the hardware together, because that’s exactly what has been tested. They don’t allow installation on random Macs or PCs.
I use some other professional software of similar complexity in another field where the annual support contracts are between $3-$5K. It’s the cost of doing business in some areas. So I don’t really understand this attitude here.
Particularly when you allow plugins. When you allow for 3rd party code to run in your process, you are going to have issues. I would bet that if people were willing to use a DAW, Nuendo or otherwise, with strictly stock effects they would encounter extremely few issues. Of course, that is not very useful so we do want plugins, but we have to accept this is going ot increase problems.
Just to give people an idea of what 24x7 support costs, we have a NetApp appliance with 24x7x365 4-hour support. The device itself was nearly $100k and the support contract is like $8k/year. That also isn’t for special use cases, you are not permitted to load anything on it other than the provided software.
For special use cases, well in general you hire developers. My GF works for a big tech company on an open-source component and the reason they have her and others like her is because they want to get the features/fixes that are important to them and literally the only way to make that happen is to hire someone to do the code.
That’s what you see in all cases for super reliable systems. They restrict what you can use, how you can use it, etc. There’s no loading your own stuff, you use the code they’ve provided and nothing else.
Even then, there can still be issues. Ever been on an airplane on the runway waiting and then suddenly the lights, air, etc all go off for a bit then come back on? Ya they rebooted the plane, or at least part of it. Planes have issues sometimes and “turn it off and on again” is legit a fix used.
It is real, real, hard to make something that has no issues ever. For most things when it is important enough that it “can’t ever have issues” the actual solution is “we have more than one of them so when one does have an issue you don’t notice.”
Since Cubase 10 times, there was always at least one final bug fix release after a new major version was released. For both, Cubase and Nuendo.