Something wrong with nuendo 14 suddenly

Nuendo
1

Nuendo 14-Win-11……….

So I have been working on the same project on and off for past month.

Since the latest update the audio is dropping out. The AISO Guard meter is now topping out.

I tried all the tricks, performance adjustments, AISO guard…you name it. I even started rendering tracks to lower plugin count. Nothing works. I’m down to 60 tracks and was at 98 before all this stuff.

And here’s the fun part. When I open the exact same project in Nuendo 12 and 13. It glides through smoothly with the performance meter at just over half.

Not sure what’s going on but thought I’d share it,

Thanks

SYS INFO

OS Name Microsoft Windows 11 Pro for Workstations
Version 10.0.26200 Build 26200
System Manufacturer LENOVO
System Model 30BE00FBUS
System Type x64-based PC
System SKU LENOVO_MT_30BE_BU_Think_FM_ThinkStation P520
Processor Intel(R) Xeon(R) W-2235 CPU @ 3.80GHz, 3792 Mhz, 6 Core(s), 6 Logical Processor(s)
BIOS Version/Date LENOVO S03KT69A, 2025-03-21
SMBIOS Version 3.0
Embedded Controller Version 19.52
BIOS Mode UEFI
BaseBoard Manufacturer LENOVO
BaseBoard Product 1036
BaseBoard Version SDK0Q40104 WIN 3915000367233
Platform Role Workstation
Secure Boot State On
PCR7 Configuration Elevation Required to View
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32

Installed Physical Memory (RAM) 96.0 GB
Total Physical Memory 95.6 GB
Available Physical Memory 80.3 GB
Total Virtual Memory 102 GB
Available Virtual Memory 79.6 GB

1 Like
2

I work on a number of songs almost continuously as I get them to how I want them. They all derive from the same template and have similar track counts and FX etc but one of the songs is always on the point of overload since I moved to N14. The rest are round about the same usage values as in N12 and N13. Can’t find a reason for it but wanted to let you know you are not alone in this conundrum.

1 Like
3

Yeah, thanks I’m back on Nuendo 13 for now.

I even tried rolling back to all the versions of 14 and I also did the same to my Video drivers… and I pulled out any new plugins I purchased in the past month.. no change. I’m not sure if this was a recent Windows update…..But ??? This was not an issue 2 weeks back. Not for me at least.

Hmmmmmmmm?

4

Hi @Withamation

Have seen this a few times when switching from different versions of Cubase/Nuendo to another over. Can you try this: Save your project as a ‘performance test’ and use this as your benchmark:

  1. To avoid auto data copying between versions Temporarily rename any other Nuendo/Cubase Version folder (apart from N14)in: \Users\*username\*AppData\Roaming\Steinberg
  2. Open your test project and switch off ASIO guard and multiprocessing. Change your ASIO latency to something else then back again to previous, close project
  3. Change your power scheme (attached)…(I have found ultimate and maximum performance power schemes to have a (normally hidden) setting which is not optimal under heavy load with ASIO guard and 14700k CPU)
  4. Switch Power Scheme v1.3
  5. Modified Power Scheme Nuendo 14.zip (2.5 KB)

Go back to your project, enable ASIO guard and multiprocessing as usual and test the performance and see if any improvement……

1 Like
5

I can try this for sure, but I’m not really understanding how this will help.

I did previously try different power schemes and I switched AISO drivers also.

My issue was not because of switching between versions. I was working only in Nuendo 14 and it tanked. So I opened the project in Nuendo 13 and it works fine now. No performance/ASIO/disk overloads now.

But if you think this can work I’ll sure give it a shot.

Thanks

6

I see, but if you have time there is no harm in giving it a shot just to rule further things out.

Another thought, is there maybe a 3rd party VST with e.g high oversampling options that could be doing something fishy in N14 but not in N13.

7

Yup true. And I’ll check for that too.
Tkx

8

Have you seen the massive thread about Cubase performance problems wherein various geeky folk use audiogridder to definitively prove that Cubase is using its own, internal core-scheduling workaround, rather than allowing the OS to choose the cores, ala Reaper and others?

When the plugins are wrapped with audiogridder, like magic, it behaves almost identically to Reaper from a performance standpoint–that is, really, really well.

I don’t know if this is your exact situation, but it may be worth a shot to at least figure out what’s going on.

9

Well it does appear to be a plugin (s) and or combination. I have not found the exact culprit as of yet. I have tried all the power scheme combinations and they don’t solve this iiissue.

SO far its only that one project..

10

I have not seen this thread of this audiogridder.
Interesting. hmmmm

11

As am I however, WIndows 10 hasn’t been completely stable with it lately but going to N14, and Windows 11, might help.

12

Here’s one of the main ones… there are a few of them, actually. This has come up quite a bit over the years, and yeah, audiogridder seems to force Cubase to defer to the OS’s core placement algorithm instead of the outdated workaround they’re inexplicably still using: C14 only using 4 cores?

2 Likes
13

Wow! That’s very very interesting.

I have the Audiogridder now, Have not figured out how to use it. I cant even get it to open as a VST plugin in a project at this point.
It shows a midi plug but not audio vst.

I’m still looking for a how to video that I understand on how to set it up. Be cool to see how this works.

Oh… and so far I have found 1 plugin to be giving me grief on the particular project… UVI Plate.

Live and learn right? lol I hope..