Hi guys I fully support the optimization is just a complete bottom! Studio Delay kills asio !!! and any plugin with over sampling enabled will overload the asio like hell! Dear developers please fix the optimization.
MacBook Pro M1Max
I made a test project. Please download and open it. See how the ASIO GUARD scale works for you. You will need a Waves C1 plugin.
studio delay bug.cpr (162.1 KB)
If anyone is experiencing the same problem, post more information about your system:
-Operating System
-Processor
-Video card
-What Asio driver you are using
This will help the dev. team to fix the issue faster 
There’s certainly an issue with stereo delay on Windows 11. This is using an i9 13900k processor.
https://www.awesomescreenshot.com/video/33512040?key=d4b07fdff77a3d6637630907c20d00af
Hi battleangel,
The CPU usage on my Windows 11 Pro PC is incredibly light with those two plugins. I put Shimmer on an Insert with a Piano VST instrument.
My PC is 5 years old and am using the old ASUS Prime Z390.
I took a screenshot of the Audio Performance Monitor whilst the piano and effect was playing back.
Tried StudioDelay on an instrument track yesterday, grandpa i7-6700K told me to love everyone, forgive, and then followed the light.
I can’t offer a repro yet, but I guess I’ll sit down and see if I can narrow it down later in the day.
Sounds really good though.
1 Like
Hope that he is better, now…
1 Like
Just tested StudioDelay as insert. Without being loaded, I have this, on my Audio Performance meter (the test project have few audio tracks, 6 instrument tracks and 5 instrument racks, with 3 external instruments among them, in it) :
After having inserted it on an instrument track, the Audio Performance meter goes from this :
… to this :
And the load is regularly following a kind of sawtooth cycle of about 8 seconds long. At the end of it, the load suddenly drops before increasing again. This, no matter the preset used. Kinda strange and obviously, a fix is needed…
So… Welcome to the club 
Thanks… 
OTOH, I read in a more in depth way this thread and indeed, I can confirm that the issue doesn’t appear if StudioDelay is loaded in the first insert slot. If the case, the load more or less stays as its previous value. Go figure… 
EDIT - Following this, the issue doesn’t appear either, on my end, if StudioDelay is set as an FX track.
2 Likes
not being an arse here but… why would you put a ‘Studio Delay’ on your master?
your master channel loads a single core regardless of DAW, whereas used on a send FX etc it can spread it’s load across the available threads.
I’ve just loaded studio delay and Shimmer in a project on my M1 MBP and it’s not causing any issues at all with ASIO guard. they’re on FX sends as designed.
M
1 Like
It doesn’t matter where it is. The issue is happening also on instrument tracks.
I didn’t came with the idea to put it on the master. Just read my first post and you’ll know where my issue is.
Those two plugins have bugs, already proved.
Why you would defend a software with a bug? What you gain out of it?
This mentality “I have no problem which means that nobody has a problem” is simply useless and doesn’t provide any help.
Besides that, this is how you do a software bug testing.
I wouldn’t, but I certainly could set StudioDelay as an insert : actually, that’s how I tested it at first, without worrying about the fact that there was already another plug-in in the first insert slot of the instrument track involved.
Not sure what you mean with this. I never stumbled on a FX plug-in ‘designed’ to be on a FX/group/bus track. Beside this, I understand that a reverb is often set as so, but am absolutely not sure about a delay one…
Historically ‘Studio FX like delays and reverbs’ were all designed to be on FX sends, that’s how we worked in studios with desks and outboard. ‘reverb, delay Studio FX’ were designed to be run from sends as opposed to things like EQ/Compressors etc which were designed to be run as inserts.
M
I’m not defending …I’m saying in response to the thread I spent some of my valuable time to test this so i could shed some light if possible and foud no issues with either plugin that’s all.
try this: put shimmer and Studio delay on an FX channel each (as they’re 'normaly used) and send from your tracks to the FX channel and tell me if you still have a problem.
M
p.s. I know about software testing I’m a Beta tester…
this is exactly what I’m seeing.
I was losing my mind, having no idea this was a known issue with the new plugins. I have a pretty hefty 12 core machine which ironically shows the CPU of one of the cores only getting to like 15% (the rest between 0 and 3%) while I’m getting completely unusable playback, with, or without ASIO Guard on–even if I raise my buffer to 1024 samples. but I see the same ramp cycle for ASIO Guard in the performance monitor.
playback seems fine when I disable these two plugins. of course this song has a few instances of both plugins, so I’m kind of dead in the water at this point. I hope they fix this soon.
specs: Win 11 - AMD Ryzen 9 3900X - AMD Radeon RX 7600 - 64 GB RAM - Focusrite 18i20 ASIO - all software up to date
That’s not quite true though. If rack effects, such as delays and reverbs, were “designed” to only be on a send bus there wouldn’t be a need for a wet/dry control. It wasn’t at all uncommon to patch a delay or reverb to a single channel or group bus and it still isn’t.
3 Likes
For me it does it in an FX position too.
BUT. I think it’s the Long Reverb setting that does this. If you could try it out and tell me how it goes for you? How I went about it:
-
Added an instrument track a HALion preset. Recorded some 16 bars of accompagnement.
-
Added an FX track with StudioDelay, sent from the HALion comp track at unity gain, post-fader.
-
Added another instrument track.
-
While the first track (HALion comp) was NOT record enabled, Record Enabled the second track and played continuously.
-
Pressed Start, played along with the recording.
-
Stopped the transport, but did NOT stop playing.
- Tested different things by doing steps 5 and 6 continuously, never stopping playing.
=====
With the Long Reverb, some seconds after stopping the transport, the whole sound goes to poopies (never stopped playing). I guess that the moment when this happens probably coincides with when the reverb tail fades out. The same thing does not happen with the Medium and Short settings, or if it does, its impact is negligible, the sound never breaks down as bad.
The setting (for clarity)
Just tried this again on a project with the Long reverb on studio delay and it’s still fine here.
MBP M1 MAX 64GB ram 2TB internal ,Sonoma 14.6.1 , Cubase 14-RME UFX III
I’ll test on my 9950x iin the studio later today.
M
1 Like