e-t172 skrev:
Installation is not really a problem. You just need to develop some trivial application which will allow the user to choose which audio devices he wants to use with the APO. Then it's just a matter of replacing two registry values and restarting a service. I even think it's possible to call the original APO (the one bundled with the audio device driver) inside the new APO, which means the original filter would still be available to the user along with the new filter.
I'm also interested in developing a standalone sAPO, and I've had the same idea to have a configuration app to let the user choose which audio devices should use the sAPO, exactly as you describe. I definitely think it can be "hacked" to work, but the real big issue will be WHQL signing. The audio server won't load a sAPO which isn't WHQL signed (at least on 64-bit systems?), and to get it signed it would need to be part of a driver package, which incidentally the standalone sAPO isn't. Not sure how to get around that, or if it is possible at all... /R ****************** 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/