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 really want to configure this card to use with my ubuntu pc, otherwise i will have to go back to Windows. I am sure that it's even possible sometimes to use windows drivers for Linux systems, but this is too advanced for me alone..
You should not need JACK, audio interfaces supporting the USB audio standard (all versions) should work without you having to do anything. In fact, installing JACK may very well be the source of your problems. Usually it is the other way round: USB audio devices work on Linux out of the box while drivers are needed for Windows.
I need someone to help me out, I've been using the Behringer Uphoria UM2 Audio Interface for a few months now. I've learnt that the stock drivers (one's which are pre-installed on the device) are inferior to the drivers available on the Behringer's website (which actually redirects to AISO drivers).
So I've upgraded to those drivers and the audio quality is in fact quite better now but I've also discovered that Behringer used to have dedicated drivers for the UM2 earlier which worked much better and I see various people sharing links for those drivers and they say that they are very satisfied with them.
Now here's the problem, I've watched every youtube video out there which recommends these old dedicated drivers, visited every site which claims the same, but on trying the same, I saw no improvement. In fact I had a ton of stability issues, I couldn't switch between speakers and headphones, I could only record in two channels (first being my XLR Mic in INPUT 1 & second channel being empty as I have nothing connected to INPUT 2), not every app out there has an option to turn the channels to mono, so i had problems with my voice only being recorded on the left channel (Input 1). Needless to say, it ruined all of my experience so i had to switch back to AISO drivers.
My question is, are there anyone out there who's having similar issues? Are the old dedicated drivers really good than AISO ? Cause I've recorded similar audio clips and compared and they sounded exactly the same. Am I missing something? Cause I'm not 100% satisfied with the recording setup i currently have.
Edit : I've noticed people complaining about the same and that specific apps/games force the windows properties mic level to 100 which should actually be set to 54 by default as that's the 0 db point for the interface. By increasing it to 100, it boosts the audio via a software making the overall sound quality sound worse. I set it back to 54 and it sounds fine, but I'm still curious if people actually feel those old dedicated drivers still sound better than ASIO4ALL drivers.
I can not get audio into audacity. Audacity will not recognize the USB input from U-Control UCA222. I used it to transfer 25 reel to reel tapes about 3 years ago when the file was still working to MP3 files.
The problem is Windows. Win10 deleted Behringer USB Audio Driver 2.8.40. I can not find this file to correct the problem.No audio goes into Audacity but I can hear audio with head phones from UCA222. I need another device to transfer audio into Audacity.
As recommended by many there are old drivers for the Uphoria UM2 flying around to be exact "BEHRINGER_2902_X64_2.8.40" or 2909 Version 2.8.40. Those are said to help out and deliver proprietary ASIO drivers. For me they only delivered worse audio since there were hissing, static and cracking/crackling noises. I wanted to uninstall them but whatever I tried the previously "USB Audio CODEC" device stayed as "BEHRINGER USB AUDIO WDM".
I once had a similar problem, and if i recall it right, uninstalling the Asio4all driver indeed helped.
At least this is something you could try quite easily. (not having the UMC and ASIO4ALL installed at the same time)
As Nemanja and others have pointed out, Behringer makes a dedicated driver for their UMC interfaces. Best of all, they are one of the manufacturers that actually make the effort to insure they have up to date drivers that keep their products working as designed with OS updates when MS publishes them, where appropriate. The link to the driver Download Center is HERE. You will have to set the appropriate filters 'Product Groups > Audio Interfaces, the driver for the UMC404HD should be on the first page.
Now with respect to the Behringer driver and ASIO4All: My personal opinion is to use the Behringer driver. I have used the ASIO4All and three or four other ASIO drivers (covered elsewhere in the Community) but the Behringer driver is the easiest to configure, works seamlessly with their audio interface, and easy to manage in Windows if necessary. Using the other ASIO drivers require a better working knowledge of how to manage them in Windows, and depending how many different ASIO driver manufacturers you are trying to manage, it can get very challenging (in Windows). My advise would be to uninstall any ASIO drivers you may have installed and then install the Behringer driver only which should keep it simple.
aa06259810