Behringer U-PHORIA UMC22

[L0FKA]

If you're on Windows 11 legacy driver might not work for you.

To get it working, install true ASIO driver FROM HERE
Also use a daw to set it to 16 bit 48000 Hz (as well as windows recording device settings)
Reaper for example

Connect your headphones to output of your UMC22
Config below is working, you may need to switch your input channel to 0 if you're using mic input instead of instrument.

RS_ASIO.log
(rename it to RS_ASIO.ini, or copy contents over)

[mdias]

Thank you for the report.
I've added it to the list 👍

[Awia001]

Out of curiosity, why does it require the use of the legacy Behringer ASIO driver? I can get it to work using that driver but then wasapi audio through the interface has a terrible popping that I cannot eliminate. And then I cannot get any audio from RS using ASIO4All as the driver in the RS_ASIO.ini.

[mdias]

@Awia001 ASIO4All is an ASIO "emulator", it does not communicate with your interface as effectively as a native ASIO driver does.

I'm not sure I understand why you're trying to use ASIO for input and WASAPI for the output if you still want to use the interface though?

[Awia001]

@mdias My apologies, I didn't explain myself fully.
During gameplay I am solely using ASIO and that works perfectly when using the Behringer legacy driver, but then afterwards when I transition back to WASAPI for "normal" Windows audio there is constant popping in my headphones through the interface. This doesn't happen when using ASIO4ALL but then I cannot get ASIO audio in or out of RS even though ASIO4ALL works perfectly in Reaper and other ASIO applications.
In my setup I am using the interface as a headphone driver just generally and not just as an input/output for ASIO based audio.

[jessemodesto]

My installation keeps failing using the provided files for my UMC22.

I found the culprit.
In the busb2902.INF file there is line:
[BEHRINGER.NTAMD64] %USB\VID_08BB&PID_2900.DeviceDesc%=USBDRIVER.Dev, USB\VID_08BB&PID_2900 %USB\VID_08BB&PID_2902.DeviceDesc%=USBDRIVER.Dev, USB\VID_08BB&PID_2902
The installation fails because my UMC 22 has the following VID & PID:
USB\VID_08BB&PID_29C2&REV_0100&MI_00 USB\VID_08BB&PID_29C2&MI_00

After modifying both INF files, running Inf2Cat for Windows 7x64, and disabling safeboot for testsigning (could not get the signing to work with signtool) the setup worked correctly and identified my UMC22. However the device fails to start (yellow sign in device manager) and other than being a usb device, does not include the sound controller in device manager (no audio output or input).

I am stuck here! I have not encountered anyone else with this issue (so far). It seems like my UMC22 got refurbished with different hardware? I am not sure. Unfortunately I have to continue using ASIO4ALL with the Generic USB Audio drivers.

[mdias]

@Awia001 sorry for the long delay; somehow I missed the notification of your message.
In any case, there isn't much I can do about it; it may very well be the case that RS_ASIO is somehow just not caring to fill the interface buffers with silence before quitting, and instead a part of the game's quit sound remains looping in the internal buffers.
RS_ASIO being just a translation layer, it sometimes lacks the easy ways to solve this kind of problem that would otherwise be simple to do on a normal ASIO integration, but at the end of the day the interface drivers should guarantee a good cleanup state after an application quits, and it seems you're missing that.

Unfortunately with a driver that is no longer supported you're also out of luck with emailing the company. :/

@jessemodesto Since no one else reported the need to edit the inf file, it looks like you might somehow have an actual different version of the interface which requires it's own drivers..?