top of page
Writer's picturedwomjuneroty

Behringer Driver Asio: Benefits and Drawbacks of Using a Third-Party Driver



It comes with sparse documentation, and no CD. The guy at the store told me it all had to be downloaded. At the site one finds the importat ASIO drivers (I got the 64 bit ones), and asio4all, as well as audacity (the last two can be found in many other places). Now, it is likely the device will produce no sound when first plugged. I found valuable advice on a review at amazon.com, author Mr. S. Bailey which I copy and rewrite a little.


If you are JUST getting into recording and want to dabble, this may be a good cheap solution (hint: there are generic ones that use the same hardware for a lot less than behringer brand and they are all equally crappy so get the cheap one just called Guitar Link). However if you expect anything of quality, look elsewhere, the amount of headaches just to get this thing functioning is not worth the savings and you will never produce quality recordinngs from this anyway.




Behringer Driver Asio




I wound up just throwing this behringer inteface in the trash and bought a Good interface for $150.This behringer is pure junk. after trying to get it to work right on SEVERAL software programsand failing i gave up on it There is a reason it is only $30 compared to other guitar interfaces that are $100 and up.


Without boring you with details, Behringer offers the generic ASIO4ALL driver for use with this product. However, with this generic driver the interface was working very badly (failed at 128 samples, high latency, pops and cutouts, unreliable).


After much pain checking and upgrading everything on his laptop, I now highly recommend the Behringer driver for a different model available in both 32 and 64 bit format under the heading "Behringer USB ASIO Drivers (For Zenyx Q502USB, Q802USB & Q1002USB Small Mixers)" at this web page:


Uninstall ASIO4ALL. Install this replacement driver then experiment with the settings from within Jamulus. You should be able to achieve much less latency and enjoy a reliable sound. This two input interface is now a good choice for use with Jamulus.


It did for me (thanks Laurent!). I uninstalled the Asio4All drivers and installed the 64bit version of the drivers Laurent said to use and bang, everything just worked. Note: make sure the audio interface is unplugged before you start the new driver installation, the software will prompt you to plug it in during installation and then prompt you to unplug it and plug back in once again. So you'll need to pay attention to the screen during the driver installation.


Hi guys. My friend just bought Behringer UMC22 but hasn't been able to get any sound coming into Jamulus (fader is set to the midde so should hear something). I had him try installing the Asio4All drivers but that didn't help so have told him to uninstall those and install these other drivers mentioned above. The thing I find odd is that when you go into the sound settings on his PC (Windows 8.1) it shows the Behringer is using some generic drivers, not Asio4All. Anyway, I'll have him uninstall them and install this new driver and see what happens.


Interesting - I have a friend who purchased the UMC22. We tried with both the ASIO4ALL / native win10 ASIO drivers, and the other behringer driver listed earlier in this thread. In both cases, we were only able to get audio from either the mic OR the guitar input to get into jamulus. Testing with Reaper, both are active simultaneously in both scenarios.


His Jamulus client shows activity from BOTH inputs simultaneously on the level meters (with different signals) when using the ASIO4ALL driver approach, but what arrives at the server is missing the left channel. I checked recordings at the server side of sessions with him in MONO, MONO-STEREO, and STEREO input modes, and in each case, the audio from the left channel is missing, even though his level meters show activity for both channels.


I had first installed the most recent driver (UMC -Driver_4-59-0). It worked immediately with Jamulus but the latency was disappointing (i.e. almost no difference with the direct analog connection of the micriphone to the PC plus built-iin Realtek soundcard plus ASIO4ALL) as you had predicted ...


I would like to share with you my experience on Behringer UMC22. Me and my bandmates have been jamming with Jamulus for many months now and I had experimented with many issues from latency to OS, interfaces, drivers compatibility etc and have finally stablized all the variables that affected us at the beginning. So I do get some reasonable understanding on making Jamulus to work. One of my bandmate is using the UMC22. When I started installing him with the ASIO4ALL driver as specified by Behringer, it did not work. Then by trial and error, I discovered that it simply would not support buffer size less than 256. I believe this is due to cheaper electronics on a cheaper product. I uninstalled ASIO4ALL on his Win10 computer and switched it to the other Behringer driver as mentioned also in this post. It works with Jamulus but because that Behringer GUI setting does not let you choose the buffer size, you have no idea what was used. I believe it automatically set to 256 or higher to support the cheap interface as a default. My conclusion is that as long as you use the UMC22 with a higher buffer size it will work at the penalty of larger latency. With that understanding, one properly can also go back to ASIO4ALL and manually set the buffer size to 256 or above to prove that it will work with Jamulus as well. That's my 2 cent.


vMix 16 and higher now support the ASIO audio driver, which provides the ability to receive and sendmultiple channels of digital audio through supported devices. What is ASIO? ASIO stands for Audio Stream Input/Output which is an audio driver standard developed by Steinberg, who are mostly knownfor their Cubase music software. ASIO is handy because it allows programs like vMix direct access to a lot of audio hardware without having to rely on the audio support available in Windows. For example, Windows drivers are usually limited to the first two channels of audio and can also increase the delay (or latency). How can ASIO be used in vMix? 1. Input Let's say you have a ASIO compatible USB audio box that provides 4 Microphone inputsFor example the UMC404 by Behringer =P0AZN You can connect up to 4 Microphones, and then add each of these as separate inputs in vMix by clickingAdd Input, clicking the Audio tab and then selecting the device from the list.You will then be given a number of channels to pick from, numbered and labelled to match the connectors on the device. 2. Output You can also send out multiple audio outputs to ASIO in vMix by clicking Settings then the Audio Outputs tabvMix supports four stereo outputs, Headphones, Master, A and B. Can multiple inputs and outputs be used at the same time? Yes, this is one of the capabilities of ASIO, and vMix fully supports it. Are only USB devices supported? No, pretty much any ASIO device will work with vMix, including audio mixers such as the Behringer X32, networked audio, Dante Virtual Soundcard software and more!


A couple of things: Firstly, you aren't running Behringer's ASIO driver - you are running ASIO4ALL which is a completely different kettle of fish. If you've installed the Behringer 64-bit driver package, you should have, as well as the ASIO4ALL driver, the actual Behringer one, and that's the one you should be using; it should be in the same list as ASIO4ALL - just select that instead.


I did a bit of checking - seems that there's a lot of discontent about this. Behringer removed the original ASIO driver and replaced it with the ASIO4ALL one which is rather less satisfactory - mainly because it's not really a driver but an interface to the 'normal' Windows driver. Somebody's done some research though and found the original driver that was removed, and posted it elsewhere. Now I can't tell you absolutely that you should try this - but I have to say that I can't see what harm it will do either. Anyway, the link to it is here: Behringer 64-bit ASIO driver If it works okay, it will be a lot better than what looks like a half-working ASIO4ALL one.


Incidentally, there's nothing actually wrong with ASIO4ALL - for many situations it's a useful driver because it provides diagnostics. But it certainly doesn't come from Behringer... ASIO4ALL homepage


However, if you have certain interfaces, we are excited to let you know that it is possible to share the audio drivers.This is a growing list of compatible interfaces to help windows users navigate the complicated world of Audio drivers on Windows.


If you want to be able to share the audio device between Source-Connect and other DAW or Audio programs on Windows, it is imperative that you download the latest driver provided by the manufacturer of that interface. Do NOT use the one provided by Windows automatically when you connect your device, as that one is unlikely to allow sharing between programs.


Here is a list of Audio devices and interfaces that provide a true multi-client USB audio driver that allows sharing between Windows programs. This will make it much easier when you are recording a backup of your voice-over session and running Source-Connect at the same time. 2ff7e9595c


0 views0 comments

Recent Posts

See All

Comments


bottom of page