Thanks for this info. It helps a lot. It's frustrating the Microsoft is now requiring it, but has provided any documentation. Do you know if it is possible to use the same APO and INF for Win 8.1 and prior versions of Windows? I'm hoping I can take existing LFXs/GFXs and do the following: 1. Add support for the new interfaces in the APOs 2. Register both the LFX/GFX and SFX/MFX in the INF Or, do we have to have separate APOs and INFs for Win 8.1? Leonard From: wdmaudiodev-bounce@xxxxxxxxxxxxx [mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of Matthew van Eerde Sent: Friday, May 9, 2014 11:46 AM To: wdmaudiodev@xxxxxxxxxxxxx Subject: [wdmaudiodev] Re: SFX, MFX, EFX There is no whitepaper or anything, but you can look at the "Microsoft slate system virtual audio device driver sample" http://code.msdn.microsoft.com/windowshardware/slate-system-virtual-audio-f2 41062f as a sample. New .inf directives: PKEY_FX_StreamEffectClsid PKEY_FX_ModeEffectClsid PKEY_FX_EndpointEffectClsid PKEY_SFX_ProcessingModes_Supported_For_Streaming PKEY_MFX_ProcessingModes_Supported_For_Streaming PKEY_EFX_ProcessingModes_Supported_For_Streaming New APO interfaces: IAudioProcessingObject::Initialize now takes an APOInitSystemEffects2 IAudioSystemEffects2::GetEffectsList New KS properties: KSPROPSETID_AudioSignalProcessing / KSPROPERTY_AUDIOSIGNALPROCESSING_MODES This calls into a new portcls miniport interface: IMiniportAudioSignalProcessing::GetModes KSPROPSETID_AudioEffectsDiscovery / KSPROPERTY_AUDIOEFFECTSDISCOVERY_EFFECTSLIST