Cubase LE 13 latency is higher than what the settings in Asio driver says

So i bought and installed Cubase LE 13, coming from Cubase 5, and now the latency in C-LE 13 is higher than my Asio driver says it is, my asio driver is set to 5ms latency, but i can clearly hear that the latency is atleast 25ms, i deactivated the Cubase latency guard cause that is even at low still 17ms, but Cubase refuses to lower the latency down to what my Asio driver is set to.

it looks like the Cubase latency guard won’t disable. Atleast i think that the latency guard means that Cubase has a safe value for latency as to what the program thinks is suitable for my hardware. i don’t know if i’m right about how that works, it’s just a guess. But than that would mean that a quad core Intel 9900K with 32Gigs of fast RAM and dedicated USB audio interface would not be enough to have a low latency with the program, i find that hard to believe.

Anyways, i have 4 Asio drivers for different pieces of hardware, one for my Mooer GTRS guitar, one for a USB audio interface, and two for multifx that are capable of recording through USB, none of the Asio drivers that come with the hardware works on Cubase 13, while all of them worked on Cubase 5, so i have to use Asio4All, cause that is the only driver that works on 13 LE, and it works on all hardware, and i can get it as low as 5ms, not lower. The generic Asio driver from Steinberg only plays back, at first it didn’t do anything, but i read somewhere that Wavelab had a generic Asio driver too that was supposed to work OK, and it actually works with playback, but does not record.

So i actually regret buying Cubase 13 LE, i just threw 99 euro’s in the toilet it seems. Or is there a solution or update or bugfix for this behaviour ?

You have the same processor as I have and amount of memory. I have no problem getting down to 3ms with an RME Babyface pro fs using its asio driver. It definitely is reading it right. If you have asio drivers correctly installed then Cubase can use them. Are you saying they are not in the drop didn’t menu when the device is turned on and connected?

I use Cubase for many years, different versions, also for Mac, and i never had this problem either, that’s why i said that i find it hard to believe that my PC wouldn’t be fast enough, i had better latency with a athlon cpu 10 years ago.

Yes, the drivers are in the drop down list in Cubase, and i can select them as well, but when i want to map the ports, they’re not there, and the one that is (steinberg generic) can be mapped to the input and output, but have no input sound. Only the Asio4All drivers work, and Asio4All finds all the hardware and can work with all the hardware, i can get the latency down to 5ms with Asio4All, this used to work fine with Cubase 3 and 5, but not with the latest version, it says in the studio setup that the latency is 5ms, but the reality is that it sounds closer to 25ms, i have a lot of experience with latency when playing my guitar solo’s in Cubase, and 5ms is perfectly doable even for pretty fast solo work, but 25 is not, anything above 10ms becomes nasty for my brain.

That’s why i think that Cubase itself must have latency coming from somewhere on top of my drivers, how, i can’t understand cause it never happened to me before and i don’t know how audio engines work internally, so i can only guess.

I’m just hoping that someone that’s read this thinks i had the same thing before myself and i fixed it like that, otherwise i’m going to have to install my old Cubase again and i lost 100 euro’s, and will not be happy.

So i have been trying all kinds of different things, nothing seemed to work, so i thought maybe my cheapass Realtek chipset on my motherboard wil work, tried the realtek asio drivers first (those worked in Cubase 5) they load, i can set latencies, but no sound whatsoever, Asio4All can do output on that, but input is no longer separated into line in and mic, but is combined and gives a extreme static noise, not workable.

So after some googling i tried something called Voicemeeter, does work somewhat, but not really satisfactory, then i installed FlexAsio and messed around for an hour with that trying all kinds of combinations, once i set that to directsound, i could see the green audiobars jumping up and down on playback, but no sound, tried setting the pc to realtek speaker, nothing.

So after nothing worked, i now tried the Steinberg generic driver again in despair, and it had a extra few inputs and outputs cause i installed alternative asio drivers, and all of a sudden that driver now works on my cheapass realtek chip where it did not before ?

And the Steinberg Asio driver says the latency on the input is 40ms, but it’s pretty much direct, like 4ms instead of what it says, 40 ???
I don’t know what’s going on with this new version of Cubase, but it is extremely bugged, nothing works like it should, i have a few other audio programs that use Asio, they all work flawlesly with all my hardware, Cubase does everything wrong !! And i mean nothing is correct…

But atleast i can do something now with the generic driver, but it is far from ideal like this, i really hope the Steinberg programmers figure these Asio problems out, cause it’s quite obvious that there are problems with the code of this version of Cubase.

i tried my old Cubase 5 for a bit, everything just works there.
i don’t know what’s going on, but i’m a bit dissapointed in this DAW.

I deinstalled Cubase 13 and reinstalled Cubase 5, everything is working again…
I don’t think i will ever buy another Steinberg product again, going to check out the competition.

1 Like

FYI same thing happening to me. I came to this topic for the same problem. I just cant lower the noticeable latency even though my Yamaha driver reads 4ms. So - I’m glad downgrading helped you work things around. I don’t have the luxury of doing that.

Cubase reports what the driver tells it so it’s not a Cubase fault. Many people have this running perfectly as I do.

You realise plugins will add latency? Make sure no plugins in the record monitoring chain that are adding latency to the signal. That includes, master track and control room as well as track inserts, group inserts if going via any groups, and even sends that the record track may be routed to.