Form MS documentation:
"The registration of the APO with the audio engine is done using a newly
created APO device. For the audio engine to make use of the new APO device
it must be a PNP child of the audio device, sibling of the audio endpoints.
The new componentized APO design does not allow for an APO to be registered
globally and used by multiple different drivers. Each driver must register
its own APO's."
https://docs.microsoft.com/en-us/windows-hardware/drivers/audio/implementing-audio-processing-objects
And the documentation also states that a system supplied APO can be
replaced by a custom APO
Considering that, what's the difference between an APO being registered
globally and a system supplied APO being replaced?
On Mon, Dec 21, 2020 at 2:01 PM Danijel Domazet <danijel.domazet@xxxxxxxxx>
wrote:
Hi wmdaudiodev,
I am looking for a consultant who could help me with setting up an APO
development.
What I need to do is the following:
1 - Build an example SwapAPO.dll from the Microsoft SYSVAD official
example audio driver
2 - Register SwapAPO on my local system
3 - Modify the registry keys to replace the existing system APOs with
SwapAPO
4 - Attach debugger to "audiodg.exe" process and place a breakpoint in
the SwapAPO.dll
(Repository is here:
https://github.com/microsoft/Windows-driver-samples/tree/master/audio/sysvad
.)
This would enable me to build my own APO in the future, basing it on
the SwapAPO example.
Please shoot me a private message if you think you could lead me to
achieve the above in one or two online screen-sharing sessions. Please
have in mind that I have already done step 1 and 4, so focus should be
on steps 2 and 3.
Cheers!
Danijel Domazet
******************
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/
