There is no supported method to create a standalone APO that attaches to arbitrary devices. That's contrary to the philosophy. The reasons for this are sound (so to speak). Prior to Vista, everyone and his brother was creating filter drivers to "add value" in the audio stream. The result was a disaster for critical audio applications. Filters fought with each other, and latency and throughput were unpredictable. Thus, that path is no longer allowed...
<soapbox> Which I still think is a *VERY* poor choice! Since the APOs work on buffers, much like a DMO or DirectX pluign, the issues of latency/throughput would ONLY be built into the algorithm/effects which the APO would be implementing, thus being a factor that implementors would only try to optimize. Of course there are less competent implementors, but lets face it, its not as if the APOs would be installed in a life support system, and besides there is nothing stopping incompetent driver developers from developing drivers that REALLY f*ck up your system, which again is no bigger deal than to uninstalling it (possibly in safe boot mode) and never touching the manufacturer again, even with a ten foot pole. The ability to add arbitrary APOs would bring SO much added value to Windows, and with a *supported* installation option, the end user would still be in full control of what he/she wants to put their audio through. I'm very sorry that Microsoft have taken such a very hard to understand (and uninformed IMHO) decision on this, making developers life's so much harder trying to accomplish things that would've been SO easy with an APO. Thank you. </soapbox> /Rob ****************** WDMAUDIODEV addresses: Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx Subscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=subscribe Unsubscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=unsubscribe Moderator: mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx URL to WDMAUDIODEV page: http://www.wdmaudiodev.com/