the same here. The performance is not bad but Cubase does strange things. My laptop’s processor is at 27% and Cubase ASIO is almost choked. I use ProcessLasso, adjusting the CPU Affinity (taking Cubase out of 0 and 1) also using Throttlestop. everything updated, but I consider the consumption to be excessive. If you use native plugins there would be no problem, but we all know that is not the reality. Let’s hope Steinberg is investigating these types of questions.
1 Like
Hi
Thanks for the input. ASIO guard is on. It has always been on. But after your answer i remembered that another thing happened, even before the actual overload and on the same day.
I tried to connect my Focusrite 2i2 3rd Gen, but when Nuenndo started i realized that i used a charge only USB C cable. This meaning that for all purposes, i ran the DAW without its default ASIO Driver (Focusrite USB Asio). After that i had to ran ASIO configurations all over again. Perhaps this is what actually led to the CPU Overload…
I’m gonna try to uninstall my focusrite, then Nuendo, and after that running all the process from scratch…
Who knows… We might actually be on to something.
I`ll keep the forum posted
1 Like
Not that this solution works for all on windows11pro/Cubendo 13…but…
Process Lasso cleared everything up on one of my laptops so far today anyway. I aimed it at Nuendo 13.0.3 to not use core 0. Haven’t checked Cubase yet.
No spikes at low buffer settings now for my motu ultralite mk5. Asio-guard at normal setting. All ok over the past couple of hours.
I don’t quite have my head around Lasso…it appears to tame a lot of windows stuff in general.
Continuing to monitor what happens.
1 Like
Thanks. I really wish Steinberg would take the lead on, oh, I dunno, engineering around problems like these by invoking their contacts inside Microsoft, Intel, NVIDIA, or whoever else so we don’t need to waste time messing with tools like Process Lasso and such.
But, so far 13.0.30 is at least doing pretty well for me at 1024 samples latency. I’ll take it if I can get some work done. Not what I’d prefer, but I can’t spend my life messing with this all the time as I slowly transition my workflow over to Ableton.
2 Likes
I can totally relate to this. Just upgraded to Mac OS Ventura with Cubase 13 and an RME Interface and it’s driving me nuts.
Plugins like Immerse Virtual Studio or Native Instruments Lores inside of Kontakt 7 just don’t work without spiking and I’m on a i7 8700K system, which should still be enough power.
Not only that, on my brand new M2 MacBook Pro it does the very same thing: random peaks and overall bad performance. Also, a friend works on a Windows machine in Nuendo 13 - same issue.
Compared it to Kontakt Standalone and hosting in Reaper and there were no problems so far.
Still love Cubase and found a way to work around it with Audiogridder but Steinberg really needs to concentrate on living up to the “Advanced Music Production System” it proclaims to be plus it’s hefty price tag compared to other DAWs. Cubase 11 works quite stable though, so there’s another alternative…^^
1 Like
A short update:
After experimenting a bit I found out that Google Chrome running in the background makes the situation worse. So closing all non-needed applications on my Mac solve at least some of the problems.
Still: Cubase 13 seems to handle CPU load quite badly…
Which motherboard on your system 7950x?
Can you tell about Bios setup, Windows 11 config?
My Cubase problem:
I’m on a ASUS P-670. I’m running standard F6 default settings BIOS(latest) , only changes are 105w Eco mode and TB support enabled. latest chipset drivers/RME drivers, etc etc I have 64GB DDR5 6000 ram but as I said running in default BIOS settings.
M
1 Like
Are turbo boost, C-state, SMT turned off?
NO keep all that ON.
Best thing to do is go into BIOS and load ‘optimised defaults’ and then see how your system runs.
You can then start ‘tweaking’ from there if all is well.
M
1 Like
This is all so incredibly annoying.
Intel replaced my i9-13900K with an i9-14900K. Stability overall seems to have improved a bit.
But the spiking is still here.
It seems somehow related to how the OS is distributing stuff to the E-cores. They are clearly overloading in Taskmaster from time to time, even though there is PLENTY of space on other E-cores to do whatever the system thinks would be wise to force onto the one it’s overloading.
I am so annoyed that the professional audio industry can’t solve this issue, or if it’s just a Yamaha and Steinberg thing. This is a very new and very light project so far.
Just crushes the dream, having to constantly be annoyed by these gnats of random spiking. Makes me not want to make music at all sometimes.
1 Like
Hello DrWashington,
Have you tweeked some settings in the Bios?
I use Amd and it runs great but before getting it to run smoothly i had to adjust afew things in the bios and in windows.
C State in the bios better if disabled
On Intel as well in the bios.
Power supply option Idle or typycal current?
Better to run typical current.
Disable virtulization
Security stuff is better disabled.
Speed stepping disabled
Are the P cores disabled?
In windows
Group policy
In windows components
Disable realtime defender
Startup.disabled
Take pictures of all the pages in the bios .
And send them to me.
I’m sure I can assist you and get your system up and running
Thank you, but I’ve been tweaking my system from every angle for over two years now.
This is something that Steinberg needs to address with Microsoft, Intel, and possibly NVIDIA. I’m done pulling levers and pressing buttons.
(Interestingly, disabling C-states led to a very notable increase in spikes. So that definitely doesn’t work on my system.)
Just wanted to inform you, that I just had the issue that two different plugins used together in the same project caused CPU spikes after freezing tracks or doing a mixdown.
Only a restart of Cubase then solved the issue.
By updating the plugins the issue went away (It was an out of date version of Decapitator used together with Sand3 from Acustica). When only one of those plugins was used in the project all was good.
Just to show you that even if you sorted out different plugins as the cause of your problems, in combination they can still f*ck up your preformance.
Took me an entire day to troubleshoot this.
This again brings me to this FR: Solution to crashes by plugins - Sandboxing (Crash protection) - Cubase - Steinberg Forums
I’ve been able to pretty well link this to the GPU: I have found that when scrolling horizontally in the MixConsole, I can pretty reliably get the VST meter to spike (and awful digital audio dropouts even when it’s not visibly spiking/overloading). This is ridiculous, because I have an NVIDIA 4090.
Steinberg… PLEASE OPTIMIZE THIS PROGRAM ALREADY.
It’s still here, it’s still maddening, and no amount of diving into system settings and making stupid little tweaks is making any substantial difference.
I have grown to really start to loathe Cubase for this. Every time I sit down to work, there’s only so much I can take before I realize I’m just not having fun anymore, that making music has become an irritating chore most of the time because of all the irritations building up like like the proverbial papercuts.
This industry is just a mess. The enshittification is among the worst out there. A million DAWs to choose from now and most seem to be unable to handle real time audio on even the most modern processors, especially Cubase. Really such a shame!
And yeah, this is the thing: Steinberg is providing the VST3 framework as a standard. It should not matter what kind of screwups the developer is making. It should be impossible for any one bad, misbehaving plugin to wreck performance for the whole system. Period.
Steinberg is simply ignoring the basics because they’ve decided it’s more important to ship features than focus on performance and stability as true differentiators. I believe this is a massive and potentially fatal mistake for them as a company.
The best thing they can do for themselves is take a step back and put quality as the number one most important consideration, where it belongs. No amount of features are going to persuade me to stick with a program that I can’t get anything done on due to these goddamn spikes out of seemingly nowhere wrecking my concentration and yanking me out of my zone.
It’s no fun anymore. Steinberg have effectively broken me of even wanting to make music due to their unforgivably lax approach to quality.
1 Like
Completely agree.
And I agree even more.
The best DAW is the most stable, performant and efficient one. Period!
Most of the features can be obtained by using 3rd party plugins anyway. Everyone who is seriously involved in this business thinks so. This leads me to the conclusion that we are not really the target group for Steinberg. They probably make most of their money from “newbies” who buy a DAW and only look at the shiny new features? lol
On the other hand I have to say, that since I’ve been a producer and audio engineer (been using Cubase since version 5), I never had bigger performance issues, which couldn’t be sorted out.
It was time consuming to troubleshoot and it gets worse the more programs/plugins are involved. Thats what led me to decrease my toolset drastically, which helped a lot. But in the end I am glad using Cubase.
But yeah, this kind of software has to work perfectly no matter what.
I always thought, if I would create an OS or a DAW Host, which runs other developers software, one of the Nr. 1 priorities would be that my Host runs perfectly no matter what devs I don’t even know throw at me.
Everything else does not make any sense.
That would be like using Windows or OSX and every poorly programmed program would crash your PC instead of just the application itself.
2 Likes
Steinberg. I want you to explain this video: https://www.youtube.com/watch?v=yKs-BXF3U5I
Why is performance in Audiogridder completely outclassing Cubase in this demonstration?
I am really losing my poopies over these persistent performance problems that you seem to be unable to address on your own. Still.
I have found that even scrolling the MixConsole horizontally causes these spikes and dropouts on a lightly loaded project at 1024 samples latency on an RME Fireface UFX. There’s simply no excuse for these performance problems. There just isn’t.
You’ve been hearing over and over that something is wrong from lots of users, but your seeming total inability to address whatever the cause is is astonishing.
1 Like
Agreed. I really don’t understand it. I don’t understand why a company with this much backing can’t seem to figure out how to make any other process that would/could interrupt the real time audio stream wait its turn.
It’s the seeming randomness of these spikes that’s killing me. A very light project can be chugging along just fine with the meters nominal and then POP! Out of nowhere.
I was just running LatencyMon again and it’s pretty much ideal.
I’m losing more faith in “German engineering” all the time. I even drive a German car (MB) and though I generally love it (it just drives really nice), trouble-free it is not. Parts that absolutely should not have failed have failed, to the tune of many thousands.
That’s beside the point, it being that this company, owned by a very stable, storied Japanese company, cannot seem to pull in whatever players from the American companies it needs to ensure that Cubase has the priority it needs at all times to reasonably protect its real time audio stream from interference.
Again, we’re not talking about heavily laden projects here: only four virtual instruments active and a few different reverbs, compressors, etc. But it’s just a nightmarish experience to try and get in a groove and stay there due to this rubbish VST performance.
2 Likes