If trashing preferences and reinstalling Cubase and all its additional needed programs, such as licensing manager etc. does not help, I think we cannot help you further here. You wrote Steinberg Support directly already, by using the support form, right? Please keep us updated, what they say!
Steinberg Support
Sorry i missed that info.
Everyone trying to help here. If you come to a forum exposing your problem you should be able to handle most types of suggestions.
I would recommend a clean fresh install of all Cubase , clean preferences etc etc. I fyou already done that i would suggest to contact via phone the support and wait for the best suggestion.
I think questioning the way Anton prefers to work is not really useful here. The truth is that he has observed a difference between C11 and C12 regarding performance at extremely low latencies (32 samples), and maybe he has a point.
It seems some things have changed under the hood that have affected ASIO performance in C12. People from Steinberg acknowledged this. Even the performance meter is completely different now. So it could be perfectly possible that C12 is simply not as performant as C11 was when working at those tiny latency values. In my opinion, this could be an interesting point we could contribute to investigate.
2 Likes
Exactly! Thanks!
1 Like
Unfortunately I can’t, because online support isn’t available in Ukraine, that’s why I’m here
1 Like
This afternoon I’ll try to reproduce Anton’s setup with my RME RayDat at 32 samples of latency, and post results.
2 Likes
Hi @AntonVorozhtsov,
I see two possible explanations for your issue:
-
Indeed, we observed a little higher base load on some intel CPUs with Cubase 12, compared to C11. This impacts low latency use cases like yours. The issue was particularly present on older generations of i7 processors (8th generation and older) with a medium core count (~12 - 24). It affects some, not all systems and we were not able to find the root cause. Do you run such a system? There’s no other way than to increase your latency, to work around this issue, I’m sorry.
-
A second issue which could be related with yours: When starting with fresh preferences, it can happen that the top most output bus ( the default one, created by Cubase on first startup) is processed with real time latency, where it should be processed with the resource-friendly Asio Guard latency. Particularly, when you use master effects, this can impose reasonable load onto your system and break your low latency experience. This issue is not new in C12, but only present when working with the initial output bus after the install (or when starting with fresh prefs, as said).
To work around this issue, either:
- in Audio Connections: delete the first output entry and create a new one and use it, or
- in Audio Connections: create a second output bus and use it instead of the first bus (subsequent buses are processed with the Asio guard latency)
I hope this was helpful for you.
Cheers, Chriss
6 Likes
@Chriss 2019 MacBook Pro with 2.3 GHz 8-Core Intel Core i9
We’ve got october now and Cubase 12.0.50 and yesterday I had the very same issue: Started fine, began to record, nice normal latency, added a new track, some plugins, this and that and wanted to record another track and suddenly latency exploded to several hundred and even thousands of milisecons, no normal recording possible…
If it helps: Some of the “this and that” I did, was to create a new Master Bus, route the original to the new one and add a deactivated plugin list to the new master channel (a “kind of a” mix & master setup)
I closed cubase, opened it, but that didn’t actually really help… Just when I deleted the created channels and plugins (deleted, not deactivated as deactivating didn’t help) and restarted macOS it went back to a normal usable latency. But it can’t be that it saturates the latency so quick, and that even deactivating plugins does not help…
1 Like
great info - thanks for posting
1 Like
I guess none of those are my issues, I have no problems with performance on mixing stage, when I use master effects/ I use low latencies with multiply buses, so it isn’t my problem, as well as CPU. On newer M1 mac I have the same issues as on old Intel 4th and 8th generation i7’s
Butthank you, i didn’t know about default master bus specific with Asio Guard. Noticed, that master bus effects takes the most of ASIO performance, but thought it’s a normal behaviour.
Hi @Chriss, thanks a lot for chiming in and sharing such a wealth of useful information. Just a quick question also related to this topic, if you don’t mind answering:
Have you considered internally the possibility of offering a preference so users could choose the behaviour of the performance bar that better suited our needs? I mean, between the old, more relaxed way of C11 and prior Cubase versions, and the new, more precise and peak-based mode of representing performance that is now the default in C12.
There’s tons of posts on the forums, both from Steinberg people and others, all saying that re-installing really does nothing for issues like these.
Yes, deleting the preference folders for ALL installs of Cubase is recommended.
1 Like
Hey there, do you mean in the project, or in the audio connection settings?
But Cubase 11 and 12 are different underneath as far as Asio and CPU performance goes?
The metering is different, the options in Studio Setup are different…
If Cubase 11 is better for his scenario, why not use it?
The Audio Performance Meter is different in v12 by design.
And what should I do after Steinberg drops it’s support? Seeking sideways is a bad option regarding to product quality. I need C12 as good as it should be without any “why”
1 Like
I think it will take a (very) long while until support for Cubase 11 will drop…I am still on 11 and super happy.
I don’t mean to appear to be “simplifying” your problem, I’m sure you have considered every opportunity, if that is the case, I apologise.
But the post is so old at this point, it just seems like somethings not adding up or some vital piece of information is missing.
If you have your Advanced options set and cannot use CDC (for whatever reason) I guess then you’re at the mercy of Steinberg.
I’ve used both C11 and C12 live on MBP (last i7 intel model) running samples, some VI and a couple of stereo sends for live vocal Reverb, I just don’t seem to be having as noticeable an issue as you’re having between the 2 versions.
This year they’ve dropped 10.5.
But, again, this is not what we are talking about. I paid for 12 and I want it working as it should, nothing more and nothing else
1 Like
Yep, they dropped it because it is part of the old licensing system. C11 is probably supported for a very long time.
You are absolutely right.
I would write an email to Steinberg support anyway. You can explain your situation, that it is not possible to get Support from your dealer because of the war. I am sure, they will be helpful and can make an exception in this case.