Well if those meters expedite your work flow, I can see your concern. If they don’t, I would consider it more of a personal preference although the one major performance meter "is"offered as a feature.
The meters on itself are not bothering me, but I see that are cpu overloads on projects which normal the meter is not even moving.
I haven’t had drop-outs yet but the tested projects are not that heavy. So I’m pretty sure there will be problems with bigger projects.
What do you all think these meters display?
Damn I better go check it out then. I’ve been working at home with COVID all week, so I haven’t really had the desire or even the energy to even turn on my Launchkey hah. I installed the update the other day but still haven’t fired it up yet.
1 Like
What I’m saying is, I had the same issue with the performance meter on 14.0.10 and it happens regardless if the ASIO guard is on or not, or what setting it is on. I never had this issue on any other versions - 7, 8, 9, 10, 11, 12 or 13. I’ve been using Cubase for 26 years and I’ve never seen this type of meter behavior before.
3 Likes
Exactly, the same here. I also never had this behaviour before. But of course is not only s graphical thing. I see actual performance issues leading to dropouts.
Hmm. I managed to open up 4 or 5 projects yesterday without trouble. These were recent ‘final mixdown’ projects I’ve been working on the last month so I knew the meter by heart hah.
From the looks of the meter, seems to be peaking a teeny tiny bit higher than usual but everything was as it normally is. These projects were hovering around 25% on the ASIO Guard meter, peaking around 30 occasionally. Seemed pretty normal to me, but BackBlaze was also running full blast in the background too doing a brand new full system backup. Apparently, at some point the DAT file that stores your BackBlaze info gets too big to load into memory and their only solution is to delete the whole thing and start over. Great job BackBlaze, only three more days of this crap left to go.
MacBook Pro M1 user here and under 14.0.20 still got the “bubbling” performance meter and drop outs with only a few VSTs loaded. Don’t have these problems with Cubase 13.
Running Sonoma 14.7.4
Aaaaaaand tried under Cubase 13 it’s fine multiple instances of the same plugins barely troubling the meters and no weird spikes.
How do I get a refund for C14?
Are you opening a Cubase 13 project with Cubase 14 or did you create a new project with Cubase 14 and then compared with the 13?
Tested on Win 10 : either ways was ok with me.
Both new projects as older projects and Cubase demo projects have the same issues.
Hi All,
After testing and updating everything I could (incl. Bios) and removing all backgound programs and services, the irradically moving preformance meters still move. But the difference is that they now always on the same (low) ‘level’ nomatter if I have a empty project ‘standing’ still or a full blown mix. Since there are no drop outs I don’t pay any attention to the meters.
I do think it’s a kind of ‘bug’ in cubase 14 that needs to be adressed. But as long it is not affecting my work I don’t bother.
Thanks for all the reactions.
I’m having the same problem with C14. Been a user for 24 years and C14 is the first time I’ve had to go back to previous versions…I can open the exact same songs in C14 and the meter is constantly flickering up and down with random dropouts…and its rock solid in C13 and C12. I think its somewhat better in windows 11 23H2 than 24H2…but steinberg why would you release a program that doesn’t work with the current (and forced on us) windows OS?
Give us some answers, especially for those of us whose careers are tied up with this product.
Brad
3 Likes
Apparently, this will be like numerous other issues from past versions that won’t even be acknowledged, much less addressed.
1 Like
The trouble with those little meters in Ableton Live is that they can show almost no activity, across multiple tracks, but Live’s CPU meter can be up in the 60%+ range because of the cumulative effect. Live’s handling of cores and workload is only impressive if you’re using stock effects and instruments. I gave it up as my main DAW after nearly 2 decades. Everything that chokes in Live that I’ve imported to Cubase runs exponentially smoother. I’ve decided that for ideas, basic production, and static mixes, it’s still a fluid and effective tool, but Live is a choke artist when it’s time to mix… for me. The way it handles external effects is subpar and almost laughable, except for the tediousness, when compared to Cubase
Maybe it’s better with factory content and loops. We track almost everything, but drums. Cubase runs circles around Live on my Mac.
I’ve have seen the ASIO guard meters in Cubase bob left and right, but never at worrisome levels. I started migrating projects from Live 12 to Cubase 13, then upgraded to Cubase 14, and have no regrets for it
1 Like
LOL I didnt make it to 12 myself. I bought it a few years back when 11 was fairly new. Like an idiot, I passed up on all the emails I got offering it at a reduced rate before it was released, and for some reason ended up buying it about six months later.
I thought the concept was brilliant. I remember using it back around Live 3/4 when it was only audio., thought it would be the remixers dream DAW. The way it handles audio and midi clips is awesome, but I don’t do the ‘session’. Im all about the arrangement window and theirs sucks. Not even any hotkeys to move around, no fast forward, rewind, nothing. It was ALL mouse clicks or jump to markers. No ‘let me just nudge the transport back one bar and play from here’ unless you used the mouse and select it.
And yeah for whatever reason, mixing was not ‘fun’ in it. I don’t know what it was that put me off about it, but I just hated every time I opened the mixer and had to do something. Ended up bouncing tracks out and going into Cubase as well.
1 Like
I don’t know if this is related, but I will put my two cents.
In Cubase 13 I had terrible problems with “peak” meter and ASIO guard going crazy spikes all the time. I found somewhere suggestion to turn off CPU core 0 for Cubase (CPU affinity). I downloaded software Process Lasso, which allowed me to set the affinity for Cubase always to use only CPU (in my case) cores 1-13 (excluding CPU 0). It worked like a charm - fixed all my issues.
After installing Cubase 14 - again my meter peaks showed up - so i did the same. And again all my meters calmed down, no spikes.
Additionally I started using Audio Gridder plug in - for heavy VST fx plug ins and VST instruments - which also helped a lot.
Maybe you can try it too.
Good luck.
Starnaf
4 Likes
Hi Starnaf,
Interessing program… But I have disabled CPU0 (Rightclick on Cubase in Lasso and turn of CPU0 in affinity) But nothing changed. I have played arround with the settings but none having an effect. (Only turning efficiency ON makes the meter spike a bit more) Also giving Cubase Realtim epriority makes no difference. The stupid thing is that the spiking is happening on my laptop aswell on my studio machine. They have completely different hardware. (The Laptop has hardly any plugins (is just for testing things before I use it on my studio machine) The studio machine is Packed with plugins.
The funny thing is that the spiking of the meters is not changing. wether I have an empty project or a full blown mix. (Offcourse when it’s really heavy the meters will go up - But that rarely happens on this Machine.
So it’s not really a problem and looks more like a graphical thing that e real physical issue. (at the moment)
Audio gridder is not necessary since I have more than enough CPU overhead for what I’m doing at the moment. (Even with 70/ 80 tracks)
But I know it and can be handy if things get really ‘big’ (what I don’t expect)
Thanks !!
2 Likes
Hey, my C14 audio performance meter also jumps irregularly compared to C13 and is more loaded by about 20%.
Yes, C14 seems quite fast and stable, but the meter is the problem.
I also noticed that since switching to Windows 11 it’s worse. On Windows 10 I had this:
141 Retrologue 2 instances, 1024 buffer size, temp max 81 C, CPU 100% in task manager
130 Retrologue 2 instances, 128 buffer size, temp max 81 C, CPU 100%
127 Retrologue 2 instances, 32 buffer size, temp max 81 C, CPU 100%
On Windows 11 I have about 5-10 instances less at each latency on C13 and C14 worsens its performance even more.
Are we going backwards in development or do I need to reinstall Windows 11? Or maybe Windows 11 is more demanding on the CPU and that’s why the drops? This was an update from W10 to W11.
Try out Raphire Windows 11 debloat script and look on YouTube for a detailed instructions about fixing the latency for good. It helped me with performance issues on my laptop and convinced me to upgrade my main machine to W11 and Cubase 14. I haven’t seen any major differences in performance between 13 and 14 but I used 14 several hour only.