Thank you. By the way: ASIO Guard on high, buffer size 256, 96k sample rate. Fireface 400.
Also trying ASIO guard on medium, it’s marginally better but the sound still breaks down.
Thank you. By the way: ASIO Guard on high, buffer size 256, 96k sample rate. Fireface 400.
Also trying ASIO guard on medium, it’s marginally better but the sound still breaks down.
Confirmed here, with two instances of HALion Sonic 7.1 on the two different instrument tracks. And it seems that the overall audio performance load after your 6 steps is even worse than previously :
FWIW : ASIO Guard set to Low / Buffer size : 128 samples /44.1 kHz / RME Fireface UCX (USB 2).
EDIT - I even get some processing overloads (red led), which wasn’t the case in my previous tests…
In my case, after waiting for everything to settle down, I find myself in a situation where all gauges (Realtime, ASIO Guard and Peak) show nothing (they are zero) but the big red light is pegged, and it won’t let go. It takes some more seconds until it allows to be reset, at which point the gauges start showing the real numbers for the idle project.
By the way, I’ve also noticed that the Imager of the Vocal Strip plug-in also seems to be very expensive on the CPU (again driven from an instrument track).
So, for this recent project it’s a combo that grinds my poor 6700k to dust.
In my case, it has never settled down. A screenshot taken more than one hour after the test :
Things are indeed getting complicated, in this case, even with my more recent Ryzen 7 3700X based setup…
Same issue here. I have a StudioDelay on a group bus.
Only two situations: Studio delay is off:
Studio delay is on:
These are the settings of the plugin:
I am using:
Cubase Pro 14.0.5 (Just to be complete)
Memory: 16Gb
CPU: Intel i7-8700@3.2GHz
It looks like this bug is fixed now with the .10 update. I tried only Shimmer and only on Mac. It still uses way more CPU than any other reverb I have, but it’s usable now. Not sure about StudioDelay with various configs. I’m after 8 hours of bug-fixing audio at work so I’m not gonna do QA for Cubase today
I can confirm it also. Fixed!
I’ve done a quick test to see what the CPU usage is like versus a comparable delay like Soundtoys EchoBoy. I loaded up 40 instrument tracks with a Cubase Studio Delay plugin on each one. The ASIO guard level on the performance meter was around 50%. The real time was about 4%.
I then repeated the test with EchoBoy with the closest settings I could. The ASIO guard level was around 15% and the real time was around 3%.
So quite a hefty performance difference, I was hoping to start using more stock plug-ins but only if the CPU usage is comparable.
Testing was on Win 11, Cubase 14.0.10 with an RME UFX+ interface, buffer at 256.
Yep. I also would like to use as many native plugins as possible so that in the future, I have less stuff to install when opening ancient projects. But CPU usage is way too high for those to replace third-party plugins. If those would have some extraordinary sound then I could understand and accept that in a few years, it will use 1% CPU max like it happened to all once CPU-hungry plugins of the past. But that’s not the case here.
It started with MultiTap Delay, which was once very CPU-heavy but has become much more acceptable (yet not great) performance-wise after a few updates. Now, StudioDelay and Shimmer continue that trend.