On 17/06/2010 22:23, Robert Bielik wrote:
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...
The signing policy for APOs is not the same as the policy for drivers.If you want to use an unsigned APO, you just need to write a registry value [1] which will disable the Audio engine "Secure mode". This means you won't be able to play encrypted Audio (i.e. Blu-ray) anymore, but most people can live with that. Of course the user should be informed of this alteration when installing the APO.
Once Secure mode is disabled, you're free. You can use any valid DLL as an APO, signed or unsigned. This is true even for x64 systems. I verified it on my own system when testing the APO samples.
[1] http://social.msdn.microsoft.com/Forums/en/mediafoundationdevelopment/thread/b16a608b-18e3-44aa-af5c-6be678e4db98
-- Etienne Dechamps / e-t172 - AKE Group Phone: +33 6 20 41 09 29
