To address your latency issue with the BEHRINGER U-PHORIA UMC22 and ASIO4ALL in Cubase, you can try the following steps:

1. Lower the buffer size in ASIO4ALL control panel. This can be accessed through Cubase's Studio Setup menu. Reducing the buffer size will decrease latency, but may increase CPU load.
   
   
2. Ensure you're using the latest version of ASIO4ALL and the UMC22 drivers.
   
   
3. Try using the dedicated Behringer drivers instead of ASIO4ALL. Some users report better performance with manufacturer-specific drivers.
   
   
4. Adjust your computer's power settings to "High Performance" or "Ultimate Performance" to prevent CPU throttling.
   
   
5. In Windows Task Manager, set Cubase's CPU affinity to avoid cores with high interruptions. This can improve audio performance.
   
   
6. Check if any VST plugins or amp simulations are causing additional latency. Disable them temporarily to isolate the issue.
   
   
7. Ensure your computer meets the recommended specifications for low-latency audio processing. An audio interface might help if you're using onboard audio.

If these steps don't resolve the issue, consider trying the Generic Low Latency ASIO Driver in Cubase as an alternative. Remember that achieving very low latency (below 5ms) can be challenging and depends on various factors including your hardware and system configuration.

Source: Perplexity

 

Last edited: Mar 6, 2025 at 12:32 PM

Sure it's not RME, but for the price given.. . I'm using those ancient (true) Asio drivers for my Behringer devices for quite some time without Issues. From win 8.1 to 10 and now 11. These Drivers are not made by Behringer, they are the dll from the chip manufacturer put in a Behringer GUI. That's what they all do. The only companies programming their Asio drivers themselves are RME and Steinberg/Yamaha.

 

(Drivers download)Behringer U-PHORIA Interface Test and drivers , latency solved

 

Last edited: Mar 6, 2025 at 1:35 PM

ASIO4ALL-drivers don't work with UMC22 as well as they should.

What bothered me the most was that adjusting the latency was a bit tricky and when the DAW is on, the ASIO drivers are only used by it and for example the sounds from other windows applications are not heard unless you set the DAW drivers away from ASIO.

I found old Behringer ASIO-drivers from internet. They work well with UMC22 and I think using them is the best solution.

Just try it yourself and tell me your opinion:

https://workupload.com/file/xnZ8yAR



Edit:

Sorry for spamming.
I just read the previous posts and noticed that two other posts also provided a link to the same driver.

Well, now at least you can definitely find it in this thread.

 

Last edited: Mar 6, 2025 at 2:45 PM

Avoid unofficial ASIO drivers, but if you need "universal" ones choose Steinberg:

https://helpcenter.steinberg.de/hc/...erg-built-in-ASIO-Driver-information-download

 

Use "ASIO Link Pro" to let all other apps sounds play while using ASIO4ALL.
Initially it was a paid app, but unfortunately the author passed away and his family made it free.
https://give.academy/ODeusASIOLinkProPatcher/

 

my friend has it. i was shocked that it has no driver only asio4all.

 

The reason you can't hear other applications is because there is a sample rate mismatch between DAW and Windows Audio. Though, I'm not sure if ASIO4ALL hijacks something that even when fixing that still doesn't work, but that is the solution for any other ASIO drivers.

 

ASIO4ALL takes exclusive access to the device and prevents other apps from using it.
As I mentioned a few posts above "ASIO Link Pro" is the solution to this exact problem.

 

presonus has Native ASIO drivers also.

 

This is only half right. Yes, ASIO is exclusive, and therefore can only be used by one device at a time. What that means is that you only have one low latency audio pathway, and once it's taken, the first one who took it gets to keep it. The non-exclusive pathway is still open, however, so that means any application that doesn't request ASIO can still output audio via Windows Audio just fine as long as this pathway has the same settings as the ASIO pathway. So it needs the same number of roads (bit depth) and the same space between them (sample rate). If you meet the requirements, the non-exclusive pathway can pass audio through at the same time.

The issue is that the way ASIO4ALL works might not meet this criteria, I can't say because I haven't used ASIO4ALL for way too many years. But there are way too many alternatives nowadays, even the guys from Voicemeeter seem to have one, so even if it doesn't work out of the box, there might be alternative drivers that replicate this behavior.

 

Some Behringer products are much better than others.

The Behringer UMC22 was first released in 2013 and it's still being sold. It's $39 brand new. One of the cheapest and most problematic USB audio interfaces for anyone working with DAW recording.

As bad as the UMC22 is, the Behringer UMC 204HD/404HD interfaces (starting at $79 new) are fantastic and are also very affordable. I only replaced mine with the SSL 12 for convenience, and there's a difference in quality, but not $420 difference!

My advice to the OP is drop $40 on a used UMC 204HD, or $79 on a new one. There are several other good options in the $99 price range that are also stable performers. I just don't think it's worth fighting against the UMC22.

 

This is how I have the settings done. and I have a latency of 10.431. I will try and see what was suggested to me.

 

Generally speaking, if it's under 10 ms, it's OK, you won't notice it.

Windows: How to set up and optimize a Digital Audio Workstation
https://helpcenter.steinberg.de/hc/...t-up-and-optimize-a-Digital-Audio-Workstation

 

But this is the in or out latency, isn't it? What matters is the roundtrip latency I guess. Maybe I am wrong, I am using Logic and there I always consider the roundtrip when setting. Yours is around 20, that is not very favourable.

 

Voicemeeter is great, especially Potato but the Banana free version can also be very handy. Both versions are much better than the old ASIO4ALL because they can aggregate all connected ASIO interfaces (and any device like onboard Realtek etc) for multi in/out use within any DAW using their virtual ASIO driver.
Cheers