question for moskus (ASIO vs EWDM)

  • Thread starter Thread starter ChorazaiM
  • Start date Start date
C

ChorazaiM

New member
Just noticing you're refering to using the ASIO drivers for your INCA88. The specs quote a lower latency with the EWDM driver though (1.5ms EWDM vs 3ms ASIO). Did you find it to be otherwise?
 
...last time I answer question pointed to moskus, he buzz my balls sink to the deepest ground of the ocean... I'm not gonna do that again... I promise... I promise... mercy.. mercy... mercy.... :eek:
 
[Enters stage]... "Thank you, James, for that kind introduction"...

ChorazaiM said:
Just noticing you're refering to using the ASIO drivers for your INCA88. The specs quote a lower latency with the EWDM driver though (1.5ms EWDM vs 3ms ASIO). Did you find it to be otherwise?
Click to expand...
To keep it short: Yes. It's possible to set the latency to 1.1 ms with ASIO-drivers (48 samples) and 1.0 ms (48 samples) with WDM-drivers. But to keep the latency down under 5 ms with WDM-drivers, I had to use 64 samples in the INCA Control Panel. That gave me 4.4 ms latency.

But with ASIO-drivers, I could get by with using 128 samples, which gave me 2.9 ms latency in Sonar (Cakewalk claims this is because WDM and ASIO measures latency different). And not only "lower" latency, but Sonar was so much more stable.

So I would say it's not about how low you can set the latency, but how low you can set it and still use Sonar the way you want it. I would suggest you try both, and see what works best for you.

:)
 
Well, after trying both, I was more or less forced to use the ASIO drivers - seems that with the EWDM drivers, my computer would reboot itself whenever more than 1 program tried to access the soundcard (such as passing a wave from SONAR to WAVELAB) - not very nice. ASIO however seems to be very stable. I don't like the naming of the inputs, but that's sheerly cosmetic and I can live with it :]
 
Strange, WDM is multiclient and ASIO is not. So it should be the other way around....

But try this: Options -> Audio -> Advanced, and tick the "Share drivers with other programs"-checkbox. :)
 
Tried that - the system would reboot both with sharing turned on or off. It could be some weird motherboard/soundcard issue, but switchign the driver helped. With EWDM for instance, if I was playing something in Winamp and tried to even open Sonar, the system would reboot. ASIO seems to have rectified this situation. Any ideas?
 
Well, I'm using EWDM-drivers too, and now that I'm thinking about it, my system would do what you describe IF I had set Windows to access the 1,2 outs directly. Using the (INCA88 1,2 WAVE-driver).

I solved the problem by selecting the INCA88 5.1 Surround WAVE Driver. I don't know if you can...
 
Hmmm - actually, that sounds plausible. I seem to recall the Maya also having selected outs besides the default 1,2. I'll have to ry that when I get home and see what happens - but, that being the case, wouldn't I have to change any other programs as well (such as Wavelab) to access outs other than the ones Sonar is using?
 
The only app I use that is allowed to directly access the outputs, is Sonar.
 
hmmm - seems you were right moskus - switching to the "4-Maya 44 6 ch wave" as the general output for windows allows me to use the ewdm drivers without sudden OS rebooting :)

have you by chance noticed any cpu usage difference between the asio & ewdm drivers?
 
WDM and ASIO-drivers have different way of measuring CPU-usage, so they're really not measured up against the other... That said, I haven't noticed any big difference between the two of them, only that maybe WDM is a liiiiitle bit more efficient....
 
You must log in or register to reply here.
Back
Top