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):

Recently 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?? Not to mention Process Lasso’ing and LatencyMon’ing my days away to literally no avail. With this data all being true, I come back to my first inkling: Could it possibly be my interface? Have I just outgrown the ol’ i2? Anyway, happy to provide the details on PL & LM if needed. Wdf01000 is my worst nightmare. nvidia drivers disabled… god I’ve done so much stuff I shouldn’t have to.

WTF is this? I spent $400 to upgrade to a garbage truck with rims. (Right before they put their entire library on sale! LOL!) 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 and money 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, guys? I really shouldn’t have to host plugins/instruments outside my daw, it’s 2024 and my laptop could eat air traffic control for breakfast.

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

1 Like

Hi,

Try to increase the Buffer Size, please.

Could you test your system by using LatencyMon utility, please?

Thank you for your response Martin,

I have tested all buffer sizes from minimum-2048 (max on my interface) LatencyMon was mentioned and I am getting the typical generic “you should try changing your throttle settings!” (Which I have done by the way lol)

I have tested all ASIO Guard settings, and tried on/off as well.

Steinberg audio power scheme enabled

LatencyMon has led me to clean up my Nvidia drivers and disable ones I don’t use (high definition audio driver for TVs etc). I have also forced all my USB drivers to never turn off eliminating that issue. I even have an SSD bypassing mandatory security checks that save data in the event of a power outage to save latency…

LatencyMon’s biggest culprit is a mostly specific DSP system interrupt, Wdf01000 I believe it’s called. Waaaaaaay over the appropriate amount of interrupts per second. Exponentially.

Windows defender is off replaced by “bitdefender” which has exceptions in place for all my samples and daw folders. As well as my plugins and Cubase13.exe itself.

Let me know if there’s anything else I can provide!

Hi,

Did you change it properly, please?

As you own Nvidia, please try this:

  • Download the latest Studio driver version from here. If there is no Studio driver for your graphic card, use the one, which is available and continue with the same steps below.
  • Disconnect the computer from the Internet to ensure Windows will not download and install its graphic driver.
  • Uninstall the NVIDIA driver.
  • Restart the computer.
  • Start the NVIDIA driver installation (as administrator).
  • Don’t install the whole package, use the Custom (Advanced) settings.
  • Disable everything (don’t install NVIDIA Experience, PhysX, etc.), and keep the video driver enabled.
  • Connect your computer to the internet.

I used NVClenstall to do a clean install of the latest Studio Driver the other day, but I did add the PhysX etc for gaming - so I’ll try this method instead today - fingers crossed! Thank you for the tip!

Hi,

I wouldn’t use 3rd party tools for this.