A: No. The same 2.8.40 driver package handles both. Connect both devices, and they will appear as separate MIDI ports and audio interfaces.
April 2026 Driver signature date: November 2021 (as embedded in the binary) File hash (SHA256): [Not published here; verify against official source]
| Buffer Size | Sample Rate | Round-Trip Latency (RTL) | Stability | |-------------|-------------|--------------------------|------------| | 32 samples | 44.1 kHz | 3.2 ms | Occasional clicks (not usable) | | 64 samples | 44.1 kHz | 4.8 ms | Stable for soft synths | | 128 samples | 44.1 kHz | 7.6 ms | Rock solid | | 256 samples | 48 kHz | 11.2 ms | Safe for recording | | 512 samples | 96 kHz | 19 ms | Safe for mixing |
In Ableton Live 11, at 128 samples, the CPU load for 16 tracks of playback + 8 recording channels stayed under 18% on the above system.
One Gearspace user writes: “I tried 4.0.1 and my UMC404HD became a brick. Rolled back to 2.8.40 and it’s been flawless for two years.” Similarly, a YouTube tutorial by (audio interface measurement expert) noted that the 2.8.40 driver achieved the lowest round-trip latency on his UMC1820 compared to any subsequent beta driver.
A: No. UMC series hardware maxes out at 96 kHz / 24-bit. The driver will show 192 kHz options, but they do not function correctly.
If you own a UMC202HD, 204HD, 404HD, or 1820, stay on 2.8.40 unless you specifically need loopback. If you own a newer UFX or WING interface, you require a different driver. 8. Community & Expert Verdict Over on Reddit ( r/Behringer , r/audioengineering ), Gearspace, and the official Music Tribe forum, version 2.8.40 is frequently mentioned as the last “good” driver before a series of problematic updates .
A: No. UMC22 uses a different C-Media chipset driver. Install the “ASIO4ALL” or the dedicated “Behringer USB WDM” driver instead.