Cubase to Nuendo - how easy is it to?

Cubase to Nuendo - how easy is it to?

I’m not 100% sure what the benefits will be for my work flow, I saw a YouTube video and the guy said Nuendo seem to be more efficient with CPU load for a composer , which I’m obviously excited about if that’s true?

I’m going to do some research before me switching , but I just had a couple of questions some relating to this forum, some relating to moving preferences and settings from Cubase to Nuendo.

If someone from Steinberg or someone who knows could tell me, is Nuendo basically the same code and the same performance as Cubase ? With extra functions added.

Or is it completely different code even the engine for midi, audio automation, etc.?

I have a couple of issues with Cubase and Eucon also HALion7 , if I fought, these would be resolved with Nuendo, I would jump ship immediately, but I always understood it to be the same basic engine with extra features, ??

If I did make the jump to Nuendo would my preference folder from Cubase and my Mediabay .db simple work with Nuendo ?

I’ve had a lot of support on the Cubase side of this forum, and always thought Cubase was the more musical version, so my question is if I move over to Nuendo , would I still be reporting problems or asking questions to the same helpful and supportive people some from Steinberg some other forum uses?

If I’m gonna move over, this is the time as there is an offer on

I have no ideas if Cubase uses read this part of the forum so I have also posted this question there , hope that’s ok
Thanks Andy

Nuendo is everything Cubase plus cutting edge audio post production tools.

  • The underlaying engine is the same.
  • There is a reason Nuendo call itself the house of dialogue.
  • Music related questions are better answered on the cubase forum and postproduction retated ones on the Nuendo forum.

As to the research…This playlist pretty much sum’s up Nuendo’s character.

1 Like

Thanks I will watched this later, I forgot there was a demo 30 day trial. I’ve downloaded it literally copied all my Cubase preferences into Nuedo preference folder and I’m pretty much up and running straight away. Looking forward to seeing if there’s any CPU performances or things that I really need

Not true, VCA mute is unavailable in Nuendo.

60 days, actually.

There is massive CPU and GPU optimizations, but you will have to try it to see, which makes going back not at all tempting, (except in my case, for the Project Browser).

You are right about that…I wonder why the VCA has or lacks mute as its operational tack is different…
Also just for the sake of clarity , I meant the core audio engine and not the overlayed control interface…
this includes temporal, spatial and midi and all processing algorithms etc. as I did not experience any difference worth mentioning.

1 Like

Early days , but i have 2 test projects for which i set up to test my M1 vs M2 and now M3 , I also made these projects to test Cubase 12 when it was released against Logic and move to cubase immediately!

my test projects cover

  1. Crazy midi notes (400+ track all playing tones on notes on bar 1 looped ) with Kontak7
  2. Heavy audio track count all with a reverb inserted

So far I can see any difference at all , more tests later today

Most of these features are in Cubase 13 as well .

Found this which has Nuendo only feature

Of course Nuendo is Cubase +
We have done a few post related tuts with novices and new comers in mind to declutter and demystify Nuendo., the ADR part may interest you and an MPEG- H may soon join the list in a week or two…

1 Like

They use different audio engines, so are therefore different products and until they use the same engine, they have nothing in common other than having similar features as provided by the different engines that they use, along with higher level features that users know and love, otherwise the sample rate limit would be arbitrary.

I don’t think they use different audio engines and I think this has been discussed several times in the past. The sample rate limit probably is arbitrary just like several other feature omissions. Why? Because it’s a way to segment the product lineup. It’s like this for all companies that have more than one version of their DAW.

2 Likes

While nothing can be confirmed either way, it would make no sense to not have a specific feature, i.e., VCA Mute in the supposed flagship or premium product; that would be akin to shooting oneself in the foot.

Nuendo was released well after Cubase so it can be reasonably inferred that Nuendo would use later technology.

In other words, the limitation is in Cubase, not in Nuendo, insofar as the maximum possible sample rate is concerned but equally so, not having what may be seen as a simple feature like VCA mute in the so-called flagship product, is more than likely a result of a limitation in the audio framework that Nuendo uses and unless that changes, the only workaround is what is offered in Cubase.

Well, these companies prioritize different features during development so it is what it is. Steinberg dragged their feet on even including VCAs and then took their sweet time to even get it to the point it is today (unfinished). On the other hand Avid gave users customizable key commands like a year ago or whatever. So, you know… this is how things go.

Not really. If anything it stands to reason that they would reuse code if possible. Having two teams developing two fundamentally different apps would be madness.

But it probably has nothing to do with audio though. All “solo” and “mute” has to do is tell target tracks to do those things. The VCA tracks don’t contain audio so the actual audio engine wouldn’t be directly involved in this. It’s just about sending control signals.

VCAs are also one of the few features that are actually coded differently for Nuendo and Cubase. Most is the same.

1 Like

If it were that simple, then SB would have already implemented a standardized VCA mute across all applications, including WaveLab.

Who is to know what the audio engine(s) can or cannot do.

The fact that competing products do this or that is beside the point, Steinberg DAW and Media Production software do more than just audio.

The point I am making is, Cubase and Nuendo are fundamentally different beasts and no amount of assertion to the contrary can change what is essentially a matter of history.

Hi…I am curious, Because they null on all levels upto @ 192 kHz. And You and I can easily test it by rendering out from both. So I have no idea as to on what grounds you insist on difference
Also Some cubase ver only support 96 kHz. thaT proves nothing.

2 Likes

Essentially, what I am saying is assuming that both DAW’s use the exact same engine is not necessarily a proven fact.

On the contrary, the lack of a clear (or no) statement on this matter by anyone connected to SBHQ lends weight to the notion that the programs do use different audio engines.

Also, there is no reason to assume that Cubase is crippled, in terms of the maximum available sample rate, simply for marketing purposes.

It has been said already that VCA mute, by definition means control by voltage, whereas in software the same outcome may not be achievable in both source engines, in a wholly compatible or compliant way.

You don’t know that though. Just think about the various other issues there have been that are related to mute. Just take muting and unmuting folders for example. I don’t really use mute that way, I certainly never automate it, but apparently a lot of users have relied on have tracks muted in folders and then they’ve accidentally unmuted them prior to export and ended up with problems. That bug, or design choice, was around for a while before it was fixed. So why wouldn’t they just rush out with a fix? Probably because either there were more important things to deal with or because the behavior of mutes interacts in multiple places in the code and there’s a logical decision tree that needs to be figured out and then coded.

I don’t think it’s necessarily as easy as “just have it do this”. But certainly I definitely cannot believe that VCAs would have absolutely anything to do with the audio path directly as far as mute goes. The signal never flows through the VCA so why would it?

Steinberg has commented on this before. They are not “fundamentally different beasts”, they are mostly exactly the same.

1 Like

I think there is a contradiction here and whatever anyone wants to read into past statements, there is still no definitive answer as to why VCA muting is not available as standard between all 3 applications, as previously mentioned.

So far I found in terms of performance. The CPU load is exactly the same on both Cubase and Nuendo , as a bug in 13.0.40 linked with having meters set to wave , which which makes both apps quit when you close the project

So the fact that that is the same in both it seems to me you Nuendo is identical but with extra features .

Some of the features seem stunning, but none of them are things that I work on so I’m gonna be sticking with Cubase for now .

If you ever do make the jump the good thing is, you can copy your Cubase preferences over to Nuendo (pref folder) and when you open Nuendo it’s like you’re working in Cubase, which is amazing

1 Like

There are people who would like to be able to use Cubase, so long as they own Nuendo but when you think about it from a marketing point of view, the economics do not stack up, and Nuendo users would likely no longer have access to ongoing specials for whole numbered releases.