CPU peaks are a huge problem in Cubase 13. I feel that the way Cubase 13 handles Plugins and VST instruments is in dire need of optimization. I just downloaded AudioGridder and 99% of my spikes disappeared as seen here:
I do not want to run this program but it does what it is supposed to do.
We need this in an update ASAP.
100% agreed on this. My thinking is AG once loaded takes cpu cycles direct from the cpu bypassing C13’s direct processing stack. So this suggests to me that there is real need for optimisation here. OR.
Steinberg has made adjustments to the VSTI stack and plugin developers have not caught up as yet. My reasoning on this is Kontakt 7. Two weeks ago K7 was causing me mad spikes when working with multi’s, N.I pushed an update a few days ago and not seen the mentioned behaviour since. Co-inkeydink? Possibly
I have had big problems with Kontakt 7 since version 7.5. I haven’t had any performance issues once I got it running, however, I had big problems loading my projects. Sometimes I must try up to 10 times to get a project I just saved up and running. If I have many instances of Kontakt in a project it is a big problem. Kontakt has been updated just about weekly so I hope they are aware of the problem. So who is at fault? I don’t know.
That’s very curious behavior. What happens if you record that midi that leads to cpu spikes, and play it back with asio guard turned off, at various buffer sizes? Does turning CDC on make any difference?
I’ve noticed the same behaviour with CB13!
To test I used the (corrected) benchmark project of Dom Sigalas (https://www.youtube.com/watch?v=3Zp05bpct3Y to compare CB11.041, CB12.070 and CB13.041. (Download benchmark project here Dropbox). It uses Steinberg’s own Retroloque in all tracks.
My PC is an i9 7900X with 64 GB ram. My Audio interface is Roland Studio-Capture 16 x 10 (usb2). I’ve set my buffer size to the lowest 32 samples.
With this setting I can play up to 60 tracks in both CB11 and CB12 without any issue. But in CB13 I can only play 18 tracks before it starts to choke! What’s also remarkable in CB13 is that I can only use the ‘low’ setting for the Asio guard! As soon as I choose ‘off’, ‘normal’ or ‘high’ I can not even play like 2 tracks in CB13 without audio spiking like crazy!
So it seems to me there is something really wrong with the performance in CB13?
I tried that benchmark project on my M2 Pro Macmini with asio guard set to medium. Results:
Cubase 12: 105 tracks
Cubase 13: 110 tracks
If I reopen the test project and try it again, the number of tracks will vary by +/- 5 tracks or so. In other words, those numbers can probably be considered equivalent for C12 and C13.