Audio Processing Object Installation

NTDEV
1

(admin note: moving to NTDEV)

Hello Everyone:

I am currently working with the SwapAPO sample from the Windows-driver-samples repository and have successfully built the APO using Visual Studio 2022, Windows 11. The DLL compiles correctly, and I have validated that the SwapAPO binaries are generated without issues.

However, i am facing a challenge in the next stage: installing the APO into the Windows audio system using an INF package.

Despite exploring the Microsoft documentation and existing sample INFs, I am unable to identify a clear, complete, or up-to-date INF example that demonstrates:

  • How an APO should be installed as a SoftwareComponent device

  • How to correctly register the ComponentIDs, AddComponent mapping, and AudioEngine\AudioProcessingObjects registry entries

  • How to attach the APO to a specific audio endpoint (via FxProperties)

  • How to test and validate the SwapAPO installation in Device Manager or through MMDevices

I also could not find a definitive INF file in the SwapAPO sample that can be used directly to install and test the APO. As a result, I am unsure of the correct procedure to deploy the APO on a test system.

Would you be able to provide:

  1. A reference INF that shows the recommended method for APO installation on current versions of Windows.

  2. Any updated guidelines or documentation for installing SoftwareComponent-based audio extension drivers.

  3. Clarification on the correct use of componentization (ComponentIDs / AddComponent) when installing an APO.

  4. Recommended steps for testing the APO with specific audio endpoints.

Any guidance or official reference material would be extremely helpful to move forward.

Thank you very much for your time and assistance. I look forward to your support.

Warm regards,
Surya.

2

It is quite true that APO installation is a confusing mess. Part of this comes from evolution of the Microsoft philosophy. Originally, when the new Audio Engine was introduced in Vista, Microsoft did not allow you to install an APO by itself. An APO was considered part of the hardware, and could only be installed as part of a complete driver package for an audio device. It was POSSIBLE to install an APO on existing hardware, but only through hackery. Why did they do this? Because one of the reasons they completely redesigned the audio subsystem was all the clever folks who released filter drivers to do both cute and stupid things. There were so many that latency grew unpredictable, which made it impossible to do professional audio stuff.

My understanding is that this philosophy has eased somewhat, so that they will now allow independent installation, but the mechanism is still not rigidly defined.

I recommend that you ask your question in the “wdmaudiodev” mailing list at https://www.freelists.org/list/wdmaudiodev . All the cool audio kids hang out there, including several extremely helpful members of the Microsoft audio team. It’s been quiet lately, but folks are out there.

3

Thank you very much for the detailed explanation — it really helped clarify both the historical background and the current state of APO installation. Your point about how APOs were originally tied to hardware drivers (to control latency and filter chaos) makes a lot of sense in hindsight.

I also appreciate the pointer to the wdmaudiodev mailing list. I’ll definitely check it out and post my questions there

Thanks again for taking the time to share your insight.