I updated to CB13 4 weeks ago and my CPU will not drop below 25-35% with Cubase alone. I have seen it when projects were not loaded either, just with Cubase open. Many projects taking forever to load. My fan is running on high 100% as long as Cubase is open. 4 weeks now.
Some projects just won’t open at all. They sit with fan cooking high.
And now it is happening with either Cubase 11 or 13. (Cubase 11 still requires the dongle)
I run relatively low-count projects, 15-20 audio tracks, 2-3 VSTi. (SSD5, EZDrummer, Maybe a Vsynth)
Softube Console and Fader
UAD plugins
Alot of external hardware.
I have been working this way for years.
I was getting PACE at 13% or more as well this week, but an update solved that.
Cubase 13 (and now 11 as well) are still running 25-30%
I do understand this has been covered regularly, and I have scoured many posts that come up with a search, but I cannot find a solution.
Grateful for any help. Any ideas to try I will.
Just opening up projects to finish this record, even if I have to find a different platform will be a life changer.
Windows 10 Pro
Intel i7-9700 CPU @ 3.00GHZ
32 G RAM
64 Bit
RME FF802 clocked by LYNX Hilo
Though as a 20+ year user of Cubase, that is early 101 troubleshooting steps. This is something else. For the first time in 22 years, I am contemplating a new DAW. I hate the idea of a learning curve this close to a new album, so I hope I can get this sorted.
A new machine may be what you need rather than a new DAW as even older cubase versions that worked in the past are no longer performing on the same machine as you were used to in the past and until they do i would suspect your machine not Cubase .
LOL, my machine is fine. Up until the update, it was rock solid, zero glitches day in and day out. It is not my first trip around the update cycle as a professional in pro audio. This, whatever it is, is Cubase 13 ‘related’.
If Cubase 11, that hasn’t been updated, starts to misbehave after having behaved correctly for a good while, it would seem to point to a hardware problem. If just C13 was misbehaving, well then, yes, but software that was fine one day and then suddenly going doolally…
Your C13 licence allows you to use C12, you could try that.
I’m hoping this includes running Cubase in safe mode and/or deleting the preferences folder (after backing up!)? And maybe uninstalling and reinstalling? And checking the Task Manager to make sure it is Cubase causing the problem? (Clicking any column in the Processes tab enables you to select additional columns for viewing, including CPU/GPU/network use for any running program.)
I was version 13’s biggest critic. Since the .21 update, with about 40 hours use, I’ve had just one crash - when I had Cubase open and was editing a video in VEGAS at the same time. I had to reboot the machine.
Cubase 13 on my i9 12900/Win 10 system.
I think it’s more than worth troubleshooting this, but I don’t know where we would start. So I’m hoping for someone more knowledgeable to appear.
Edit: Troubleshooting will tend to start with the most obvious suggestions, to either eliminate those possibilities or to gather more clues in the process. It does not reflect on you personally.
