|
sAPO Failure Monitoring and Automatic Disabling
|
| bet | 22/28 | | Sana | 22.07.2021 | | Hajmi | 0.57 Mb. | | #15720 |
The audio system monitors sAPO return codes to determine whether sAPOs are being successfully incorporated into the graph. It does so by tracking the HRESULT values that are returned by any of several designated methods. The system maintains a failure count value for each sAPO that is being incorporated into the graph, typically an LFX and a GFX sAPO. A single registry value, PKEY_Endpoint_Disable_SysFx, disables both sAPOs when it is set.
The system increments an sAPO's failure count each time one of the designated methods fails. Certain failure codes might be excluded from this count.
If an sAPO indicates that it has been successfully incorporated into the graph, its failure count is reset to zero.
If the failure count for either sAPO reaches a system-specified limit, both sAPOs are disabled by setting PKEY_Endpoint_Disable_SysFx. Currently, this limit is set to 10, but that might change in the future.
The system monitors four primary API calls:
CoCreateInstance: The attempt to create an sAPO can fail for a number of reasons, including:
The graph is running protected content, and the sAPO is not properly signed.
The sAPO is not registered.
The sAPO has been renamed or tampered with.
IsInputFormatSupported/IsOutputFormatSupported: The system increments the sAPO's failure count if either method returns a failure code.
LockForProcess. If this call is successful, the sAPO failure count is reset to zero. Otherwise, the failure count is incremented.
|
| |
