No, that's not correct. The LFX, GFX, and GUI are all registered under
the same FX subkey, but with different property IDs (a property ID is a
combination of a GUID and an integer index value). It's not clear from
the SysFX document what purpose multiple APOs for the same endpoint
would be. Elsewhere in the same document (on page 4) the following is
"Each Plug and Play hardware ID can be associated with only one GFX and one LFX sAPO."
I don't think this is referring to multiple endpoints within the same Hardware ID, since each of them would get installed as "FX\0" for each endpoint. Sounds like we need some clarification here...
Michael R. Preston wrote:
The more I've looked into wrapping the Microsoft APO, the more difficult I find it. Sure, Microsoft gives you examples on how to do it, but the manner in which it's supported is extremely limiting for the IHVs. I'm not sure about the multiple FX key issue from the APO standpoint, ...
My interpretation of the "multiple FX key" thing in the document is that you can have one subkey for the LFX, one subkey for the GFX, and one subkey for the configuration UI.
-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | Mike Preston | Home/Office: (360)756-1655 | | E-mail: mike@xxxxxxxxxxxxxxxxxxx | Cell: (360)303-9331 | |~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| | The man who follows the crowd will usually get no | | further than the crowd. The man who walks alone is | | likely to find himself in places no one has ever been. | | -- Alan Ashley-Pitt | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ******************
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/