Very High Latency with UR44 Inputs

I am trying to digitize some LPs via a UR44 front line inputs. The latency of the audio getting to the Cubase input channel meter is almost 3 seconds.

I have the UR44 buffer set as 32ms, and Constrain Delay Compensation on in Cubase.

Why is there such latency on the UR44 input?



Are you on Mac or Windows, please?

Can you use Direct Monitoring?

Do you have any inserts in Control Room?

On Windows 10. There are some inserts in Control Room but they are all disabled.

But it turns out it was the Direct Monitoring was not enabled. Thanks for that.

But, while we’re at it, how can I make it so that I can open both Cubase and the UR44 control panel? Right now I have to open one or the other, but not both (driver in use thing).

Also, even with Direct Monitoring on, it takes Cubase several seconds to start recording when I click “Record”. Why might that be?

Are you sure they’re disabled and not just bypassed (there’s a difference)?
Just to rule it out as the culprit, try removing them completely. Same with the Stereo Out bus if you have any inserts there.


The Direct Monitoring doesn’t go through Cubase at all.

Isn’t the Count-in enabled by any chance?

Yes. The plugins on the CR are disabled, not just bypassed.

Even with a count in, it takes several seconds before the record count in begins. It also takes time for play to begin, or for the transport to stop, etc.

Have you tried running LatencyMon on your computer?

1 Like

I should add that I don’t have this problem if I am not trying to record from the UR44. If I use my normal composing template things work as expected.

Do you experience this latency if you start with a new Blank project with your UR44? Is the UR44 driver updated to the latest version?

I’ll have to try starting just with a blank session. But this little 48k/24bit template is almost blank already.

That’s not possible. Cubase takes exclusive control over the driver.
But Cubase allows to control the UR44:
Studio > Audio Hardware setup

I don’t have any personal experience with Steinberg interfaces, but that sounds ludicrous to me. They’re asking about the control panel of the interface, not another audio application.
Besides, are Steinberg interfaces not multi-client?

I am not an expert but this a known limitation of ASIO drivers and Windows.
Search this forum for ASIO4ALL to read more about this limitation.


Yes, this is how it works.

Not really. It depends on the ASIO driver in question. Many (most?) ASIO drivers are multi-client, meaning they can accommodate multiple audio generating applications at the same time including Windows system audio.
Here is a Steinberg announcement from 2012(!) confirming:

These examples are obviously out of date, but it proves that it is quite possible. I’m not sure why the UR44, in this day and age, has such a limitation and it surprises me.

I use RME interfaces and have been for the past couple of decades. Their ASIO drivers are top notch and have been supporting multi-client use for as long as I can remember. I can happily assign dedicated outputs in several applications and use them all at the same time.

1 Like

Yes, I think so as well. For my UR824 (similar to the UR44 I think) I use the Yamaha Steinberg USB Driver. This driver doesnot allow to be used by more than one App at the same time. e.g.: I cannot run Komplete Kontrol and The Grand using this ASIO driver at the same time.

I’ve read your link about that muticlient ASIO wrapper but that’s ‘new’ to me.

Lucky you. RME is probably the best solution but it has a hefty price tag …

The article was merely to point out that multi-client ASIO drivers do indeed exist and have been for quite some time. Everything else in that post I would assume to be obsolete.

RME is far from the only manufacturer that provides multi-client ASIO drivers. That Steinberg interfaces, the proprietors of the ASIO protocol, does not—baffles me.

1 Like