The problem and cause probably varies for some updaters but for me the CPU overload was related to the VST3 option to - turn off the plug-in when no audio was present - . Unchecking this stopped the CPU overload. In my system / project, one VST3 plug-in had issues with CBase 10.5 and this VST3 option when ON: The excellent DMG Equilibrium EQ.
Within hours I received a response from DMG: Indeed, there is an issue with that ‘suspend’ setting and EQuilibrium. If enabled, Cubase continually sends a call to setProcessing when playback is stopped or in silence. This call means it’s about to start processing audio and we usually expect it just once before the processing starts. We use it as an opportunity to setup the EQ. Recalculating the EQ can be costly on CPU and in this case it’s happening constantly, hence the high CPU usage you are seeing.
I have added a workaround fix for this for the next update. There is a public beta release with this fix that you are welcome to use until the official update is out:
I tried the beta version and it works correctly with the VST3 option ON.
I hate to say it, but I have now joined the club. I bought 10.5 as soon as it was released, but I didn’t notice the cpu spikes until yesterday. The only way that I could get them to stop was to change the following settings:
{Studio/Studio Setup/ VST Audio System} on that page I changed the ASIO-Guard Level to “high”, and changed the “Audio Priority” to “Boost”. I also changed the “Disc Preload” from “2 Seconds” to “4 Seconds”. My cpu reader is still abnormally high, but my Windows 10 “Task Manager” CPU %Utilization never goes above 40%. It does sort of feel as if Cubase is working abnormally hard to do some of the simplest features, and I don’t know why.
After going back to 10 for a few weeks so as to finish a couple of projects I had a time limit on, I today went back to try 10.5, same problems, crashes, CPU mega-high…I read that some people thought the first update would sort it, still no sign…anyone hazard a guess as to when we should expect one? Pretty much unusable.
I 'm pretty sure Ed Doll (from Steinberg) said in a previous topic, regarding this issue, that they haven’t been able to reproduce this problem. If that’s the case I don’t hold much hope for a fix, which means all those who have this issue are stuck on v.10.
What’s next?
Re: [CAN-26328] Cubase 10.5 completely slow on Mac Mojave
Post by Matthias Quellmann » 08 Jan 2020 16:05
I can assure you that we wouldn’t have released Cubase in November if the memory issue would have been known at that time. The alpha testing for Cubase 10.5 started in February '19. The beta in summer. This issue must have gotten into application at a very late stage. I understand that restarting the application is not a solution, but the maintenance update with the fix is already in the testing phase and will be released at the end of January. Please have still a little patience.
I remember there was a time when you could only post in the forum if you filled out your signature. So at least System, MacOS or Windows and which Cubase version. That should be reintroduced. A post that doesn’t show whether it refers to Windows or MacOSX is completely unnecessary and annoying.
I remember there was a time when you could only post in the forum if you filled out your signature. So at least System, MacOS or Windows and which Cubase version. That should be reintroduced. A post that doesn’t show whether it refers to Windows or MacOSX is completely unnecessary and annoying.
I assume you are not referring to me, who started this thread?
Thanks kb420 and no, I didn’t have anyone specifically in mind. But of course already everyone who posted without signature I like to help where I can, and a reasonable signature makes it easier. I can still remember when Steinberg made the decision to no longer differentiate by system in the forums. I am still of the opinion that this was a wrong decision.
There are very specific system related problems. But this is now too much off topic. I just wanted to get rid of it once. All good.
P.S.
Besides that for me none of the described problems.
Thankyou very much for this WillBthr. Your temp fix worked for me though I’m not using the DMG plugin. Turn off the VST3 option and the problem goes away. Turn it back on and the problem returns. I obviously have an offending plugin as well. Not sure which one. Any idea on a short cut to determining the problem plugin?
I’m gong to make sure all my plugins are up to date and see if that helps. If that doesn’t work I’ll have to go through each plugin to see which one is a problem. Unless of course any one knows a short cut to figuring this out. I’ll report back my findings.
Hi, there is no quick way to see which plugins cause increased CPU usage, but I would suggest to not waste time trying to find out which ones.
The issue is not on the plugins’ side and is already fixed for 10.5.10, IMO the best way to approach this is to disable the VST3 option until the patch is released.
I don’t know how I missed this before. I went back and reread some of this thread and found this! Thanks for this post. This really seems to have fixed the problem, along with all of the other adjustments that I made to Cubase.
Just to add to this - my cubase 10.5 was causing my system to completely freeze every hour or so. My mobo on hard reboot thought it was an overclock issue, but it definitely wasn’t that. Reverted back to 10 and no freezes. Anyone else getting freezes, not spikes?
I’m sorry to say there is a one week delay due to a show-stopper we had to fix before releasing it.
This required building an additional release candidate version.
I like to help where I can, and a reasonable signature makes it easier. I can still remember when Steinberg made the decision to no longer differentiate by system in the forums. I am still of the opinion that this was a wrong decision.