You could release Nuendo with Cubase and add the extra stuff later. That way, no one has to wait.
What is the benefit to you if this was the case?
It would mean more work. Since Nuendo v14 contains a bunch of stuff that Cubase v15 does not it would mean that you would now need to test Nuendo v15 two times, first testing Nuendo v15.1, then again a v15.2 with the new Nuendo-exclusive features.
More time to test equals both potentially lost development time and increased costs. We always take the hit for increased costs and lost development.
6 Likes
Exactly my point in case. Steinberg did this once before in the last 5 years.
People who want stability can wait for the .5 release. Nothing changes for them.
People who want new features early can use them as soon as they are released. What’s the benefit of making me wait for the new per-articulation attack compensation feature?
The new features need to be tested for the Cubase release anyway. There’s no need for additional tests.
Lower testing costs and more time for development.
What? Of course there is. Cubase and Nuendo are different applications. The Nuendo 14-specific features will also be in v15 but not in Cubase 15. You cannot only test Cubase 15, shove the new Cubase 15 features into Nuendo 14 and release that as v15.1 without testing!
What if you change a piece of functionality in C15 and a N14-specific function calls on that functionality in C14? In C15 that would be different. No testing?
7 Likes
In this day and age, who likes to wait?
Saying that, whatever the previous version is, notwithstanding the latest version, in this case Cubase 15, that may be considered a stable release, i.e., V14.
There is a reason why the applications are released together, prior to a new or updated version being made available and I can’t see that ever changing.
It was only in the previous cycle that harmonisation of both applications was made possible, and while stability is prioritised using this method, initial features are released in the audio/MIDI version, and post features are always introduced later, which from a business perspective, makes perfect sense.
Curiously that’s a proper third world view on how a normal world should work, the vanity of being able to pay more, showing it… In a normal world one would go about doing its business as usual, and enjoying the added stability and debugging delivered by that testing period. In fact, in a normal world where one’s mind is in the actual work and not on displaying ownership of something, that would be the real benefit of having the premium software.
2 Likes
I’ll be skewered…..but….personally….I’d like new versions of Nuendo to release every 2 years instead of annual. I’d even pay more on that schedule …..yes…..yes….I know….I’m the only one ok with that 
1 Like
It all depends on features, for example I have a license for Nuendo 14 (unactivated), because I am in the process of ensuring that all of my scores are consistent in terms of key signatures, before I migrate to the Dorico based version.
Since version 13 introduced the Visibility inspector for the Key Editor, that particular feature is all I really need at this stage and I am on Windows 10, as well which is what the V13 cycle is optimised for.
2 years and more bugfixes between the versions.