Setting up a new computer with CbB. The PC has Realtek built-in sound, and that worked fine for a couple of days when I was just playing stuff back. But When I plugged in the audio interface to record, Cakewalk stopped playing sound. In Preferences Driver Settings, my only choice is "Realtek ASIO HD Audio. The Behringer does not show up at all, and no other ASIO, WDM or WASAPI drivers show up either. In Device Manager I have disabled the Nvidiia audio drivers. In the Windows sound control panel, the Behringer is listed as the default input and output. I have uninstalled the driver, rebooted and reinstalled the latest one. I have uninstalled Cakewalk and reinstalled.
Did you install the ASIO driver from the Behringer's support page under downloads? Sometimes it helps if you read the instructions or watch the video supplied with the products. Even the Sweetwater page has a ton of information about this interface.
Yes that's pretty important. Why on earth would they update to a broken driver? And how would any body know that as like @Larry Jones I can't find that info. And is this for your device only or for all in the series? But it might explain the OP's issue if they are using a bad version of the driver. Behringers drivers have always been a bit of a quandary. Like they even are recommending ASIo4all which is totally not needed any more because Windows uses WASAPI. Are they that out of touch with Windows?
Same here. Would note that after one of the recent recent minor Win10 upgrades, when I opened Cakewalk it had ASIO4ALL drivers showing in Options. I switched it back to the UMC404 ASIO drivers and all continues to work fine. Just pointing out that there may have been some "glitch" in recent minor upgrades from Microsoft that impacted Cakewalk, but for me not worth the time to figure it out and easy to remedy.
Thank you. Yes, I saw that readme. It just says "If you're using already one of the named interfaces without any trouble, there is no need to install this driver." Since the OP was setting up a new computer, I assume he did not have any driver installed, so the logical one to use would be the newest one, right?
Why on earth would they update to a broken driver? And how would any body know that as like @Larry Jones I can't find that info. And is this for your device only or for all in the series? But it might explain the OP's issue if they are using a bad version of the driver. Behringers drivers have always been a bit of a quandary...
Up to some point Behringer had an excellent high quality ASIO driver developed by Ploytec for most of their interfaces. Later on they replaced it quietly with something undefined, maybe their own driver, idk. So perhaps the license for the previous came to end at some point or maybe they parted ways for whatever reason. Anyway that's all I know, hope it can help understanding some of their decisions.
Uninstall and/or disable every audio device on your computer (including the old Behringer drivers). So for me that means I turn off the Realtek in the BIOS and I disable the nVidia HDMI audio device (and always use the custom option when upgrading so I can deselect the audio driver). After uninstalling all of this (and especially any ASIO4ALL instalations) be sure to clean reboot (without the audio interface connected). Then install the Behringer driver. Reconnect the device.
I tried all the available drivers from the Behringer website and none of them worked. When I was uninstalling I noticed that in the list of programs in Windows Control Panel, the Behringer driver was taking up no drive space at all - the size was listed as zero. I downloaded the latest driver one last time and as a last resort I excluded the setup file from my antivirus (McAfee). I've never had to do this before and I can't say if that's what did the trick but this time the driver installed and worked. One note: I have to use WASAPI. When I try to switch to ASIO CbB freezes and I have to close it to get back into Preferences.
Sad update: Not working again. When I went back to this today and plugged my bass into the Behringer interface, Cakewalk crashed. This is with the latest driver from Behringer's website. The previous driver didn't work for me, and the newest driver only allowed WASAPI, which I was happy to use (as long as it worked). Now I'm back to ground zero. Only thing I can think is that the old bad drivers are not getting completely removed in the "uninstall" process, but I don't knwo what I can do to fix that -- or even if that's the real problem. Thanks to all who tried to help me with this. (By the way, Behringer's online support is next to useless.) It's a great box, as long as you don't need any assistance from the manufacturer ?)
I'm trying to setup my Behringer UMC404HD with a Neewer NW-700 condenser microphone to my laptop (USB 3.0) running Windows 10 in Adobe Audition. I currently have my microphone plugged into input 1, phantom power switch on, all knobs pointing straight up (just used as a reference point), none of the buttons depressed, and nothing connected to the back of the unit besides the power and usb. I found a couple youtube videos on the setup, but I'm not getting the same result as them. I don't know if it's a new driver or my settings. See attached pictures for my current settings. Thank you in advance.
The UMC404 has an ASIO driver, and that's the one you should be using - it bypasses all that Windows rubbish completely. If you've downloaded the Windows driver from here: -Audio/Interfaces/UMC404HD/p/P0BK1/Downloads then what you need to do is select ASIO instead of MME. If you ever need to record all four channels at once, this is likely to be the only way you'll be able to do it - MME drivers are usually no more than stereo, and since they operate through the OS, you're at the mercy of M$ all the way.
If the hardware you are trying to run is compatible with Windows you are using, and it is very important to use this hardware, you should purchase a USB controller that uses a PCI port like this...
Note: I can't guarantee that this kind of product will work.
I have the same problem with a Gigabyte GA-Z97X-Gaming 5 motherboard with an AMD Ryzen 9 3900X. In the end I just installed a cheap 4 port PCIe USB 3 add-in card and everything now working fine.
I wonder what it is that is making a *UNIVERSAL* serial bus so incompatable?
The work around I have found to work perfectly so far in Reaper and Harrison Mixbus is to bypass the USB altogether and just use the LAN port and use this to set up the RTP MIDI protocal. -erichsen.de/software/rtpmidi.html
Thanks for this. I have the same problem with my Asrock x570m pro4 Mainboard. I can't install a PCIe card because I have only one slot wich is covered by the cooling blocks of my graphics card. Hey Asrock, great architecture !!! Maybe a riser would help, I have to figure this out.
This workaround helps me out. But unfortunately it takes away the possibility to switch the xtouch between X Air control and DAW control. The xctrl/MC Mode is not usable, because the X Air is controlled via Ethernet while the DAW MUST be connected via USB. Both via Ethernet is not possible.
So if you want to switch, you have to shut down the X-Touch and boot it (with pressed Select on Track 1) into the other mode. This is not acceptable. Is there any hope that this problem will be fixed?
MIDI has always been used as a standard combined with makie control and HUI emulation.
the USB 3.2 is backwards compatible with USB 2.0.
The latest intel processors have no such problems and even the previous ryzen generation only the new x570 motherboard so i think it's a chipset driver problem or BIOS.
Again, mixing boards are not meant to have midi. Some have them as an added bonus, but its not their main purpose. Midi is for synthesis. Controlling modular or soft/hardware synths. Midi is for controlling a daw. I could go on...
If Behringer Tech themselves mentioned there are compatibility issues doesn't that suggest that it is up to Behringer to come up with a driver that will make it compatible with AMD. Or at least cooperate with AMD to come up with a solution to the incompatibilities. That error you got can indicate incompatible hardware connected.
A couple of website mentioned to delete the Higher and Lower Filters in Registry to fix the problem such as these websites: windows 10 - USB Driver - This device cannot start. (Code 10) - Insufficient system resources exist ...
Finally this website APPAULS give some similar tips on resolving the same error: Fix: Insufficient System Resources Exist to Complete the Api Xbox Controller - Appuals.com (Note: Don't download their "Recommended" Software to fix. it is basically a scam but the info is legit).
I'm using the latest driver and bios. I tried several workarounds in the registry (found online). Plugged a usb hub. Nothing worked. Also a new installation of windows 10 pro doesn't work because I had the windows 10 pro "n" (no media pack) version. (Then I plugged the controller as the first usb device). Still no success.
Good news! I bought a delock pci-x usb 3.0 controller and it works with my Qcon Icon Pro X controller. I don't even had to install any drivers for the USB controller. I just plugged my Icon Pro X and it works instantly. No USB code 10 error anymore.
Just chiming in to say I have the same issue. Asus TUF x570 motherboard, AMD Ryzen 3900X and Behringer X-Touch One. None of the USB ports worked. Upgraded from an Asus TUF 450 board with an older Ryzen CPU and didn't have any issues.
c80f0f1006