Audio Gridder use to solve poor Cubase performance

Hello
I just want to comment that I have experienced recently.
Last November I bought a new Mac Studio M2 Ultra as my main music machine. Currently I’m using Cubase 13 on it.
Recently I have been writing a piece using NI Lores - specifically a patch called The Merchant. I have three instances of this loaded for the piece (the reasons aren’t important really!).
I have been very frustrated with extreme performance loads, cracking and audio drop outs.
In frustration I decided to try the Audio Grinder solution suggested by SoapMak3r. I was reluctant to do so because Cubase/NI/MacStudio M2 should work by itself right?
Sadly it did work and really solved the problem!!!
Please - Steinberg - I have been a faithful Cubase user since the early 90s - can you please address this issue?
All the best,
VolkerB

6 Likes

You should add the tags “Cubase 13” and “issue” to your post, so that it is marked as such.

EDIT: I added the tags for you.

1 Like

yes it works!
Sadly Steinberg doesn´t seem to dimension the problem as every new upgrade needs more CPU.
I would prefer 0 new features but better performance…

2 Likes

That’s the way it goes, it is not just Steinberg, even plain Office stuff requires more resources with every release.

Btw. It is not necessarily the CPU that causes a bottleneck, there are many other pieces that will need upgrades. One of them is RAM, stuff that used to fit into memory five years ago, today needs at least double or even more of that. So you need to anaylze carefully where your bottleneck is.

1 Like

Unfortunately same problem here… and it’s definitely Cubase 13 - the Kontakt 7 Standalone with Lores loaded does not have any issues whatsoever.

ASIO Guard just seems crazy high on my M2 Max and I just don’t understand it tbh. Peak and average meters are around 50%, so, yeah I don’t see why audio crunches to a halt and ASIO Guard hits the limits no matter what I set it to. Changing buffer size (UAD Apollo X) seems to make barely no difference at all either?

2 Likes

I have actually stopped using Audio Gridder now (- executive decision - it created too many workflow issues for me).
Now I just write some and then either render or freeze sections if and when I start getting too many spikes and crackles etc.
(of course I shouldn’t with the high power setup I have! - that was the point of it)
The very strange thing is that initially in my writing session it is all very good but as I keep working back and forward in the music and especially when I open the Key Editor the spiking of CPU/Asio Guard gets very high. And I can add all sorts of other VST tracks, say big Hollywood Strings patch, with very little additional load registering on the meters. So - so far - its really only Lores. Other Kontact 7 instruments seem fine.
I’m waiting for a Cubase update and hoping it improves - otherwise its the old workarounds for hardware limitations. If people keep posting maybe it will get noticed.
Cheers all.

1 Like

Ah it’s only Lores with your setup?
Perhaps this is an issue Native Instruments should attend to then? Well in Kontakt Standalone it works quite fine here - as do other Libraries.
You shouldn’t need workarounds with a specced-up computer on a supposed “Advanced Music Production System”.

1 Like

I’m having the same issue now. Upgraded from C11 > C13 and I’m appalled at the horrendous performance drop. I have a decently god-like PC with an i9H and an rtx 2080 Super, 32GB ram, 2 x 2TB SSDs, Audiobox i2. (basically picture Red Dead Redemption 2/Cyberpunk on Ultra at 100fps without a sweat, or in our terms: ~190 audio/vst/fx tracks, with plugin chains (2-8 inserts) - mostly vocals with fx, (contemporary pop if you will) runs fine in C11. yes, I freeze and render tracks when it gets bloated. In C13 It fixes essentially nothing, example:

On a project that ran fine (great even) in C11, I am getting INSANE ASIO peaks and literally ZERO realtime/disk cache. I have gone through countless sysadmin steps, going so far as to change CPU affinity + change the amount of f*n milliseconds it takes for my computer to ask for an update on the power plan’s status??

WTF is this? I spent $400 to upgrade to a garbage truck with rims. Although, a garbage truck would still get me places…

I have been a dedicated Cubase user for almost 10 years and I’m not only disappointed, I practically want a refund to go buy Ableton or another MODERN DAW that, idk, actually works as intended? Does the literal one job it has?

This is meant to be professional audio production software, but runs like audacity or MuseScore. Steinberg, please never push out a waste of our money just so you can meet a quota again. This is killing your fan base; your company.

I should not have to waste HOURS of my time learning coding to optimize your software, when it is best spent Making Money Making Music With Your Software.

Please help if you’ve got any advice. I’ve scoured countless forums here with the same issue, NO solutions other than to run VEP or AudioGridder smh. Maybe take notes from them, Steinberg?

After typing this I have decided to make my own post, but this is still relevant to this topic.
I hope one day another weary traveler finds solace in this and other frustration/disappointment-fueled posts, leading them to an easy answer I never found <3

2 Likes

Not everyone has that problem, @LuxDafuqs, so we don’t really know what the problem is.

According to Presonus your Audiobox i2 is already considered ‘legacy’. Cubase 11 runs on Windows 10, while Cubase 13 ‘needs’ Windows 11, if I’m not mistaken. So there’s a discrepancy as well.

It’s not always Steinberg’s fault, until you know for sure what the problem is. But it doesn’t seem like you know, yet…

I agree, and you’re absolutely correct! My post was fueled by a crestfallen conflagration, and pointing fingers isn’t helpful on my end. Apologies for the scathing rant, I know the team works hard to make things happen. I appreciate your redirection!

I am highly considering replacing my Audiobox i2 since the buffer size maxes out at 2048. Any idea if this will help? I want to avoid buying another piece of gear if possible, but if it’s the only solution I gotta do what I gotta do!

1 Like

It’s good to see you reflecting on yourself. My sincerest compliments!

I’m sure if you make a new topic for yourself, a lot of people (including me) would be willing to help you, to see what the problem might be!

I appreciate your candor, you’re incredibly kind!

I posted a topic a few days ago (link below), I’d edit out my emotions to leave only objective (and helpful) information, but my fate has been sealed and I’ll have to deal with my early-morning immaturity as I solve this * facepalm * live and learn!:
" [HELP! Audio Dropouts Stutters ASIO Guard peaks in C13 was fine in C11 URGENT!]"

This post is based on a comment I made on a related post, it is a big enough issue that I made my own. Here’s the scoop (I bet you’re having this problem too):

lots of info there on what’s going on - happy to provide anything else if needed - still unsure of root cause but seems like we could be closing in on a solution. Hopefully it helps others encountering this in the future! Thanks again @MaXxive!

To be clear - there are known issues with Cubase as a VST host especially Cubase 12 & 13.

High CPU utilization even at rest / ASIO guard spikes - certain plugins run away with the CPU as can be seen in the performance meter.

Not all plugins cause the issue but even some of the built-in steinberg plugins do cause the issue.

I know the issue was confirmed by Steinberg at some point but it seems to have gone off the grid. I’m not sure if any senior steinberg dev is working on the issue or if its just above everyones head that is currently there.

Personally won’t be buying any Cubase updates until the issue is resolved. Maybe they should consider making their own version of Audiogridder.

I’m with you here. A Cubase version of VEP integrated into the DAW seamlessly would be a game changer!

the problem is though AG/VE pro work beasue they are OUTSIDE the Cubase ‘process’ . As soon as something is inside the Cubase process then you’re back to square one.

AG is free, works fine so just use it if needed.

If you’re a film composer who needs a large template then use VE pro, a mature and sorted program.

M

1 Like

i fundamentally disagree that cubase users should need a 3rd party tool for the program to function as it had in many previous versions

it seems steinberg is ok with this though so that’s prob the final word on it

this is like the steinberg version so shrink-flation - getting less than we have in the past

Je suis tout à fait d’accord avec ton message. Je suis dans la même situation. Nouveau ordinateur très puisant pour la dernière version de cubase pour rien… que de bugs avec… C’est telleent triste :sob:

That’s not how present day computer software works. An application can and often do run multiple processes.

well of course Cubase uses multiple ‘processes’ but it’ s still ‘inside’ the Cubase overall program so dependent on buffering/ASIO guard as to where cubase craps out which can be as low as 20% system use.
Whereas AG/VE pro are separate programs(processes) and that’s why they can leverage CPU /memory not used by Cubase or any other running program.

I’ve already had these dicussions behind the scenes this year with the Steinberg Engine team via official tech support.

:slight_smile:
M