Hi Guy’s,
I installed the latest cubase 14.0.20 and I noticed that the performance meter if moving constanty (This now happens on My Studio PC and My laptop). Even in a empty project and when not even playing. Also I see that my midi out is also moving constantly (This is only on my studio PC - Also in a empty project and not running) I haven’t had this before on my PC (windows 11) Normally in a moderate project the preformance meter would hardly move at all. (even at a low latency setting) It’s not that I’m have drop-outs (yet). I never had this before with version 11/12/13
(I have done all the tweaking that is recomended)
So I’m wondering why this is now suddenly happening. As far as I know I haven’t changed something to my PC (except updating to the latest release of Cubase.
I’m having the same problem. I’ve already made a comparison with version 12 and 13, which runs very stable on my machine. Cubase 14 is consuming more energy even in small projects. I had to go back to version 13 because of this problem.
Hi Renato,
That’s not the answer I was hoping for. It’s silly that it seems that steinberg messed up cubase again that you have to go back to a previous version, that can’t be true. But I’ll take it that you already reported this. Did you get any responce from Steinberg ??
I cannot confirm that. I don’t see any noticeable difference between C12 and C13 on my Win11 system.
Are you sure that there is not some antivirus scanner involved? I remember having a really bad performance once with a new Cubase version, only to realize that I forgot to exclude the new Cubase version from the Wndows Antivirus Scanner.
I’m on a Mac but I have projects with at least 5x the track count loaded with UA channel strips, compressors, multiple group busses, reverb/delay busses. etc.
My ASIO guard is almost always hovering at the edge of the first little box in the meter (roughly 25%). It almost never changes and stays at this level from project start to finish.
@Rotil66 , It’s a shame that I have to use a previous version because in this version 14, I don’t have the same performance and stability as in version 13 and other versions that always ran with the stable meter. I even posted a topic here on the forum, but I still don’t have any answers. Cubase 13 is faster and more responsible in all tasks here for me. It is a problem that needs to be fixed in this new version as soon as possible.
The higher the ASIO guard setting, the higher the buffer it creates goes, so you WILL see that bar get larger if you select it.
Still, that seems REALLY high for the default settings. Are there any CPU serious plugins anywhere in the mix at all??
(This is one of those times, I wish we had Ableton’s little CPU meters on each track showing us the load each one is using).
Wonder if a preference file is corrupt or causing the issue.
%userprofile%\appdata\Roaming\Steinberg
If you rename the subfolder “Cubase 14_64” to “Cubase 14_64-OLD” and then open Cubase - wonder if the performance issue is solved.
But then the problem would be, trying to figure out what exactly in the Cubase14_64 folder - the original one you started with, is the messed up.
If you deleted the CB 14 prefs, it would revert back to CB 13 prefs.
It may work correctly with those but what’s to say that the problem is also in those prefs and have now migrated to CB 14?
If that doesn’t work then, make a copy of all previous prefs and then delete the originals from the prefs folder so CB 14 can start with a fresh set. At that point, if the prefs were even the problem, the culprit would show itself when customizations are built incrementally.
I’m going to power up the PC later today and update to 14.0.20 and see if the same problem occurs. I’ll post back any new observations.
Hi Suprawill and Cage22,
I have deleted (renamed) the Cubase14_64 folder as suggested but this makes no difference (on both my laptop with simple hardware and my studio pc with a focusrite interface). Still in an empty new project the preformance meters are ‘flipping’ randomly. As soon as I disable the audio driver it’s gone (kind of logical)
Using Asio4all or steinbergs own build in asio driver makes no difference.
If I select a generic Low latency driver the issues is not there but I also can’t select my audio-outputs (nothing there) so that’s logical since this is the same as having no driver. Increasing the buffersize is decreasing the amount if performance problems. But before I could easily run with a buffersize of 64 (4ms latency) on the biggest project without hardly any movement in my prefomance meters.
But starting with a clean Cubase 14 the issue is there.
I’m not sure if the 14.0.10 had the same problem. I have been ‘out’ for a while and could not work with cubase. I immediately updated on the release of .20 and that was actually the first time that I really was working and noticed the issue. So it might already been there before .20 but I didn’t noticed it at first short glance. (more looking at the new cool features of 14
Thanks
Same. Was happening on the initial release as well. It’s annoying AF and very distracting. Was NOT happening on ANY previous versions and my settings are exactly the same.
Thanks for posting that you’re also having this problem, @D-SANE .
I’m not sure what you mean though when you say you had the same problems on the “initial release”, but “not… any previous versions”. Can you clarify please?
I too had this problem with v14.0.10 and eventually went back to using v13. I’d hoped it might have been fixed in 14.0.20 but this does not seem to be the case. I do find it difficult to understand how something so fundamental can change from one version of the software to another. I can only hope that this gets addressed soon so I can enjoy the new score engine.
Ok, I just loaded a 14 track song with FX, VSTs etc. The performance meter read about 3% at idle and about 10% while running on CB 14 Pro 10.0.10. I updated to 10.0.20 and the meter results were the same although it stayed at 10% at both running and at idle. I’m not experiencing the performance issues posted here so that would lead me to believe it’s not a universal problem. The readings are low enough where I didn’t feel the need to check CB 13.
If the problem didn’t occur in your CB 13 version, then it would appear that it’s not a hardware or settings issue. The changes from 14.0.10 to 14.0.20 may turn out to be incompatible with another program being hosted by CB, whether it be a VST or standalone.
I know it would be time consuming but personally, I would try disabling programs, one by one to see if there’s a particular culprit. I would also go offline to make sure the background is quiet.
I hadn’t even looked at the performance meter since before CB 13 so I had no idea what its response had been to different songs. I wouldn’t have been inclined to go there unless I had audio glitches but hadn’t any of those since CB 9 or before. Is there any particular reason the meter concerns you if your audio is sound?
This is Ableton’s typical response when users ask about the CPU meter. Despite the meter, if the project isnt glitching and is running fine, its likely nothing to worry about at all.
I’d still like those little CPU meters on each track though like Live has!
I cannot say that the issue occured from 14.0.10 to 14.0.20. I think it was introduced with the initial release of 14. I didn’t notish since I have been away and actually started with 14 with the .20 version. But otrher reported it was other with the change from 13 to 14. I don’t think incompatible vst or plugins are causing this since nothing is loaded. The problem is already there in an new empty project without any track created or plugin active. It doesn’t feel like a hardware issue since it wasn’t the in previous versions before 14.
I actually had the same question, but I’m on a Mac and there really isn’t an “ASIO” driver anyway, so I’ve largely ignored that “performance monitor” altogether, only occasionally looking at it. Same with the CPU meter in Live - I’ve found them to be largely inaccurate on my typically over-engineered rigs anyway.
Now, all that said, I actually saw the behavior reported in 14.0.20 yesterday and did think it was curious: empty project, and the ASIO-Guard was quite erratic. Now it’s fine and exactly the same as N13, so previous suggestions that out-of-band processes (meaning non-Cubase) may/are contributing to that measurement may be correct.
Maybe it’s me, but if my audio sounds the way I want it to, I don’t care if that wee meter is doing an Irish jig or not
Yes it is not uncommon that non Cubase processes do conflict or can cause this behaviour. Off course on a PC you can never say ‘nothing’ has change. But I know I haven’t installed or changed anything last month 's (updates of windows are on manual not automatic) Also all background processes that can be killed, are killed.
(after noticing this behaviour I even killed about everything even what I normally use and have been using before) But nothing seems to make a change.
