Audio Device Testing Prerequisites
This section describes the tasks that you must complete before you test an audio device by using the Windows Hardware Lab Kit (Windows HLK):
Hardware requirements
The following hardware is required for testing an audio device. You might need additional hardware if the test device provides bus-specific support. To determine whether additional hardware requirements apply, see the test description for each bus-specific test.
Two test computers. These test computers must meet the Windows HLK prerequisites and must be included in the same computer pool. For more information, see Windows HLK Prerequisites. If the device being tested is a Bluetooth audio device, you need one of the test computers to include a Bluetooth radio, or you must have a Bluetooth controller adapter installed or connected to one of the test computers.
One audio device to be tested.
For in-air tests, a microphone or another active source for audio capture.
Note
For in-air tests, a microphone or another active capture source (such as an S/PDIF cable that is attached to an audio/video receiver that is actively playing back audio) must be attached to all capture endpoints. In addition, speakers or headphones must be attached to all render endpoints.
A sound playback device (speakers or headphones).
An Audio Precision System Two analyzer. This is required when the Fidelity Test is run and a host computer (x86 or AMD64 based) is used for communication during that test.
An audio loopback cable.
Note
For loopback tests, loopback cables must be plugged into all jacks under testing. This links the render jacks to the capture jacks.
Warning
All audio devices must be plugged in during audio testing.
The following diagram shows how to configure your hardware for Device.Audio testing.
This configuration is specifically required to complete the Audio Fidelity test; however, all other audio tests can be completed without changes to this setup.
Note
To certify your product for use on servers, the test computer must support four processors and a minimum of 1 GB of RAM. These system capabilities are required to test the Rebalance, D3 State, and Multiple Processor Group functionality of the device and driver. You do not need a computer that actually has more than 64 processors to test your device. Additionally, the server system(s) being used for device or driver testing must have Server Core installed prior to testing. For more information see Windows Server Installation Options.
If you use a pool of test computers to test devices, at least one computer in the pool must contain four processors and a minimum of 1 GB of RAM. Additionally, that computer must contain the device and the driver that you want to test. As long as the driver is the same on all the computers in the pool, the system creates a schedule to run against all test computers.
For tests that do not include a driver to test, such as hard disk drive tests, the Windows HLK scheduler constrains the tests that validate the device's and driver's Rebalance, D3 State and Multiple Processor Groups functionality to run on the default test computer. You must manually configure this computer to have multiple processor groups. The default computer is the first test computer in the list. Test personnel must make sure that the first test computer in the list meets the minimum hardware requirements.
Note
Except for para-virtualization drivers (as defined by the WHCP Policies and Processes document), you may not use any form of virtualization when you test physical devices and their associated drivers for server certification or signature. All virtualization products do not support the underlying functionality that is required to pass the tests that relate to multiple processor groups, device power management, device PCI functionality, and other tests.
Note
Multiple Processor Groups Setting You must set the value for the processor group size for Hardware Lab Kit testing of Windows Server 2008 R2 and later device drivers for certification. This is done by running bcdedit in an elevated command prompt window, using the /set option.
The commands for adding the group settings and restarting are as follows:
bcdedit.exe /set groupsize 2
bcdedit.exe /set groupaware on
shutdown.exe -r -t 0 -f
The commands for removing the group settings and rebooting are as follows:
bcdedit.exe /deletevalue groupsize
bcdedit.exe /deletevalue groupaware
shutdown.exe -r -t 0 -f
Note
Code Integrity Setting
The Virtualization Based Security feature (VBS) of Windows Server 2016 must be enabled using Server Manager first.
Once that has occurred, the following Registry key must be created and set:
HKLM\System\CurrentControlSet\Control\DeviceGuard
HypervisorEnforcedCodeIntegrity:REG_DWORD
0 or 1 (disabled, enabled)
Software requirements
The following software is required for testing an audio device:
The drivers for the test device.
The latest Windows HLK filters or updates.
Audio Precision System Two software
Note
The second computer is required to complete the Fidelity Test. However, if that test is run in Import log mode, the audio processor is not required.
Test computer configuration
To complete audio testing, you must configure two computers. The computer that includes the test audio device is referred to as the System under Test (SUT). The computer that receives audio communications from the SUT is referred to as the AP Host.
Note
The secondary computer must contain either an x86 or an AMD64 processor.
To configure the SUT for the testing of an audio device follow these steps:
If your SUT supports HDMI video and audio output capability, you SUT must be connected to an HDMI audio capable device such as an HDMI Monitor or an A/V Receiver.
Install the appropriate Windows operating system on the test computer and then configure the computer for your test network (the network that contains the Windows HLK Studio and Windows HLK Controller.
For an external audio device, install or attach the hardware to be tested on the test computer.
Install the manufacturer-supplied device driver, if you have to, on the test computer.
Set up the device configuration that is specified in the Fidelity Test.
Check that the capture device functions correctly on the test computer. If you are testing a Bluetooth audio device, verify that it is paired with the test computer.
Install the Windows HLK client application on the test computer.
By using Windows HLK Studio, create a machine pool and move the test computer to that pool.
To configure the AP Host for the testing of an audio device follow these steps:
Install the appropriate Windows operating system on the test computer and then configure the computer for your test network.
Install the Windows HLK client application on the test computer.
Using Windows HLK Studio, move the AP Host computer to the same machine pool that contains the test computer.
If the test computers include a third-party firewall, then the SUT and AP host must be configured as follows:
On the SUT there must be a firewall exclusion to allow the Fidelitytestapp.exe (located at <testbinroot>\nttest\multimediatest\avcore\audio\wdk) to receive incoming traffic on port 135.
On the AP Host, there must be a firewall exclusion to allow the dllhost.exe (located at <windir>\system32) to receive incoming traffic on port 135.
Make sure that the test computer is in the ready state before you begin your testing. If a test requires parameters to be set before it is run, a dialog box will be displayed for that test. Review the specific test topic for more information.
Some Windows HLK tests require user intervention. When running tests for a submission, it is a best practice to run the automated tests in a block separately from manual tests. This prevents a manual test from interrupting completion of an automated test.