XDSP Errors
This topic lists the errors that can be returned by any of the XDSP APIs.| HRESULT | Message ID | Error Text |
|---|---|---|
| 0x8AC810A0 | XDSP_E_QUEUE_FULL | The command queue is full. Please wait a sufficient amount of time for the hardware to finish processing the current submitted commands before submitting more. |
| 0x8AC810A1 | XDSP_E_PENDING_RESULTS | The XDspStream was deactivated before all results from submitted commands were received. Please wait a sufficient amount of time for the hardware to finish processing the submitted commands of the stream before deactivating the stream. |
| 0x8AC810A2 | XDSP_E_NO_DEVICE_RESOURCES | No XDSP device resources are available to service your request. |
| 0x8AC810A3 | XDSP_E_DEVICE_FATAL_ERROR | A fatal error has occurred (eg. crash/hang) for the currently processed command. Please check the XDspStatus structure to understand which command sequence has failed. The hardware has an auto-recovery mechanism that will allow subsequent commands to continue being processed. |
| 0x8AC810A4 | XDSP_E_NOT_ALL_HANDLES_DEACTIVATED | XDspDisconnect was called on an XDspClient before all XDspStream objects associated with the client have been deactivated. |
| 0x8AC810A5 | XDSP_E_MAX_CLIENTS_EXCEEDED | The maximum number of XDspClients have already been created. |
| 0x8AC810A6 | XDSP_E_MAX_AGGREGATE_IMPULSE_RESPONSE_EXCEEDED | The current XDspConnect call will cause XDSP to exceed the maximum supported aggregate impulse response length, and is therefore invalid. |
| 0x8AC810A7 | XDSP_E_INVALID_IMPULSE_RESPONSE_LENGTH | XDspActivate was called with an impulse response length that is either too large or too small. |
| 0x80070057 | E_INVALIDARG | An invalid argument was supplied. |
| 0x80004003 | E_POINTER | An invalid pointer was supplied. |
| 0x8007000E | E_OUTOFMEMORY | There is no memory remaining to service your request. |
| 0x8000FFFF | E_UNEXPECTED | An unexpected error has occurred. |