I must admit , ive managed to reduce the issue BUT it’s a far from stable Asio for sure , they really need to jump on this
4 Likes
[quote=“Highly-Controversial, post:18, topic:876527, full:true”]
Steinberg do recommend to off antivirus [/quote]
They do? Where? I read all their recommendations for setting up DAWs but I cannot remember having read something like that?
If anyone is using kontakt 7.6.1 be aware there’s currently an issue that causes CPU spikes that they’re aware of.
4 Likes
Not in my case.
These performance issues have been an issue for a long time, and it makes working with certain virtual instruments at a 128 sample buffer unusable. Kontakt, Eastwest Opus, Spitfire sampler etc.
I have compared the performance of the same software instruments in Studio One 5.5, and the performance was totally stable, with a lot less of a performance hit. It was also much more stable at lower sample buffers.
Where Cubase 12/13 is struggling at 128 samples, Studio One 5.5 is stable at 16 samples!
I had really hoped there this would be a priority for Steinberg to optimize stability at lower sample buffers in Cubase 13, but performance seems to be just as bad as in Cubase 12.
7 Likes
Yep, totally agree. Steinberg needs to refocus big time on performance and stability, and releases should not leave RC status and go out into the wild until a much, much higher bar is cleared. It’s ridiculous.
If you can’t make the current features reasonably stable and performant, stop what you’re doing and swarm on the basics. Get it right. So many of us are so very tired chasing down issues and providing solutions that are not our job to provide.
It’s unacceptable. If I wasn’t such a Cubase power user at this point, I would’ve jumped ship long ago, but it’s hard to adjust to other workflows. Not impossible and I’m getting better with Ableton, but I still miss being able to do certain things more easily. I’ve been looking into Studio One and even Bitwig. Just want to get music done at the end of the day.
And yeah, Kontakt 7.6.1 was highly unstable and totally crashed Cubase. I ditched it for 7.6.0. These companies really need to up their testing game and get with the CI/CD standards that other big software houses have mastered. Certain things should just not be getting out the door, but they still are.
7 Likes
You could also try what ive tried , it’s at the bottom of my thread .
Seems to have stabled things quite a bit
NO rant , just facts Cubase 13 Audio engine Spikes compared to Cubase 12 - Cubase - Steinberg Forums
1 Like
Thanks again to everyone who chimed in with tips. I’ve got the latency way, way down and CPU spikes have almost entirely cleared up. Weirdly, C-state disabling seemed to make things worse. Updated my BIOS to latest, didn’t do anything. Then I ripped out all NVIDIA bloatware and used NVCleanstall to enable MSI and tie to closest CPU. Checked CPU core parking, was already set to 100%. Also used Power Settings Explorer to set timing checks to 5000 ms.
I can’t quite tell what contributed the most, but I think it was probably NVCleanStall after setting the Windows Defender exclusions.
What a nightmare, though. All of it. I spent pretty much my whole Sunday digging into the guts of my operating system. This should not be the price we pay to run a DAW on Windows in 2023.
Steinberg (Yamaha?), Microsoft, and NVIDIA need to get their heads together and figure this BS out and create automated tooling to discover the root of the problem with real time audio and fix it.
As it stands, I’m scared to breathe on my computer wrong lest things inexplicably fall apart yet again. None of us should be in this position. The industry needs to change! Not all of us are Hans Zimmer and can afford a top-dollar technical crew to keep his stuff running tip-top.
7 Likes
Maybe time for Yamaha to produce a piece of dedicated hardware on which to run Steinberg software? If it was to be cheaper than Apple’s solutions, I’d buy it.
3 Likes
Ohh, that’s a new one on me , i normally use DDU to remove every single component of Nvdia , will try this as well , glad you are getting there , just think , with all this extra OTT , painstaking 2 days of shear PITA research ,research , research just to update from a previous version , i bet C12 fly’s like nothing on this planet , will try in a bit
Exactly , especially as Steinberg recommend a Nvdia driver base that BREAKS the system apparently more than the lesser windows driver but the windows driver is a minimum
Are we going to see a major amount of input from Steinberg staff today ? I bloody hope so
1 Like
Welp. I spoke too soon. While it’s much better now, this problem is far from solved. Still getting random audio dropouts when opening plugin GUIs, sometimes without the VST meter even spiking.
This is so stupid. My whole Sunday wasted on this. It’ll never end, either. Some software company will just release another update that we’ll dutifully install to get our system to quit nagging us and it’ll screw everything up again in some novel way we can’t see coming.
I hate the software industry.
2 Likes
Do you have any plugins with OverSampling raised ? I found my culprit , i’ll add it to my thread but C13 doesn’t like over sampling on my system
Not exactly, I’m watching the CPU meter like a hawk and am enabling & disabling it on Cherry Audio’s Mercury 6 & 4 to test; doesn’t seem to be causing any problems at all.
But just letting LatencyMon run for a long time, I’m consistently getting storport.sys and wdf01000.sys DPC overruns, along with the occasional NVIDIA related one.
Real time audio is just such a mess. Such a mess. In 2023! It’s really unbelievable. Nothing about my storage system should have any authority to cause audio dropouts for any reason. Full stop.
Again, we are not the ones being paid to solve such problems, and those that are are collectively dropping the ball. I’m sick of it. Time to sleep. Sure got a lot of “music” done today…
Did you install via Nv ? if so it would of installed the gamers driver , not the studio one ?
Max Performance preferred in the Nvidia control center ?
2 Likes
No, installed NVIDIA driver via NVCleanstall. But yes, Maximum Performance Preferred for Cubase.exe.
It’s gotten better and isn’t driving me completely up the wall, just about halfway up the wall now. Progress.
2 Likes
I can confirm that applying Maximum Performance setting for Cubase in Nvidia panel helped to reduced realtime spikes significantly. Thanks for this tip.
1 Like
Would you mind telling us the “workaround” regardless of the amount of high-priority threads showing. I would be interested in what it is and changes. Thanks.
1 Like
This workaround definitely brings back memories of other multicore fixes. I swear, the amount of screwing around inside Windows I’ve had to do over the years to have a semi-stable (emphasis on semi) production environment is bananas.
There is that BUT on the good side of it , you get to learn what could potentially be causing issues and helps for self maintenance , depends on if you are a problem solver or not . But Things like the OS issue at the moment are not good for us that feel the need to have everything perfect . One thing i do like now is saving an Optimised windows of a bootable Usb stick so if oyu do need to do a complete reinstall you don’t have to go through every god damn tweak again like when used too .
Im not Steinberg sticking up for Steinberg , seeing trolls on Reddit saying " Im a beta tester for Steinberg and there is absolutely no bug with Cubase 13 " really does peeed me right of for false representation because if that was a beta tester he’s as thick as a brick .and as blind as a bat . But we are where we are , no-one forced us to update , we knew the risks , ive said my bit on my problems , Steinberg knows what to do to keep us happy otherwise customer base could slowly dwindle
Bit OT but hey
1 Like
Hi @SoundPerf. Sure. There’s more information on this topic in the link below. From there you can download a small tool that lets you increase this limit by modifying your registry. This should not be done without reason. But if you’re hit by this windows limit, this may be a workaround.
2 Likes