Figure 4. Registry settings for Microsoft Audio Home Theater Effects
INF Files for sAPOs
This section shows examples from an INF that is used to install an sAPO. For readability, it is useful to define friendly names for the property store value names. For example:
; PropertyKeys
PKEY_FX_Association = "{D04E05A6-594B-4fb6-A80D-01AF5EED7D1D},0"
PKEY_FX_PreMixClsid = "{D04E05A6-594B-4fb6-A80D-01AF5EED7D1D},1"
PKEY_FX_PostMixClsid = "{D04E05A6-594B-4fb6-A80D-01AF5EED7D1D},2"
PKEY_FX_UiClsid = "{D04E05A6-594B-4fb6-A80D-01AF5EED7D1D},3"
PKEY_FriendlyName = "{ D04E05A6-594B-4fb6-A80D-01AF5EED7D1D },4"
The following example shows the INF text to add the keys and property values to the registry:
HKR,"FX\\0",%PKEY_FriendlyName%,,%FX_FriendlyName%
HKR,"FX\\0",%PKEY_FX_PreMixClsid%,,%FX_PREMIX_CLSID%
HKR,"FX\\0",%PKEY_FX_PostMixClsid%,,%FX_POSTMIX_CLSID%
HKR,"FX\\0",%PKEY_FX_UiClsid%,,%FX_UI_CLSID%
HKR,"FX\\0",%PKEY_FX_Association%,,%KSNODETYPE_ANY%
The final element of each line is a friendly name for the associated property store data. The exact values are defined elsewhere in the INF file, but not shown here.
It is possible to register multiple sAPOs by creating additional subkeys under FX and adding the sAPO's property store data to these keys. However, the names of the subkeys that contain the property store data must be sequential integers, starting with zero. The above example registers a single sAPO, so the property store data goes under FX\0. The code to register a second sAPO would look similar, but the data would go under FX\1, the third under FX\2, and so on.
|
