
I want to know if the 404HD does this as well (with less output ports off course)? Because I want an audio interface with which I can record multiple tracks at the same time in a DAW.
Moderators: MattKingUSA, khz

So it seems to be a class compliant device and should work with Linux.Mac OS X operating system: No drivers needed, your U-Phoria interface operates class-compliant.
Thanks. If I'm not mistaken then the UMC204 was supposed to be class complient too. Some people however have problems w/ it. Same thing goes for the (discontinued) UMC404 (notice the omission of the "HD"). Firmware upgrades etc. changed the way that the device was reported to Linux (i.e. as "generic" instead of a proper unique name). That meant that ALSA couldn't load a driver for it.AutoStatic wrote:From the manual:So it seems to be a class compliant device and should work with Linux.Mac OS X operating system: No drivers needed, your U-Phoria interface operates class-compliant.
Thanks!asbak wrote:My UMC404 (not the HD model) works fine in Linux. For what it's worth, I did firmware update it in Windows but cannot remember what version was flashed to it.
I suspect that what's being referred to here is issues with Dbus / jackdbus. In the past I had so many problems with it myself that I ended up throwing it out by getting rid of the Ubuntu supplied jack2 and recompiling it from source without dbus support. Since doing that my systems have worked a lot more reliably. Note that Cadence will stop working because it requires jackdbus.The root problem is the JACK server itself which seems to not stop properly if you press the STOP button at the QJackCtl panel.
That jackdbus autospawning thingy had me puzzeld for a while too. Seemed impossible to kill Jack. If I want to stop Jack I always run:asbak wrote:Thanks for the link, Linuxmusician01. I'm a bit surprised about that user's problems because I would have thought that the firmwares in use on the 204 and 404 would be very similar. There are so many variables which come into play that it's difficult to draw a conclusion based on one user's issues.
If there were more reports it would have been possible to draw conclusions with more certainty as to whether there is really a problem or not with the audio interface, as opposed to how the workstation/s are configured.
I noticed this statement from the Behringer support guy:I suspect that what's being referred to here is issues with Dbus / jackdbus. In the past I had so many problems with it myself that I ended up throwing it out by getting rid of the Ubuntu supplied jack2 and recompiling it from source without dbus support. Since doing that my systems have worked a lot more reliably. Note that Cadence will stop working because it requires jackdbus.The root problem is the JACK server itself which seems to not stop properly if you press the STOP button at the QJackCtl panel.
Code: Select all
pkill -9 jackdbus
killall jackd
I actually received the 404HD two days ago. Connected it to my laptop (no ext. power adapter needed!) and it presented itself to JackAudio as a USB sound card/device w/ 4 separate IN and OUT ports. No problem. Some say that using the 404HD to monitor output (headphones?) does not work. I still have to test that yet. I'm experimenting w/ the insert ports for effect (stomp) boxes (works fine by the way too). I primarily use it as an analogue mixer at the moment.sysrqer wrote:So did anyone actually buy one of these? I'm looking at the UMC202HD.


What is an xrun and how do I check that?sysrqer wrote:That's great news Linuxmusician01, thanks for the information. How about xruns, is it stable etc?
Xrun is when you hear a pop or dropout in the sound, if you're recording audio and one happens it means that the drop out will be recorded. Qjackctl and cadence have counters for them, and I think ardour creates markers when they happen. Sometimes they are not too much of a concern and can be pretty much silent but generally you want to avoid them.Linuxmusician01 wrote: What is an xrun and how do I check that?
Do Mixbus and/or Ardour work without the Behringer 404HD device attached?basstrombone wrote:Greetings everybody,
My question here is related with running Ardour and Mixbus. I've recently bought a Behringer's UMC404HD. Differently from what I've seen around, Jack recognizes the interface, Alsa Mixer too (altough it is not on the top of the list). I can see the device under Alsa Mixer etc. I can start Jack and make all adjustments, but when I load either Ardour or MixBus, starts but sytem becomes quite unstable, no sound etc.
I have tried many things (e.g. running MixBus under Alsa>Jack etc.) But it doesn't work at all.
I've tried the Unity under Windows and it runs fine. While Installing MixBus I've got couple messages regarding processor scaling systems governor to be set as " performance" which I did (I'll try to load pics here).
But despite all the adjustments done, seems that the system and the interface are not getting along too well...
Most the time MixBus doesn't run at all... but even when I make it work, I can't record, play anything. Same with Ardour.
I've installed 17.10 then formated the HD and installed 16.04 and in both systems I could not make MB nor Ardour to run.
[enter image description here][1]
[1]: https://i.stack.imgur.com/n1x4I.png (ALSA MIXER)
Well I hope I have provided engough information. I don't know if it is an ALSA, OR the Interface problem (Behringer says that it is USB compliant and runs OTB with Mac OS) but did not work for me at all
Please let me know if need to provide more info ok?
Thanks before hand,
Cheers,
Alex