Cubase 12 Upgrade ASIO-Guard Issue

Try different plugins just to be safe. Not sure about the Wavestate but the Opsix was released with pretty terrible CPU optimization as it is (at least on the Mac side of things). That one is brick walling every DAW until Korg gets it together…

@Chriss - FWIW, here’s mine: Intel(R) Core™ i5-4570 CPU @ 3.20GHz 3.20 GHz

Thank you!

1 Like

Same problems here. Tried all suggestions above. Windows 10 full up to date i7 32gb ram. With only one track open getting clips. No problems in cb11.

Also weirdly loaded cb 12 pro onto an old laptop from 2006 dell inspiron 1525 with only 4gb ram works perfectly no spikes ? Had the 79 track demos working perfectly.

Edit…disabling c states in bios definitely helped, but still getting massive spikes that were not in version 11 on same songs.

2 Likes

Hi Chriss,
Thank you again for your continued assistance. Your help here sorting and working through the issues has been invaluable! Also, a big thank you to all the users for continuing to share their experiences in a constructive, informative manner!

I’ve had an opportunity to run some tests based on the information you provided (sorry for the delay) Here are the results:
Buffer 128 - AG Low, Normal or High. All OK. No dropouts
Buffer 256 - AG Low = dropouts. AG Normal, High both OK.
Buffer 512 - AG Low, Normal = dropouts. AG High is OK
Buffer 1024 - AG Low, Normal, High all = dropout/clicks.

I performed the test using the Demo track “Cubase 12 - Pop Demo By Austin Hull.cpr_MIXED”
My systems specs are:
Intel Xeon CPU E5-2687W v4 (12 core / 2 processors)
128 GB Ram
Windows 10 Pro (19044.1586)
GPU Nvidia Quadro P600
RME HDSPe Madi

1 Like

Hello! For me it is exactly the same… The performance indicator jumps, even on an empty project… With the same latency settings as in C11, nothing can be done in C12. In addition, I am annoyed by the jumping indicator when changing the sound in some plugins, even such as PADSHOP or SYNTHMASTER 2 and how pops occur when I select tracks during the project playback. The same pops occur as during playback I add a MIDI track … In C11 such a thing did not occur…

1 Like

Is the meter actually correct though?

I had this doubt as well; however: the Windows ressourcemonitor shows a ressource demand for Cubase 12 which is more than twice the value of Cubase 11 for the same project. In other words: the problem is real and not caused by incorrect metering of the audio performance meter in Cubase 12.

1 Like

You probably did this, but how did you confirm that both your versions are using the same VST prefs

Hi @djn14 , thanks for your feedback (and also for setting the cooperative tone on this thread!).
The reported behaviour is as expected, due to the bug, though not desirable. We didn’t get the fix for this into the .10 update, unfortunately. We are working on it for one of the next updates.

3 Likes

Thanks Chriss! I appreciate the update and the information. It does provide some degree of comfort knowing there is an identifiable root cause for the issues I’m having. At the very least, this will keep me from obsessively tinkering with my system trying to find a fix! I look future to the future updates.

Thank you again for your participation in the thread and for adding to the constructive, cooperative nature of the discussion. I hope everyone’s contributions here has helped in some small way to improve Cubase moving forward. From this type of positive exchange, we all benefit in the end!

1 Like

Do you have any kind of time frame for this fix? I track live drums, etc., so setting buffers high isn’t an option for me, and I won’t go back to direct monitoring, since I haven’t had to use that for a few years at least. I have tried some of the suggestions listed here, but if you have a good workaround I have missed I would like to hear what it is. I have been tracking in 11 and porting to 12, as well as tracking with the pops and clicks, which don’t show up in the recorded files amazingly. Any suggestions would be helpful, and a time frame for the fix would be most appreciated. Thank you in advance!

1 Like

Yep, would definitely like to know the time frame for when this ASIO Guard spike issue can be fixed.
I currently have not much drop outs once I’ve activated the Steinberg Power Scheme, however, I do know there is a CPU allocation problem with ASIO Guard because it still spikes, and a sample library I’m currently using that uses up more CPU than RAM, has audio dropouts.

1 Like

Hi Chriss,
I just downloaded the 12.010 Version and tested the performance:
Bingo!
On my system I now get about the same ressource/performance behaviour as in Cubase 11.
The spikes seem to have gone away and the windows ressource monitor shows values that compare to the (lower) Cubase 11 value.
Great job and many thanks to the team!
Cheers Tom

2 Likes

@Scrummy , @Teo: the 12.0.10 update improves the Midi device handling and solves performance issues in that area - which seems to make things better for @jazztom and hopefully many more users (Thanks for your feedback!).
The update does unfortunately not provide the solution for the decline in real time performance (hence, the crackles, dropouts, stop-and-go events when record-arming Midi/ VSTi tracks at low latency). The solution for these issues will be part of the next update (no release date specified yet, sorry).

3 Likes

Hi Chriss,

thanks again for Your great support!
Is there a changelog or feature list for the 12.010 update?
Cheers
Tom

1 Like

UPDATE:
Going counter to advice, I changed my Kontakt VST plugin to multi-core instead of none WITHIN Cubase, and now it’s all good. No more dropouts.

Sorry for the false alarm!


12.0.10 update is actually worse for me.

Now the ASIO Guard spikes are not as bad, but realtime and peak and pushing like mad, and I’m getting even more audio dropouts than before!

2 Likes

Yes, the info has been added to the release notes on the website:

thanks a lot Martin!
Cheers Tom

Please let us know if you are still experiencing performance issues with Cubase 12.0.10 here: Cubase 12.0.10 - performance issues

2 Likes