I have some really good feedback to solve this problem from the Behringer users forum. It's long, but it appears to have the solution.
Hello Paul,
I had similar problems directly after buying the device and attaching it to my system. The problem here is obviously caused by multiple applications which use different bit depths and sample rates.
As far as I could research it, the device driver of the UMC usually converts different sample rates to the one which is set for the output channel. This is called sample rate conversion (SRC). I saw several postings on the net which state that this worked well until Microsoft rolled out the Windows 10 build 1803 spring patch. After this, the sample rate conversion was broken, the postings stated.
YouTube, for example, uses 44.1kHz sample rate while your DAW will probably use 192kHz. As the driver's SRC doesn't work anymore after Build 1803 got installed, it can't convert the rate of the 2nd application and thus, you won't be able to listen to it (if my assumption is correct - if not, please correct me directly).
I can't reproduce the pre-build1803 behaviour of the UMC404, because the patch already was installed on my system when I bought and attached the device.
What helped me to rid the problems completely was to set a fixed output playback sample rate of 44.1khz (24bit) in the Windows sound properties.
Open up the Windows sound properties control and chose the 'Playback' tab. Double click the input device you want to change (on my system, it's 'Line Out 1-2'). In the device properties, chose the 'Advanced' tab. You will see a drop down field with the setting '2 channel, xxbit, xxxxx Hz (xxxx quality)' or similar.
Click on the down-arrow right next to this drop down field - it will give you a list of possible bit depth / sample rate combinations. Chose '2 channels, 24bit, 44100 Hz' here, then click OK two times. Restart the system to close / initialize any opened application handles / drivers. Now, start your DAW and a YouTube video and examine if both sounds are played.
Hope this helps - please leave me a feedback here and tell me if it worked out, thanks.
This is not a driver problem alone, the problem here is in my humble opinion that MS changes a lot with every new Windows build (they publish those twice a year) and thus, breaks the funcionality of many hardware devices.
If one of the Behringer developers should read this - it would be awesome if you could test this driver for compatibility to Windows 10 Build 1803 and revise it. Thanks in advance for this!
Kind regards,
F
#5 by Fritz deVries on 2 Weeks Ago Fritz deVries's Avatar
Fritz deVries Fritz deVries is offline
Posts: 4
Hi,
I just wanted to give you an update.
I fiddled a bit more with the sound settings. I set them back to 192kHz in the Windows sound control. Then I started a Youtube video which ran fine. Now I started my DAW which stopped the vid immediately.
Youtube doesn't run at 44.1kHz but adopts the bit depth / sample rate of the system. In my case the DAW was the problem. It obviously sets it's own sample rate which breaks the video streaming.
I changed my DAW's standard sample rate to 192kHz, closed the DAW and the browser and started them again. Now both the video and the DAW run fine without any errors. I will leave the settings as they are and run a few recording tests but upto now everything looks ok.
So I guess the main cause of problems like these are imho just different sample rates in different applications. Change the sample rate and bit depth in your applications to the same setting as in the Windows control.
The UMC driver seems to be fine so far and runs smoothly with Windows 10 Build 1803.
Kind regards,
Fritz
#6 by Michael Lapke on 2 Weeks Ago Michael Lapke's Avatar
Michael Lapke Michael Lapke is offline
Posts: 1,669
- Marius Marzec wrote View Post
Can anyone from Behringer reacto to this? I have same problem. My previous interface was Tascam US 322 and its multiclient driver allowed to work in a DAW on Tascam's ASIO while being able to listen to Youtube, Soundcloud etc. without closing the DAW program, for quick referencing. Now I moved to UMC 202 HD and while sound quality is clearly superior, it's a giant leap backwards driver - wise. FIX THE DRIVERS.
I'll tell you this definitely isn't a problem with the ASIO4ALL driver designated to be used with our UMC204HD interfaces, as those are compatible with the latest builds of Windows 10. (including 1803)
I'd take a look at Fritz's comments above as he provides some accurate information on this topic. In addition I'll add the following:
When using only one audio program under Windows, the used driver decides the sample rate.
If the audio application uses the Windows Sound Devices driver part (browser, media player, etc.), then Windows decides the sample rate, as shown / pre-selected on the Sound settings panel of Windows.
If an audio application uses the (UMC) ASIO driver, this driver decides the sample rate.
In the special case where 2 applications want to access the same hardware (UMC output), it “could” work by default, but only if both applications (WDM and ASIO) are already set to the same sampling rate. But if they are not set to the same, then the ASIO driver will have priority and the other application (which is using the Windows driver model) will not work.
The reason is quite simple - an audio device such as an USB audio interface needs a clear defined sample rate to operate properly. If 2 different applications want to access it, the hardware would not know what to do, so an actively running ASIO-driver has generally priority. The UMC driver can NOT do sample rate conversion, and never has been able to in the past.
Also good to know:
Even when changing the sample rate inside a typical WDM application (such as Audacity), this will not affect the connected USB audio interface! The audio hardware will always be fed by the Windows sound device driver part. So, for example, when Audacity is set to 96 KHz, but at the Windows Sound panel is 48 kHz selected, Windows will do a sample rate conversion from 96 to 48 kHz and playback at 48 kHz via the USB audio interface. But this will not work for ASIO applications or when 2 different audio applications are running in parallel.
Hope this information is helpful to you and anyone else here in the forum trying to playback multiple audio sources from different audio programs to one dedicated audio interface.
Michael Lapke
Specialist, Community
MUSIC Tribe
BEHRINGER
#7 by Marius Marzec on 1 Week Ago Marius Marzec's Avatar
Marius Marzec Marius Marzec is offline
Posts: 2
Forget it guys. I just logged to say I've fixed but Fritz nailed the problem 10 out of 10.
If your soundcloud/youtube don't work when you have your sequencer up running U-Phoria's ASIO, the problem is the sample rate difference among various applications.
I just ran the "fix sound problems" and it auto - corrected the "non default" samplerate set in Windows to 44100 hz. Why it was set to other value before - Idk.
Thanks all for taking time to look into this and reply.
sinc747 wrote:Dave Edwards recently reported issues with the new UMC404HD drivers that may be causing your problem. Dave is an Administrator for the "World of Live Streaming" Facebook group. If you would like to join the group,
here is the link.
Here is his post on the driver issue...
"The latest Behringer UMC 404HD driver has issues. Not sure of why it was updated on Behringer's site but I installed it on a new system for a client and it presented itself in a different manner than any driver I had previously installed and because it would change they way we support our customers I decided to remove and install the previous version. Just to keep things consistent. I then removed the previous version from my system and installed the newest driver since I wanted to become familiar with the latest version and develop a support model for it. Unfortunately the driver would not install correctly and the was a yellow triangle on the listing in device manager. Unable to get the driver to resolve, I removed it and went back to the previously known good driver. Today during WOLS, Giles Warham mentioned that he had a problem getting the new driver to work on one of his systems as well. The driver installed completely for him but audio failed after 30 minutes or so and the only way to get the audio back was to change the Windows default back to the internal sound card and then switch back to the Behringer. So not totally sure what is going on but my recommendation is to use the driver version 3.29 and do not switch to the 4.38 version. I am sure it will get sorted out but for now I do not recommend the upgrade. I will upload driver 3.29 to the files section in case someone needs a copy."
Good luck!
- Tom
