I just got the behringer UMC404HD. Works pretty well, especially for the price. I did the research after I had downloaded the drivers from Behringer. Engaged ASIO driver and did the new gear dance of try this, try that, and now have everything working. Got an email from Cakewalk on optimization and looked into what was said. Found the drop down tabs and went to my unit. In the driver section it told me to use the MME driver...??? I had always thought that that was not the way to go. Any thoughts? I may try the new settings when I get home just for the heck of it. Anybody here receive these odd requests on audio gear. MME?.......hhhhmmmm
MJ

Hi MJ!
 
I have 2 Behringer X32's. Whilst I share your reservations with MME drivers and have always used asio exclusively,  I have very recently discovered that the X32 WASAPI driver is far better than the asio driver under both win7 and win 10. Well worth a try.

Thanks Tenfold, I will try that when I get back to studio.
MJ

I though this was an ASIO compliant interface. did you do the set up like shown here ?
https://www.youtube.com/watch?v=eIXlkYdPfyk

chuckebaby
I though this was an ASIO compliant interface. did you do the set up like shown here ?
https://www.youtube.com/watch?v=eIXlkYdPfyk

 
Thanks to the very clever people on this forum I have recently discovered that all asio drivers are not created equal Chuck. My RME asio drivers are brilliant. My X32's are also asio compliant and have dedicated drivers, but I can't overstate how much more efficiently the wasapi driver performs. Wasapi has come a very long way.

tenfoot

chuckebaby
I though this was an ASIO compliant interface. did you do the set up like shown here ?
https://www.youtube.com/watch?v=eIXlkYdPfyk

 
Thanks to the very clever people on this forum I have recently discovered that all asio drivers are not created equal Chuck. My RME asio drivers are brilliant. My X32's are also asio compliant and have dedicated drivers, but I can't overstate how much more efficiently the wasapi driver performs. Wasapi has come a very long way.

oh man, I wasn't questioning your advise. hope it didn't seem like that.
I just thought it was an ASIO Complainant devise.
I was reading about this interface a few weeks ago because it seems like a good deal. and someone had mentioned they were using ASIO4ALL with it and a Behringer rep explained it uses a downloadable ASIO driver.
 
Didn't WASAPI just recently expand the driver in Windows 10 ?
So if he is using Windows 8 or lower, will that make a difference ?

chuckebaby

tenfoot

chuckebaby
I though this was an ASIO compliant interface. did you do the set up like shown here ?
https://www.youtube.com/watch?v=eIXlkYdPfyk

 
Thanks to the very clever people on this forum I have recently discovered that all asio drivers are not created equal Chuck. My RME asio drivers are brilliant. My X32's are also asio compliant and have dedicated drivers, but I can't overstate how much more efficiently the wasapi driver performs. Wasapi has come a very long way.

oh man, I wasn't questioning your advise. hope it didn't seem like that.
I just thought it was an ASIO Complainant devise.
I was reading about this interface a few weeks ago because it seems like a good deal. and someone had mentioned they were using ASIO4ALL with it and a Behringer rep explained it uses a downloadable ASIO driver.

Didn't think that at all Chuck....all good mate. Just adding to the pool of info:) The fact that alternate drivers could now compete with asio was news to me too.

what surprises me is that you've gotten productive results using it in Windows 7 (I see in your sig) I actually thought Microsoft improved the WASAPI driver in Windows 10 because I have tried it in the past with less than stellar results.
(I haven't upgraded to Windows 10 yet.)
really is an interesting topic.

chuckebaby
what surprises me is that you've gotten productive results using it in Windows 7 (I see in your sig) I actually thought Microsoft improved the WASAPI driver in Windows 10 because I have tried it in the past with less than stellar results.
(I haven't upgraded to Windows 10 yet.)
really is an interesting topic.

My studio DAW is running windows 10, which is where I was initially experimenting with the X32 - though it is not my recording interface of choice. That said, when I discovered the improvement under win 10 I loaded the wasapi driver on one of my live performance laptops running win7 and surprisingly the improvement was almost as impressive. To be honest it probably speaks as much to the questionable quality of the provided asio driver as much as it does to the improvement in windows core drivers.  Thread about it here if you are interested (Bitflippers post is particularly interesting):
 
http://forum.cakewalk.com...-drivers-m3493308.aspx
 

chuckebaby
what surprises me is that you've gotten productive results using it in Windows 7 (I see in your sig) I actually thought Microsoft improved the WASAPI driver in Windows 10 because I have tried it in the past with less than stellar results.
(I haven't upgraded to Windows 10 yet.)
really is an interesting topic.

I got good results in Vista and 7 using Wasapi with a Presonus/Cakewalk UA-101 interface. There was a rare bug in earlier versions of Sonar that meant if you used some ASIO drivers and loop recorded each successive pass through the loop was shortened by the ASIO latency resulting in silent gaps on playback.

The Wasapi driver fixed that and that particular Wasapi driver gave very similar performance to the ASIO one.