C14 Shimmer and StudioDelay - CPU massacre

I’m getting about 40-50% CPU Peak usage with any of those two plugins. They must be the worst-optimized plugins in recent years. I have tons of plugins, some much more advanced but none of them are using as much CPU as those two.

It looks like these plugins are not yet fully optimized/finished (just look at the GUI that even I could do :sweat_smile:).

I’m testing it on: Basic Mac Mini M2 OS: Sequoia 15.1. Audio: CoreAudio Mackie Onyx 24 mixer. Buffer 64 samples (tested on 128 too). Asio GUARD Normal.

Empty project with 1 instrument (Retrologue).Buffer size 64. ASIO Guard active (normal). Processing precision 32Bit.

1 Like

steinberg wont do anything the customers want. they do basic stuff. dont hope for good things to happen. you will be disappointed.

4 Likes

Cubase 14 is working really fine in my Windows 10 but it´s true that studiodelay and shimmer are killing Asio guard…

Not here (Windows 11).

1 Like

I was going to type some snotty response to this but I just setup a new project in C14 with Retrologue and then then StudioDelay on that channel… zero CPU usage at all. And then I added Shimmer after the delay and it was fine… until I stopped playing the keyboard … a few seconds later the CPU spiked and took a while to calm back down … with no input signal.

Very strange… when it had a signal to work on … no CPU load.

No signal… maxes out the CPU… took between 5 and 10 whole seconds to calm down. Strange. Sounded really good though while I was playing keyboard.

Win 10 here on a fairly ancient PC by todays standards, and an RME AIO. I’m not getting anywhere near that much of a usage spike - maybe 20-25% max. Not great, but not terribly dire considering my system.

It looks like it’s different from system to system but also these effects react differently to different instruments. After taking away CPU usage of those instruments I’m getting from 20 to 50% CPU Peak usage for effects. No problem with audio tracks tho.
Kinda bizarre experience with these two effects, I never saw such unpredictable CPU usage, probably ever.

I also tried other reverbs like Raum where I set 200s long decay and it barely affected CPU performance. I tried other reverbs with similar outcome.

Then for such basic delay there’s no excuse for a big CPU usage at all.

But I remember how bad was TapDelay at the beginning.

Studio delay is running fine for me.
Here’s a Full project image
Win 10
7900x
Babyface Pro fs 128mb buffer
Load of plugins , automation and plenty of channel tracks opened during prod.
:ok_hand:


I don’t have issues on Windows either. CPU usage is the same as with other reverbs.

BUT the OT is about Mac M2. Which is totally different platform.

Hello battleangel,

I opened a session on my Mac M2 pro and I tested those 2 plugins you were referring to.
You’re right, there’s a difference in performance when compared to both platforms.
But nothing to the extent where they would be unusable.
They are actually very usable.
But yeah meter is higher…
Most probable on the upcoming update it can be addressed.

ASIO-Guard Level is low
Processing Precision 64 bit float
Buffer Size 128 Samples

Oliver

1 Like

Did try it on instrument channels? Like I said, no problem on audio channels, only instrument channels.

  • shimmer seems to have a predelay? audible with reverb at zero, but cannot seem to tweak
  • shimmer intensity adjusts the whole shimmer intensity but it would be really nice to have a way to control the intensity/volume of the pitched signal alone
  • studio delay has a high cpu cost, would be nice to be able to disable the effects to save on cpu maybe, and/ or optimize

Yes, long fixed predelay limits the usage of this plugin. It was the first thing that caught my attention.

1 Like

I have a problem with studio delay. To demonstrate it, I just need to create a clean project, load any waves plugin or fab filter (ex. pro-q) on the master channel, audio or instrument track and load studio delay in the next insert slot. I immediately have an abnormal load of ASIO Guard.

asio bug

2 Likes

I just tried it on the master after Waves C1 and this is the outcome :joy:

My god, it’s so broken it’s unbelievable. It’s a major bug, not just the tiny one. Example video on Streamable
After adding a plugin like Waves C1, it slowly rises until it hits 100% CPU then after a few seconds it drops back t o normal and rises again. When tried with VoxComp, the situation is similar, just shorter.

Yes, on the master channel the realtime ASIO is overloaded, and on the audio or instrument channel the ASIO Guard is overloaded.

If you swap the plugins, the load returns to normal. The problem only appears if any plugin is before the studio delay

“Thou shalt have no other plugins before me!” Or something like that :smile: