This morning I updated the Steinberg download assistant, updated 14.0.20 to 14.0.30, updated halion, and updated Spectra layers. All this occurred without any error messages, or security notices. I have not actually run any of the programs.
I have the same problem with my Steinberg CC121 Controler.
Hi folks,
I truly was looking forward to Cubase 14 which I bought around Easter with that plugin bundle. But I have to admit that I’m not truly happy with Cubase 14. With the 14.0.20 upgrade the mouse wheel behavior has been broken in the sample editor which then made it impossible to quickly jump between multiple samples in a group to easily review the pitch and warp changes. This really breaks my workflow as I do that a lot with around 32-64 samples in a group. The following picture shows the dropdown box I’m talking about:
And truly I don’t get the hassle with that mouse-wheel “destroying mixes”. Just use the “Lock” (also visible in that screenshot) and be happy.
Sadly, with 14.0.30, this is still not fixed (filed under Cubase Support Ticket #705926).
–
Furthermore I’m experiencing higher ASIO-Guard Latencies for the same project under Cubase 14 compared to Cubase 12. Under 14.0.30 the load is sometimes around 75% as the following screenshot shows:
In Cubase 12 the ASIO Guard seems to be more stable jittering around 51-54% as this screenshot shows:
Is this intentional or rather reveals a performance issue?
–
Sorry Steinberg, but for now I stick with Cubase 12 
.
2 Likes
I don’t think they are sorry about you deciding for Cubase 12. They already got your money for Cubase 14 - and money is what business is about.
Yep, you are true about that. But I’m pretty certain that Cubase 14 might have been my last version. If they truly gonna drop VST2 with Cubase 15 I might not consider upgrading anymore. There are a few VST2 plugins I’m still using for which there is no VST3 version…
2 Likes
You can use wrappers for vst2, bluecat, etc..
1 Like
At £50 a year for updates, plus the £450 for the initial purchase, I estimate I’ve spent £1950 for Cubase. Spread over 33 years. Pretty good value, if you ask me.
3 Likes
I am usually not working with multi-mic recordings so I don’t quite understand in what way Cubase 14 is lacking a navigation feature compared to C12.
Can you maybe try to make me understand if it is not too much to ask?
BTW - the latency does not increase together with the meter. The latency remains steady. The meter is just showing how much of the maximum ASIO Guard is in use.
I’m facing the same problem with Cubase 14. I haven’t been able to use it until today due to performance instability compared to versions 12 and 13. It consumes a lot more power and is slower. It really needs a fix in the next update at this point. Many users report the same problem I’m having.
1 Like
Ah, I wasn’t aware of that. Will check it out. Thanks for the hint!
I am usually not working with multi-mic recordings so I don’t quite understand in what way Cubase 14 is lacking a navigation feature compared to C12.
Can you maybe try to make me understand if it is not too much to ask?
In Cubase 14 it is not possible to quickly navigate through the individual samples using the mousewheel anymore. That was possible in Cubase 12 using the mousewheel over that checkbox that I’ve marked in that screenshot.
Ah and I totally forgot to mention that this feature has been broken with Cubase 10.5.30 maintenance upgrade and fixed in Cubase 11. I filed a support ticket back in the day (issue #375541, as if anybody from Steinberg would actually care).
BTW - the latency does not increase together with the meter. The latency remains steady. The meter is just showing how much of the maximum ASIO Guard is in use.
The meter is altogether showing a higher latency than in Cubase 12. This indicates - at least to me - that Cubase 14 is suffering some performance issues. Performance has increased from Cubase 11 to 12 (in my personal experience) but 14 seems to be worse.
@Renato_Borges post confirms my statement.
2 Likes
Good update! I would like to see this thing to be addressed if possible:
In these kind of windows, I always unmark/uncheck the “Always on front” option, but everytime I open a project that include these MIDI inserts they always reset to be activated this option again.
PD: And in the contrary: the “Always in front” option is missing for the Modulators panel:
As was already said, the CPU meter does not show latency in any way at all.
Yes, but that is not the point. Why is that ASIO-Guard latency having these spikes in Cubase 14, whereas in Cubase 12 this was rather smooth?
This thread (and links to the help article) may help:
The updated APM includes additional telemetry data. Are you actually experiencing audio dropouts in a C14 project that you do not experience in C12, or are you just looking at the APM gauges and presuming that C14 performance is worse because the C12 gauges show different activity?
2 Likes
Indeed, I was assuming that observing these spikes mean it’s worse in a sense. Even the average ASIO-Guard load appears to be higher. I haven’t experienced drop outs so far. Yet, I guess it cannot hurt to take a look at the CPU load to be sure. I’ll keep you posted.
1 Like
You keep referring to latency which you are not really seeing. The ASIO Guard does not in ANY way show latency on your system.
All you are seeing is how big the ASIO Guard buffer is. This is NOT latency.
Are you pressing a key and the note doesn’t come out until a second later? THAT is latency. The meters do not show and have absolutely NOTHING to do with latency. There is no meter in Cubase at all that shows you latency. You can have latency and have the ASIO Guard not even above 1/4" of the way. You can have latency and never see the CPU meter move, has nothing to do with the meter.
I did not talk about LATENCY. If you read my posts I was always talking about ASIO-GUARD LATENCY. The difference between Cubase 12 and Cubase 14 in the AISIO-Guard latency is clearly visible, yet the meaning of that difference is unclear to me.
After reading @Thor.HOG linked post I’ll check the CPU load next and see whether there is some noticeable difference. If this is just “optics” showing more precise data, then I’m completely fine with that. Yet, I truly want to understand what’s causing the difference and whether this impacts Cubase’s performance at all. Judging from the “optics” it looks like “something is slower”.
–
But apart from all that I’d rather have that mouse-wheel behavior as it was in Cubase 12. For now this is a blocker to my workflow 
.
To see your ASIO Guard latency, open Studio > Studio Setup and select Audio System.
Just not the right term. I guess we could say the meter shows the ASIO Guard load. when the meter is full, drop-outs are likely to occur.
All the while the ASIO Guard Latency is a fixed value, that only chnages, when you go to the Studio Setup and change it by yourself.
No biggie. Some of us try to get terms pedantically correct in order to avoid misunderstandings in the future.
2 Likes