Rick, I'm trying to figure out your POV as a programmer, what exactly is wrong with ASIO? (Just sparking friendly conversation)
Programmatically, it's not all that difficult to handle -- support wise, it can be a nightmare
It adds another layer of complexity to an already complex program. My theory is, the less things to break, the less they will, and make my life easier
I have a hard enough time explaining to some customers how to plug in a sound card, let alone set it up properly for ASIO!
If I have a customer call, and say they want to output each deck to a separate mixer channel, I can simply tell them to plug in two sound cards, change the deck outputs, and walla, everything works just dandy -- no drivers to load, no headaches tweaking ASIO settings, everything just works.
If MS adopted ASIO as it's standard sound driver, they would supply built in ones, which each manufacturer would have to handle, and code to, like WDM. Then I would be happy to utilize them, as it would be standard across sound cards.
Also, my software is not designed as a wiki-wiki, scratch type program, so I have no need for the extra features that ASIO allows.
Life is simple
