Cubase has a bug that's pissing me off. On a small 24 track project(no plugins in use), Cubase is peaking at 100% and yet the same project opened in Nuendo peaks at 5-7%. Project is 24bit 96KHz and my soundcard buffer is 64 samples.

I've tried everything including enabling/disabling Asio Buffer,
multi-core, power mode, 32bit and 64bit processing. Makes no difference in Cubase.

Funny thing is my Cubase 12 pro is legit and Nuendo is R2R version.

Guess I'll have to try Cubase 12 pro R2R, to see if I'm having the same problem.

 

I use both, nuendo and Cubase from R2R. The peaks are the same!

Btw i figured out if you deactivate vstconnect, the whole thing runs remarkably faster and with less cpu usage. So if you have no use for vstconnect, you could give it a try

 

VST connect is already disabled.

 

Same, this is well know issue with C12

i have legit C11 and it works perfect, glad i can test new versions and decide if it worth an update

 

Running legit 12.0.50 version. easily 100-150 tracks with out spikes... I did notice Kontakt 7 is a biatch that can cause some problems. Not sure if you use that. I would bypass one by one tracks to find out which VST is causing it.

 

I have both legit C11 Pro and C12 Pro.

C11 Pro works really well, C12 Pro - crashes mid project with the same project file as I use in C11 Pro and is unusable. I've given up on C12 Pro.

The spec on my machine is pretty good, so it's not a machine issue (i7, 32GB RAM etc etc)

 

96KHz and small buffer size could be an issue

 

What The F*** thanks for info this is really bad, i thought something wrong with my system (i7 11700k, 16ram)

C12 with 2048 buffersize works okay, may i ask you change your buffersize to 64,32 whatever size and record something, just for test

with my experience you should get cpu spikes (clipping)

 

@Havana IMHO one setting you should pay attention to: Asio Guard.

It's very strange because depending of your gear you have to set it very differently: some have reported that to have the minimum problems they have to set it to "Low", or even set it off (= less overall latency), others have to raise this setting to the maximum to don't have audio interruptions nor CPU spikes...

ATM here it is set to "Low", BUT the "Audio Priority" is set to "Accentize". Another important thing to try: "Treatment precision" to "64bit float" instead of 32bit (you'll have to restart Cubendo for this setting to be effective).

Depending of your hardware and your plugins, all these settings can have mixed effects: you have to find the best combination especially adapted to your current configuration.

For the eternal beginners (like me): to access to these settings, go to the menu "Studio" > "Studio configuration" > on the left column, click on "Audio system" > all these settings are in the right column.

Just my 0.0002€.

EDIT: "64bit float" seems to be prone to crashes ==> avoid, except if you have a very recent CPU...

 

Last edited: Nov 7, 2022

I run R2R C12 on a very old machine, a core2quad (so befor core i), an OCed Q9750@ 4ghz with 8gb DDR2 on Win10 22h2 and it runs very smooth, same as my legit C11. No AVX no hyperthreading. Officially my CPU is not supported, might be that all the newer CPU´s with all there options, cause some issues. I know from a small chat with a steinberg developer that cubase uses AVX when available, but using AVX has quit an impact on the cpu, but different with all CPU´s. Some downclock the whole cpu, some not, some a core etc. And temps can go out of control with AVX. The better optimisations of C12 might also have unwanted effects.
Maybe using throttlestop for watching andfixing CPU speed and or process lasso for not using HT can gain some insight.
It worked wonders on my corei7 laptop where I run VEP for AVX VSTi

 

on the legit cubase 11 i able to disable VST connect se, vst connect pro, and other component . but cubase nuendo 12 R2R gay out those options , wish there is other way to disable those component

 

You can rename the dll´s, there are 2 for vstconnect in the cabase program folder, you can also disable a lot of other components like that, like video if you don´t use it. I rename them to something like VSTconnect.dllno, but anything will do, like deleting one l...

 

thanks a lot...

 

With 512/1024/2048 buffersize -- yes, it may and should work fine. We talk about small buffersize for recording stuff with ~0 delay. So everything you said is just offtop, yes, my C12 works very smooth as yours and what the point? The point is when your buffersize is lower - you fu**ed up. This is why steinberg's forum flamed about C12 performance.

 

@Havana Did you compare the results between C12 and N12? I am interested in this, because some other fellow said he had similar issues, but on a separate machines.

 

no issues here on cubase 3.05 xt on win 3.11

 

No issues here on V12 legit and R2R. Works smoothly. But I don't use 96 KHz but 44,1 KHz 24bit.

I also remember reading somewhere that you should turn off ASIO guard on V12 @Amore_de_la_Vida

 

Yes but Nuendo doesn't seem to have a problem. Aren't they suppose to be running the same audio engine?

Cubase image is on the left and Nuendo on the right. Biiiigggg Difference.

 

Last edited: Nov 7, 2022

Yes it's Cubase 12 and Nuendo 12 on the same machine. I'm running a AMD Ryzen 9 3900X 12-Core Processor 3.79 GHz with 16GB RAM.

 

Yep tried it all, doesn't seem to make a difference. Mind you this project doesn't even have a single plugin yet.

I'm running the same project fully mixed with over 50 plugins in Studio One 6 with same buffer settings and sample rate and my latency is 10ms with 45% max CPU. Cubase needs to fix their bugs. The reason why latency is important to me is because I mix live bands for Livestream.

And the reason why I'd rather use Cubase is because of the excellent DAW Control features.

EDIT: After testing Nuendo, I'm now fully convinced that both Nuendo and Cubase are not optimised for livestream, especially if you need that low latency.

 

Last edited: Nov 8, 2022