Nuendo 14 fixed Nuendo 13 bugs

Nuendo 13.0.51 had serious bugs:

  1. Graphical errors repeatedly occurred. The cursor no longer displayed the corresponding symbols at the clip end, fades, and clip gain. The only solution: restarting the project several times a day.

  2. ARA extensions. When editing location sound, it is important to align the phase. If you wanted to use additional offline plug-ins in Nuendo 13, you had to repeat the ARA extension after each plug-in change. This was a huge additional time-consuming issue.

Steinberg had been aware of this for a long time. Various updates to Nuendo 13 did not address either bug. Today, Nuendo 14 was released – without these bugs. A relief! However, it left a bitter aftertaste, as you had to pay for the fixes in the form of this update. Steinberg seemed to be capable of fixing the N13-bugs, but didn’t until the release of N14.

Alternatively, you could also use Nuendo 12. These bugs didn’t exist there. On the other hand, 14 has automatic text recognition and a really good improvement to the clip gain curves. Only the display of the selected event in black is really annoying.

So, all in all, a good update. But the handling of bug reports leaves a lot to be desired.

2 Likes

Good to hear! I still use Nuendo 12 daily. I purchased the update for 13 (it’s never very expensive, IMHO), but then I saw a lot of users dealing with many, many issues over the months of it’s (relatively) short lifespan before 14 was released, so I decided to wait. Unlucky number 13, perhaps? Since 12 was doing everything I needed it to do reliably (and still does), I never bothered installing 13. But this time, I jumped into 14 and am looking forward to ‘kicking the tires’ as they say, while still using 12. The biggest reason is for the Softube Console 1 Fader Mk III support, in which only Nuendo 13+ support their Direct DAW Control protocol. I’ll be testing that soon. Cheers!

1 Like

Yes, Steinberg fixed the existing issue where ARA was not updated after modifying some offline processes. However, they solved it at the cost of irreversibly losing the entire offline process chain. Now you can’t change plugin setting anymore.
Is this the right approach?
Martin

1 Like

Yes, that’s the right approach. You correct the phase via ARA with the blank files and then, you can change whatever you want and the phase stays stable.