Voice Clarity Driver Timestamp Test on AC/DC-power Source
Test description
To guarantee Voice Clarity provides robust echo control, the capture and render timestamp jitter must be sufficiently small. In addition, microphone and speaker devices must be in the same clock domain and not present relative drift. This test ensures that the jitter in the capture and render timestamps, and the jitter between the render and capture timestamps, are within required limits. A significant deviation between speaker and microphone timestamps would indicate either excessive jitter or drift between microphone and speaker clocks.
Warning
This test requirement must be satisfied on all power modes where the Voice Clarity APO is used. Some user intervention to configure DUT power supply during the tests will be required for battery powered devices.
Test details
| Specifications |
|
| Platforms |
|
| Supported Releases |
|
| Expected run time (in minutes) | 5 |
| Category | Development |
| Timeout (in minutes) | 60 |
| Requires reboot | false |
| Requires special configuration | true |
| Type | automatic |
Test steps
- Configure the system to render and capture at the default time period.
- Render (default mode) and record (raw mode) several minutes of a full-scale tone at a fixed speaker gain (less than maximum to avoid activating speaker protection). The recording needs to be sufficiently long so it can capture drift between timestamps that may accumulate over time.
- Record both render and capture timestamp sequences. Discard an initial portion of timestamps to remove turn-on transients and to ensure timestamps have stabilized for analysis.
- Calculate capture and render first order differences to measure both capture and render timestamp jitter.
- Calculate the relative delay jitter.
Pass/Fail criteria
The first order difference of speaker timestamps and the first order difference of microphone timestamps must not exceed the threshold. The relative difference between microphone and speaker timestamps must not exceed the threshold.
Troubleshooting
- Verify that render and capture share the same clock domain.
- Verify that audio driver and CPU provide adequate real-time performance, with no glitches, gaps or dropouts.
- Verify that the device does not turn the screen off or go into sleep mode during the duration of the test.
If your failure mode is not included on this list, search the error code in MSDN.
For generic troubleshooting of HLK test failures, see Troubleshooting Windows HLK Test Failures and Troubleshooting System Fundamentals Testing.
More Information
Parameters
| Parameter Name | Parameter Description |
|---|
Additional Documentation
Tests in this feature area might have additional documentation, including prerequisites, setup, and troubleshooting information, that can be found in the following topic(s): - Device.Audio additional documentation and System.Fundamentals additional documentation.