Device.Audio Requirements

Description: This APO must match all APO tests

Related Requirements

• Device.Audio.APO.MicArrayRawData
  
  
• Device.Audio.APO.WinPEConformance
  
  

Target Feature: Device.Audio.APO

Title: System effect in capture path provides RAW data from microphone array when requested by the client

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows RT
  
  
• Windows Server 2008 R2 (x64)
  
  
• Windows Server 2012
  
  

Description

If a microphone array processing algorithm is provided in a Windows system effect audio processing object (APO) instantiated in system effect local effect (LFX) insert point in capture path, it must provide all the individual audio streams from the array when a client asks for a format greater than one stream/channel. This allows the APO to provide hardware compensation processing and microphone array processing to the client that takes advantage of the entire APO but allows clients that rely on the microphone array processing that resides higher up in the audio subsystem to take advantage of hardware compensation in the APO but not the array processing in it.

Target Feature: Device.Audio.APO

Title: System effect APOs comply with Windows Protected Environment conformance and compliance criteria

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows RT
  
  
• Windows Server 2008 R2 (x64)
  
  
• Windows Server 2012
  
  

Description

Audio Processing Objects (APOs) that are loaded into the system effect infrastructure by the audio device driver INF must be signed with a certificate indicating conformance and compliance with the robustness rules of the Windows Protected Environment. This signature attribute is granted automatically as part of the submission process dependent on signing of the Test Agreements.

See Code Signing for Protected Media Components in Windows at http://go.microsoft.com/fwlink/?LinkId=70751.

Description: This Audio Controller must match all Audio Controller tests

Related Requirements

Device.Audio.AudioController.HDAudioVersionNumber

Device.Audio.AudioController.HDControllerCompliance

Target Feature: Device.Audio.AudioController

Title: HD Audio 1.0 compliant hardware sets appropriate registers to specify the version number

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows RT
  
  
• Windows Server 2008 R2 (x64)
  
  
• Windows Server 2012
  
  

Description

HD Audio hardware that complies with HD Audio specification version 1.0 must set the correct version number in the appropriate registers. The VMAJ and VMIN registers must specify a major version number of 01h and a minor version number of 00h.

Design Notes

In future HD Audio specification revisions the register values may be updated. It is assumed that any future requirements that reference an updated revision of the specification will also require using the VMAJ and VMIN registers defined by that revision of the specification.

Target Feature: Device.Audio.AudioController

Title: HD Audio controllers comply with the Intel HD Audio specification

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows RT
  
  
• Windows Server 2008 R2 (x64)
  
  
• Windows Server 2012
  
  

Description

An audio or modem controller must be implemented as an HD Audio controller (except where noted otherwise within this document). The controller must:

Be implemented according to Intel High Definition Audio Controller specification, Revision 1.0.

Be updated to comply with future specification revisions.

Comply with future HD Audio specification ECRs in accordance with policies around new hardware requirements.

Description: This Device must match all base tests.

Related Requirements

• Device.Audio.Base.AudioDriversSupportMute
  
  
• Device.Audio.Base.BasicDataFormats
  
  
• Device.Audio.Base.ChannelMasks
  
  
• Device.Audio.Base.DCOffset
  
  
• Device.Audio.Base.DevicesWorkWithoutExtraSoftware
  
  
• Device.Audio.Base.DigitalStreamsNoMixing
  
  
• Device.Audio.Base.DockingStation
  
  
• Device.Audio.Base.DRM
  
  
• Device.Audio.Base.EfficientBufferManagement
  
  
• Device.Audio.Base.ExposedAudioEndpointsAreFunctional
  
  
• Device.Audio.Base.Fidelity
  
  
• Device.Audio.Base.FullDuplexOperation
  
  
• Device.Audio.Base.HDAudioRemoveDevicePowerState
  
  
• Device.Audio.Base.IMiniportWaveRTStreamNotification
  
  
• Device.Audio.Base.IndependentInputOutputFormatSelection
  
  
• Device.Audio.Base.InitiatorTargetBlocktransferSupport
  
  
• Device.Audio.Base.JackConnectorStateDescription
  
  
• Device.Audio.Base.JackDetection
  
  
• Device.Audio.Base.KSPROPERTYAUDIOMIXLEVELTABLE
  
  
• Device.Audio.Base.KSPROPERTYAUDIOVOLUMELEVEL
  
  
• Device.Audio.Base.KSTopologyCompliance
  
  
• Device.Audio.Base.NoHiddenStreamRouting
  
  
• Device.Audio.Base.NoUncontrollableStreamRouting
  
  
• Device.Audio.Base.NoUndiscoverableDevice
  
  
• Device.Audio.Base.PCMNonPCMForSPDIF
  
  
• Device.Audio.Base.PowerManagement
  
  
• Device.Audio.Base.ProperUSBDescriptors
  
  
• Device.Audio.Base.RealtimeDriversSupportStandardLoopedStreaming
  
  
• Device.Audio.Base.ReportSupportedProperties
  
  
• Device.Audio.Base.RestartWithinASpecifiedDuration
  
  
• Device.Audio.Base.ResumeLatency
  
  
• Device.Audio.Base.SamplePositionAccuracy
  
  
• Device.Audio.Base.SamplingAccuracy
  
  
• Device.Audio.Base.TimeSynchronizedSampleRates
  
  
• Device.Audio.Base.TipRing
  
  
• Device.Audio.Base.TwoDMAEnginesAndConnections
  
  
• Device.Audio.Base.VoiceCommunicationUAA
  
  
• Device.Audio.Base.VolumeControlsIsLinear
  
  
• Device.Audio.Base.VolumeGranularity
  
  
• Device.Audio.Base.WAVEFORMATEXTENSIBLESupport
  
  
• Device.Audio.Base.WaveRTConformance
  
  
• Device.Audio.Base.WaveRTImplementation
  
  
• Device.Audio.Base.ZeroGlitch
  
  

Target Feature: Device.Audio.Base

Title: Audio drivers support mute

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows Server 2008 R2 (x64)
  
  
• Windows Server 2012
  
  
• Windows RT
  
  

Description

Any audio driver capable of supporting compressed format need to expose KSPROPERTY_AUDIO_MUTE.

Target Feature: Device.Audio.Base

Title: Audio subsystem supports basic data formats

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows RT
  
  
• Windows Server 2008 R2 (x64)
  
  
• Windows Server 2012
  
  

Description

When the Microsoft software sample rate conversion (SRC) is used, hardware SRC is not required. Windows provides software mixing and SRC, which eliminates the requirement for hardware to support multiple sample rates.

* Bluetooth HFP drivers that do not implement wideband speech are bound by the standard to support only 8 kHz. This is an accepted exception.

** Unless further specified by external specifications. For example, HDMI audio requires both 44.1 kHz and 48 kHz, and Bluetooth A2DP requires both 44.1 kHz and 48 kHz for a Bluetooth sink. Windows HCK tests may enforce these stricter specifications.

Support for other rates (8, 11.025, 16, 22.05, 32, 96, 192, and 384 kHz) in hardware is optional.

Design Notes

This requirement is valid for both input and output devices.

Target Feature: Device.Audio.Base

Title: Audio device that supports multichannel audio formats properly handles channel masks

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows RT
  
  
• Windows Server 2008 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows Server 2008 R2 (x64)
  
  

Description

If the audio device supports multichannel audio formats, the audio device driver must deal with channel masks consistent with the content and the current selected speaker configuration.

If supported, the device properly handles 5.1 and 7.1 PCM formats. The channels are routed to the proper analog lines, and these requirements apply for all the channels except LFE.

See the Audio Driver Support for Home Theater Speaker Configurations white paper at http://go.microsoft.com/fwlink/?LinkId=65430.

Target Feature: Device.Audio.Base

Title: Audio capture device DC offset is limited within range of + or - 0.15 on a scale from -1.0 to +1.0

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows RT
  
  

Description

Audio capture device DC offset is limited within range of + or - 0.15 on a scale from -1.0 to +1.0.

Target Feature: Device.Audio.Base

Title: Devices that work with UAA class drivers must support basic functionality without installing any additional software or drivers.

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows RT
  
  
• Windows Server 2008 R2 (x64)
  
  
• Windows Server 2012
  
  

Description

UAA audio devices must meet basic functionality requirements following a new Windows installation and prior to the installation of any additional software (drivers, system services or applications). When running exclusively with the built-in Windows support, audio devices as a minimum shall:

• Correctly render stereo sound from built-in speakers
  
  
• Correctly render mono sound from mono render devices
  
  
• Correctly transmit a stereo sound signal through line output connectors
  
  
• Correctly capture a stereo line-in signal
  
  
• Correctly capture a stereo mic-in signal
  
  
• Correctly capture a mono sound from mono capture devices
  
  
• Correctly support, Mute, Volume Control
  
  

Identical functionality must also be supported with any custom driver provided with the device.

If the physical design implements line-in and/or mic-in, then line-in and/or mic-in should work with class drivers in Windows.

Design Notes

This requirement checks the interaction of the UAA compatible devices with the class driver and insures it is equivalent on basic functionality to that provided by third party drivers.

UAA class drivers support:

1. HD Audio
   
   
   • High Definition Audio Specification Revision 1.0.
     
     
2. USB Audio 1.0
   
   
   • Universal Serial Bus Device Class Definition for Audio Devices Release 1.0
     
     
   • Universal Serial Bus Device Class Definition for Audio Data Formats Release 1.0
     
     
   • Universal Serial Bus Device Class Definition for Terminal Types Release 1.0
     
     
   • Universal Serial Bus Device Class Definition for MIDI Devices Release 1.0
     
     

Hardware mute and volume controls if implemented must be compatible with Windows class drivers. In particular:

• HD Audio hardware volume controls if implemented must be designed as amplifier widgets, and not as HD Audio volume knob widgets. See HD Audio spec sections 7.3.3.7 "Amplifier Gain/Mute", 7.3.4.10 "Amplifier Capabilities", and not 7.3.3.29 "Volume Knob".
  
  
• HD Audio mute is implemented many ways in the class driver. If an amplifier widget has the "mute capable" bit set, sending a mute control down must mute the signal path through that amplifier widget. See HD Audio spec sections 7.3.3.7 "Amplifier Gain/Mute" and 7.3.4.10 "Amplifier Capabilities". If a pin widget has "input capable" or "output capable" set, setting "input enable" or "output enable" to 0 must mute the signal path through that pin widget. See HD Audio spec sections 7.3.3.13 "Pin Widget Control" and 7.3.4.9 "Pin Capabilities". Setting "digital enable" bit to 0 on a digital converter must mute the signal path through that digital converter. See HD Audio spec sections 7.3.3.9 "Digital Converter Control" and 7.3.4.6 "Audio Widget Capabilities".
  
  
• USB hardware volume controls if implemented must be designed as the proper set of descriptors and associated command responses. Refer to USB Audio Specification 1.0, Mute Control and Volume Control as defined in sections 5.2.2.4.3.1 and 5.2.2.4.3.2.
  
  

Target Feature: Device.Audio.Base

Title: Audio sources are available as digital streams without analog mixing to the audio subsystem

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows RT
  
  
• Windows Server 2008 R2 (x64)
  
  
• Windows Server 2012
  
  

Description

Audio sources must be available as digital audio streams that are accessible to the system-wide kernel; that is, they must not rely exclusively on any analog mixing stage between the DAC converter and the speaker jack as the only means for output. Sources that continue to offer an analog mixing output configuration must also provide the user a configurable digital option.

One model for providing the user such an option is Windows support for CD music.

This requirement covers the following audio sources, which must be available digitally to USB speakers if attached:

• CD-ROM or DVD
  
  
• TV tuner
  
  
• FM radio
  
  
• Voice modem
  
  

PC Beep notifications are exempt from this requirement.

Design Notes

Analog microphone and line in with available analog-to-digital converters (ADCs) are digital-ready by definition. Devices for which the operating system supports emulation equivalents, such as hardware-accelerated 3-D and MIDI synthesis (Microsoft DirectSound 3D emulation and the Windows GS Wavetable SW Synth) are acceptable.

Target Feature: Device.Audio.Base

Title: Audio jacks on docking stations

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows RT
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows Server 2008 R2 (x64)
  
  
• Windows Server 2012
  
  

Description

Audio jacks on docking stations need to support the below three states:

1. The system is not plugged in to the dock:
   
   

The dock audio device should not appear in the Sound control panel at all.

1. The system is plugged in to the dock, but nothing is plugged into the jack:
   
   

The dock audio device should appear in the Sound control panel as "unplugged" (DEVICE_STATE_DISCONNECTED.)

1. The system is plugged in to the dock, and something is plugged into the jack:
   
   

The dock audio device should appear in the Sound control panel as "working" (DEVICE_STATE_ACTIVE.)

When the system is undocked and is using the HD Audio class driver, it is acceptable for devices on dock to show as unplugged.

Target Feature: Device.Audio.Base

Title: Audio device implements DRM support as defined in the Windows Driver Kit

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows RT
  
  
• Windows Server 2008 R2 (x64)
  
  
• Windows Server 2012
  
  

Description

Audio devices must comply with Windows trusted audio paths for digital rights management (DRM). Hardware that complies with Windows DRM supports DRM level 1300. The audio drivers must not call the DrmForwardContentToFileObject function.

The DRM requirement does not apply if the underlying device is a Bluetooth audio device.

Design Notes

See the "Digital Rights Management" topic in the Windows Driver Kit.

Target Feature: Device.Audio.Base

Title: PCI-based audio device supports efficient audio buffer management

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows RT
  
  
• Windows Server 2008 R2 (x64)
  
  
• Windows Server 2012
  
  

Description

The audio device must be able to fully function when the system can provide only single 4 KB pages of contiguous memory. In other words, the audio device can require many 4 KB pages of memory, but it must not require the largest block of contiguous memory to exceed one 4 KB page.

The audio device and associated device-specific driver must not introduce unnecessary latency. If the audio driver adds more than 2 ms of computational latency between buffer transfer and queuing for rendering, the driver must provide a programmatic method for a latency-sensitive application to temporarily disable the computation.

Target Feature: Device.Audio.Base

Title: Audio device must be functional (capable of capture/render) all the time while the system is powered on.

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows RT
  
  
• Windows Server 2008 R2 (x64)
  
  
• Windows Server 2012
  
  

Description

Exposed Audio Endpoints in a system must be functional (capable of capture/render) all the time while the system is powered on. Built-in speakers and microphones must work while the system is operational.

Exposed audio end points continue to function even during system state changes such as:

• while the power source changes from external to battery or vice versa
  
  
• while the GPU switches from a to b
  
  

Target Feature: Device.Audio.Base

Title: Audio solution delivers a minimum fidelity audio experience

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows RT
  
  

Description

Audio solution, either integrated or add-on discrete streaming audio device, must meet the following minimum fidelity audio requirements. Measurements are performed electronically via externally accessible jacks (not in-air) for all the below defined device types when they exist on the device/system. Frequency sweep and/or multi-tone test methods may be used when appropriate. The Device Types in the tables reflect those defined by the Intel HD Audio Spec and the Microsoft HD Audio Pin Configuration Programming Guidelines.

1. For codecs on systems regardless of voltage the full scale input and output full scale voltage requirement changes to >= 0.707 Vrms. Speaker output expected to be half into 8 Ohm for 3.3V codecs.
   
   
2. Reference level: 1Vrms. Full Scale is defined as a signal that contains samples at the maximum digital value. .
   
   
3. These are two examples. Testing will occur at these two endpoints and anywhere within this envelope. Smaller output voltages (>=120mVrms) are permitted when required by regulatory and safety standards.
   
   

Design Notes

For more information on the Audio Fidelity Testing Policy see http://go.microsoft.com/fwlink/?LinkId=72638.

Target Feature: Device.Audio.Base

Title: Audio subsystem supports full duplex operation

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows RT
  
  
• Windows Server 2008 R2 (x64)
  
  
• Windows Server 2012
  
  

Description

Full duplex audio is essential to support emerging communications applications such as IP telephony, conferencing, and network gaming. These applications require the audio system to play back and record simultaneously.

At least one audio subsystem in a PC system must support full-duplex operation. Secondary audio subsystems may be added to the systems that support only half-duplex operation.

Target Feature: Device.Audio.Base

Title: HD Audio Codec Driver Must Not Leave Function Group in D3Cold State Upon Unload

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows RT
  
  
• Windows Server 2012
  
  
• Windows Server 2008 R2 (x64)
  
  

Description

By the exit of the IRP handler for IRP_MJ_PNP/IRP_MN_REMOVE_DEVICE, an HD Audio Codec driver must have

1. remembered or discovered the current power state of the function group and
   
   
2. if that current function group power state was D3 Cold, the driver must have changed it to a different power state. The function group power state upon exit is required to be D3.
   
   

Target Feature: Device.Audio.Base

Title: WaveRT drivers support pull mode audio streaming technology by implementing the IMiniportWaveRTStreamNotification interface.

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows RT
  
  
• Windows Server 2008 R2 (x64)
  
  
• Windows Server 2012
  
  

Description

By supporting this functionality in the driver, future Microsoft Windows operating systems will be able to employ more efficient techniques for supplying and retrieving data buffers from the audio device. In turn, this will reduce the overall audio latency on the system.

Design Notes

IMiniportWaveRTStreamNotification

The IMiniportWaveRTStreamNotification interface augments the IMiniportWaveRTStream interface, providing additional methods to facilitate DMA driver event notifications. The port driver accesses this interface by querying the IMiniportWaveRTStream interface (via QueryInterface) that it received by calling the IMiniportWaveRT::NewStream method. IMiniportWaveRTStreamNotification inherits from the IUnknown interface.

IMiniportWaveRTStreamNotification is not supported in operating systems earlier than Windows Vista.

In addition to the methods that IMiniportWaveRTStreamNotification inherits from the IUnknown interface, IMiniportWaveRTStreamNotification supports the following methods:

• IMiniportWaveRTStreamNotification::AllocateBufferWithNotification
  
  
• IMiniportWaveRTStreamNotification::FreeBufferWithNotification
  
  
• IMiniportWaveRTStreamNotification::RegisterNotificationEvent
  
  
• IMiniportWaveRTStreamNotification::UnregisterNotificationEvent
  
  

In addition to the above, the driver INF will also need to be modified with the following changes to support event notifications:

1. Use AddReg directive to reference a new add-registry-section to add endpoint property keys. This step can be skipped if such a section already exists. The following example adds a new add-registry-section (HDAudio.EPProperties.AddReg) under HdAudModel.PrimarySpeakerTopo:
   
   

[HdAudModel.PrimarySpeakerTopo]

AddReg=HDAudio.EPProperties.AddReg

1. Next, create an add-registry-section, if it does not already exist, to add endpoint property keys to the registry. Example below adds the appropriate property key for the first endpoint declared in this INF:
   
   

[HDAudio.EPProperties.AddReg]

HKR,"EP\\0",%PKEY_AudioEndpoint_Association%,,%KSNODETYPE_ANY%

HKR,"EP\\0",%PKEY_AudioEndpoint_Supports_EventDriven_Mode%,0x00010001,0x1

1. In the strings section, add the following section for the value of the property keys used in Step 2 above:
   
   

PKEY_AudioEndpoint_Association="{1DA5D803-D492-4EDD-8C23-E0C0FFEE7F0E},2"

PKEY_AudioEndpoint_Supports_EventDriven_Mode="{1DA5D803-D492-4EDD-8C23-E0C0FFEE7F0E},7"

Please reference Windows Driver Kit documentation for details on writing an INF file.

More detailed information on Wave Port Driver for Real-Time Audio Streaming can be found in Windows Hardware Developer Central.

Target Feature: Device.Audio.Base

Title: Audio subsystem supports independent selection of input and output sample formats

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows RT
  
  
• Windows Server 2008 R2 (x64)
  
  
• Windows Server 2012
  
  

Description

If the built-in or external audio device includes both input and output capabilities, the audio device must support independent selection of input and output sample rates and support concurrent streaming at arbitrarily selected sample rates.

Target Feature: Device.Audio.Base

Title: PCI-based audio device supports initiator, target, and block transfer

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows RT
  
  
• Windows Server 2008 R2 (x64)
  
  
• Windows Server 2012
  
  

Description

Full-duplex audio sample transport must be supported by using separate PCI bus-mastering hardware for playback and capture sample streams.

Design NotesSee PCI Local Bus Specification, Revision 2.3 (PCI2.3) or later, "Bus Master."

Target Feature: Device.Audio.Base

Title: Audio drivers support specific properties to describe state of jack/connector

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows RT
  
  
• Windows Server 2008 R2 (x64)
  
  
• Windows Server 2012
  
  

Description

Audio drivers must support the following properties: KSPROPERTY_JACK_DESCRIPTION and KSPROPERTY_JACK_DESCRIPTION2.

* For every endpoint exposed by an HD Audio driver, the driver must respond to a KSPROPERTY_JACK_DESCRIPTION request with a KSJACK_DESCRIPTION structure.

*For every endpoint exposed by an HD Audio driver, the driver must respond to a KSPROPERTY_JACK_DESCRIPTION2 request with a KSJACK_DESCRIPTION2 structure.

*The structures must be populated to accurately reflect the hardware state.

* Third-party jack-presence-detecting drivers use KSJACK_DESCRIPTION.IsConnected for KSPROPERTY_JACK_DESCRIPTION and jackdesc2_presence_detect_capability for KSPROPERTY_JACK_DESCRIPTION2.

Refer to http://msdn.microsoft.com/library/windows/hardware/ff537484(v=VS.85).aspx

Target Feature: Device.Audio.Base

Title: Audio devices need to support jack detection

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows RT
  
  
• Windows Server 2008 R2 (x64)
  
  
• Windows Server 2012
  
  

Description

Analog and digital jacks need to support jack presence detection, except for USB Audio 1.0 devices and S/PDIF. Third-party drivers must advertise this to the OS via KSJACK_DESCRIPTION2.JackCapabilities and relay jack connection state to the OS via KSJACK_DESCRIPTION.IsConnected.

Target Feature: Device.Audio.Base

Title: Audio driver that implements KSNODETYPE_SUPERMIX correctly implements the KSPROPERTY_AUDIO_MIX_LEVEL_TABLE property

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows RT
  
  
• Windows Server 2008 R2 (x64)
  
  
• Windows Server 2012
  
  

Description

If a driver implements support forKSNODETYPE_SUPERMIX then that node must correctly support the KSPROPERTY_AUDIO_MIX_LEVEL_TABLE property whose value is a multiple of decibels.

Design NotesSee the Windows Driver kit, "KSNODETYPE_SUPERMIX." The decibel values are documented on MSDN.

Target Feature: Device.Audio.Base

Title: Audio driver that implements KSNODETYPE_VOLUME correctly supports the KSPROPERTY_AUDIO_VOLUMELEVEL property

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows RT
  
  
• Windows Server 2008 R2 (x64)
  
  
• Windows Server 2012
  
  

Description

If a driver implements support for KSNODETYPE_VOLUME, that node must correctly support the KSPROPERTY_AUDIO_VOLUMELEVEL property whose value is a multiple of decibels.

Design Notes

See the Windows Driver kit, "KSNODETYPE_VOLUME." The decibel values are documented on MSDN.

Target Feature: Device.Audio.Base

Title: Audio Device Driver provides kernel streaming topology according to the documentation in the Microsoft Windows Driver Kit

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows RT
  
  
• Windows Server 2008 R2 (x64)
  
  
• Windows Server 2012
  
  

Description

Some important examples (not inclusive of all the driver has to adhere to, see the WDK for full disclosure):

Check Pin KsDataRange

If a datarange structure (KSDATARANGE structure) has a "Specifier" value KSDATAFORMAT_SPECIFIER_WAVEFORMATEX, then:

FormatSize must be sizeof(KSDATARANGE_AUDIO).

KSDATARANGE_AUDIO values must have:

SampleFrequency is between 1 Hz and 2,000,000 Hz

BitsPerSample are between 8 and 32 bits.

Check Orphaned Pins

All pins must have at least one internal connection and none can be orphaned.

Node Verifications

All Nodes Pin I/O Count

For all node types specified in the MSDN, the following is a list of the required number of input and output connections.

Check Orphaned Nodes

Checks to make sure that all nodes have connections to other nodes and no orphaned nodes are left.

All channel properties, including channels returning Boolean values, such as mute, must include one MembersHeader, and the MembersCount field must accurately describe the number of channels. This requirement also applies to mono controls.

Test your device driver with the KS Topology test to ensure compliance with this requirement.

Target Feature: Device.Audio.Base

Title: Audio device relies on Windows to support various throughput scenarios

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows RT
  
  
• Windows Server 2008 R2 (x64)
  
  
• Windows Server 2012
  
  

Description

Audio device must not rely on analog circuitry designed to mix audio signals between the various device inputs and outputs or signals routing from one DAC to multiple output connectors or from multiple input connectors to one ADC for playback and capture operations in other ways than defined in the UAA HD Audio Pin Config Guidelines.

The device must be able to rely on the operating system to support various throughput and monitoring scenarios and provide independent or otherwise pre-defined by Microsoft audio device implementation guidelines audio connectivity on the PC.

This requirement does not prohibit a codec from having a mixer, it implies that the codec must not rely on the mixer for I/O.

This requirement does not prohibit hardware from supporting offloading, provided the HW audio capabilities are exposed in a manner consistent with Windows.

DAC's and ADC's must have direct I/O from jacks to the operating system.

Design Notes

The PC streaming audio device should behave like a transparent entity without any processing, including mixing paths in the analog domain that the operating system is unaware of. This enables predictability and a uniform audio experience for all Windows users.

Target Feature: Device.Audio.Base

Title: Audio driver does not perform undiscoverable stream redirection or perform other hidden stream handling that is unknown and/or uncontrollable by user or the Windows Audio System.

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows RT
  
  
• Windows Server 2008 R2 (x64)
  
  
• Windows Server 2012
  
  

Description

Audio driver does not perform undiscoverable stream redirection or perform other hidden stream handling that is unknown and/or uncontrollable by user or the Windows Audio System.

Audio driver does not perform hidden stream redirection, routing, switching, splitting, mixing, muxing to other exposed or hidden logical audio devices, applications or other entities but ensures the audio stream from the audio system endpoint for a particular logical device is only directed to that particular logical device that the application is streaming to, as set by the Windows user in the Windows Sound control panel.

The handling of streams is an application layer feature and must not be performed by audio drivers in fashions not discoverable to Windows.

This requirement does not apply to hardware processing as described by KSNODETYPE_AUDIO_ENGINE.

Design Notes

A Windows friendly audio driver exposes the capabilities and peculiarities of the independent logical audio endpoints the audio device or system audio implementation supports. The audio driver provides other hardware specific support enabling use of the device on Windows but the audio driver does not enact policies on the streams coming from the Windows application layer destined for a selected logical audio endpoint on the device or other devices.

Target Feature: Device.Audio.Base

Title: Audio device does not use undiscoverable and/or uncontrollable non-linear audio processing that is on by default.

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows RT
  
  
• Windows Server 2008 R2 (x64)
  
  
• Windows Server 2012
  
  

Description

Some applications depend on accessing unaltered audio data to provide the intended user experience. Products must be capable of providing audio data from Windows applications to listener's ear, or from user's mouth to Windows application that is not modified in any way by the audio device in hardware, firmware, or third-party software. This means that there shall be no undiscoverable or uncontrollable hardware, firmware or third-party software-based AGC, AEC, beam forming, noise suppression, or anything else that significantly alters the audio samples (for example: non-linear processing) from/to the device.

Processing of this type is allowable on audio recording or playback streams if a means is provided for users to disable the processing on their systems, either by exposing the effects as APOs or through another solution. Once disabled by a user, processing must remain off on that product until a user turns it back on.

There is an exception for processing that protects system reliability. This may be on by default and not provide a disable mechanism. Companies that implement reliability effects must ensure the processing elements are reliable and do not pose compatibility issues with the wide range of Windows application needs.

Digital effects may default to enabled or disabled on first use.

Target Feature: Device.Audio.Base

Title: Audio device supports S/PDIF output for PCM and non-PCM data streams

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows RT
  
  
• Windows Server 2008 R2 (x64)
  
  
• Windows Server 2012
  
  

Description

If S/PDIF output is implemented, such Audio device needs to support both PCM and non-PCM data streams.

Design Notes See recommended requirements in the Universal Audio Architecture UAA Hardware Design Guidelines at http://go.microsoft.com/fwlink/?LinkId=50734.

Target Feature: Device.Audio.Base

Title: Audio device complies with related power management specifications

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows RT
  
  
• Windows Server 2008 R2 (x64)
  
  
• Windows Server 2012
  
  

Description

Audio devices must comply with Audio Device Class Power Management Reference Specification, Version 1.0, which provides definitions of the OnNow device power states (D0-D3) for these devices. The specification also covers the device functionality expected in each power state and the possible wake-up event definitions for the class. The device and driver must implement support for power state D3. Support for other device power management states is optional.

For implementation details, refer to Audio Device Power Management Reference Specification, Version 1.0, at http://go.microsoft.com/fwlink/?LinkId=58377.

Target Feature: Device.Audio.Base

Title: USB audio device to properly set descriptor to indicate the purpose of device

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows RT
  
  
• Windows Server 2012
  
  
• Windows Server 2008 R2 (x64)
  
  

Description

USB audio device must properly set descriptor to indicate the purpose of device according to the USB spec http://www.usb.org/developers/devclass_docs/termt10.pdf

Target Feature: Device.Audio.Base

Title: KS category realtime drivers need to support at least standard looped streaming. Other KS category audio drivers need to support standard streaming.

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows RT
  
  
• Windows Server 2008 R2 (x64)
  
  
• Windows Server 2012
  
  

Description

To enable user to take advantage of the most efficient lowest latency path and to play audio correctly on the windows platform, the windows audio engine requires:

• KS category realtime drivers to support at least standard looped streaming.
  
  
• Other KS category audio drivers to support at least standard streaming.
  
  

Target Feature: Device.Audio.Base

Title: The audio driver correctly reports all supported properties

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows RT
  
  
• Windows Server 2012
  
  
• Windows Server 2008 R2 (x64)
  
  

Description

If the audio device and driver support additional properties, the audio driver must report all supported properties correctly to optimize speaker configuration.

Design Notes

If the driver has analog output, the driver exposes a DAC node in its topology. The driver must then support KSPROPSETID_Audio and KSPROPERTY_AUDIO_CHANNEL_CONFIG on that node through a filter handle. The driver then correctly reports support for this property (that is, BASIC_SUPPORT call with KSP_NODE.[node ID of DAC] must succeed) and reports the _GET and _SET capabilities. See the Windows Driver Kit, "Streaming Devices."

Target Feature: Device.Audio.Base

Title: Audio device restarts working within a delay of 10 seconds for S1-S3 and 15 seconds for S4.

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows RT
  
  
• Windows Server 2008 R2 (x64)
  
  
• Windows Server 2012
  
  

Description

Audio device restarts working within a delay of 10 seconds for S1-S3 and 15 seconds for S4.

Refer to: http://download.microsoft.com/download/1/6/1/161ba512-40e2-4cc9-843a-923143f3456c/AudPMSpc.rtf

Target Feature: Device.Audio.Base

Title: Audio adapter should have resume latency to running state (D0) less than the specified values.

Applicable OS Versions

• Windows RT
  
  
• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows Server 2012
  
  

Description

When powered down, an audio adapter must be able to resume to the fully powered state (complete a D0 Power IRP) within the maximum time specified by PortCls.

Using the new IAdapterPowerManagament3 interface, PortCls generates a new D3 exit latency tolerance and communicates it dynamically to the audio miniport. These tolerances are represented as PC_EXIT_LATENCY enumeration values as defined below.

Target Feature: Device.Audio.Base

Title: Audio driver reports render sample position with defined accuracy for stream synchronization

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows RT
  
  
• Windows Server 2012
  
  
• Windows Server 2008 R2 (x64)
  
  

Description

HD Audio drivers must be able to report the current position of the buffer being rendered with an accuracy of 1/20000th of a second, or with frame accuracy (as defined in the HD Audio specification) the current position of the buffer being rendered, in relation to the samples given to the codec. This applies to both the compressed and uncompressed data.

This requirement does not imply that the compressed and uncompressed streams are synchronized. The requirement covers both types of streams but that is the extent of the interaction between the stream types.

For USB audio devices, the required accuracy is 1ms for USB Audio 1.0 implementations and 0.125ms for USB Audio 2.0 implementations.

For all other audio devices, the required accuracy is 1ms.

Target Feature: Device.Audio.Base

Title: Audio sampling position error needs to be less than 0.02 %

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows RT
  
  
• Windows Server 2008 R2 (x64)
  
  
• Windows Server 2012
  
  

Description

Audio sampling position error needs to be less than 0.02 % in order to help accurate echo cancellation when using the device for communication purposes. Sampling rates for capture or render shall be one of the following: 48kHz, 44.1kHz or 16kHz.

Target Feature: Device.Audio.Base

Title: Audio subsystem supports time-synchronized sample rates if both input and output capabilities are present

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows RT
  
  
• Windows Server 2008 R2 (x64)
  
  
• Windows Server 2012
  
  

Description

If the built-in or external audio device includes input and output capabilities, the timing relationship between input and output sample rates must remain constant (that is, no drift). For example, if 8 kHz is selected for both input and output sampling rate, audio hardware must ensure that the sampling rate for input and output is precisely matched.

Further, when input and output sample rates are set to integer ratios, the actual sample rate ratios must match (that is, no drift). For example, if an 8-kHz input sampling rate and a 32-kHz output sampling rate are selected, the ratio of actual sampling rates must be precisely 8:32. This requirement can be accomplished by ensuring that both input and output sampling rates are derived from the same clock and that sample rate divisors are set correctly.

Design Notes

This requirement helps ensure that AEC and NS algorithms maintain performance and convergence. This requirement does not apply to inputs and outputs where the input source sets a clock such as a digital S/PDIF input.

Target Feature: Device.Audio.Base

Title: Audio jacks must use defined tip/ring connections to ensure proper audio channel path.

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows RT
  
  
• Windows Server 2008 R2 (x64)
  
  
• Windows Server 2012
  
  

Description

If the system exposes a multi-channel analog logical device, then each analog output must have independent DAC resource.

The audio jacks must use defined tip/ring connections to ensure proper audio channel path.

Design Notes

See the Intel HD Audio Specification, Revision 1.0, and Microsoft HD Audio Pin Configuration Programming Guidelines.

See recommended requirements in the Universal Audio Architecture UAA Hardware Design Guidelines at http://go.microsoft.com/fwlink/?LinkId=50734.

Target Feature: Device.Audio.Base

Title: Audio device that supports digital output has at least two independent DMA engines and a separate physical connection for digital output using one of the available DMA engines

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows RT
  
  
• Windows Server 2008 R2 (x64)
  
  
• Windows Server 2012
  
  

Description

The audio controller that supports digital output must have two independent DMA engines, one that can be used for wave output and the other to make it possible to support AC-3 over S/PDIF at the same time. The digital audio output capability is supported through a separate physical connector identified for digital audio output and used only for digital audio output.

Given physical limitations, PC system may have limited input and/or output streams. Secondary HD audio controller in such systems may implement fewer DMA engines.

Design Notes

With support for two independent DMA engines, a different signal can be streamed to each connector simultaneously. For example, sending a DVD player application's Dolby Digital stream to the S/PDIF connector while simultaneously sending a voice conversation to the analog connectors. The S/PDIF port needs to be represented as its own audio "device" separate from the analog outputs. Therefore, it will have its own policy configuration, including the preferred data format for a specific signal.

Target Feature: Device.Audio.Base

Title: Voice Communication devices must be UAA compliant audio devices with an appropriate communication centric form factor exposed to the operating system through available mechanisms

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows RT
  
  
• Windows Server 2012
  
  
• Windows Server 2008 R2 (x64)
  
  

Description

Voice communication devices must expose themselves to the operating system as Universal Audio Architecture (UAA)-compliant audio devices. The devices must include an appropriate communication-centric form factor, such as a headset or handset, that Windows can recognize and support.

Webcams that have a microphone expose a microphone form factor device by using USB descriptors according to the USB Audio 1.0 specification.

Aggregate USB audio devices (that is, audio devices that have input and output on the same device) expose themselves to Windows as handset or headset device types by using USB descriptors according to the USB Audio 1.0 specification.

For integrated and PCI audio devices that have analog jacks, the jacks are exposed accurately by using the pin configuration registers and driver topology. The driver topology uses relevant KSNODETYPE descriptors.

There are two options to identify devices as communication-class devices for audio testing with Windows.

• Audio endpoint devices of certain KSNODETYPE descriptors are automatically treated as communication devices for testing purposes. Custom drivers should map to one of these KSNODETYPEs for the device to be recognized as a communication-class device. The following list is a full list of communication-class KSNODETYPE descriptors:
  
  

KSNODETYPE_MICROPHONE

KSNODETYPE_DESKTOP_MICROPHONE

KSNODETYPE_PERSONAL_MICROPHONE

KSNODETYPE_OMNI_DIRECTIONAL_MICROPHONE

KSNODETYPE_MICROPHONE_ARRAY

KSNODETYPE_PROCESSING_MICROPHONE_ARRAY

KSNODETYPE_COMMUNICATION_SPEAKER

KSNODETYPE_HANDSET

KSNODETYPE_HEADSET

KSNODETYPE_SPEAKERPHONE_NO_ECHO_REDUCTION

KSNODETYPE_ECHO_SUPPRESSING_SPEAKERPHONE

KSNODETYPE_ECHO_CANCELLING_SPEAKERPHONE

KSNODETYPE_PHONE_LINE

KSNODETYPE_TELEPHONE

KSNODETYPE_DOWN_LINE_PHONE

Microsoft class drivers map device types to these KSODETYPE descriptors based on information from device hardware or firmware. For example, the Microsoft USB Audio class driver directly maps the USB Audio terminal types that are defined in tables 2-2, 2-4, and 2-5 of the Universal Serial Bus Device Class Definition for Terminal Types, Revision 1.0, March, 1998 to the corresponding KSNODETYPE descriptors above, with three exceptions that do not clearly imply a communication function. These exceptions are the following:

To see the Universal Serial Bus Device Class Definition for Terminal Types, Revision 1.0, March, 1998, visit the following website:

http://www.usb.org/developers/devclass_docs/termt10.pdf

Communication-class USB audio device manufacturers must use one of the mapped terminal types to be tested against communication class requirements and to be used correctly in Windows.

Other drivers may choose different mapping criteria. As long as they map to a KSNODETYPE descriptor that is listed above, the drivers will be considered communication-class during testing. For information on expressing KSNODETYPE descriptors in a WDM driver, see the following website:

http://msdn.microsoft.com//library/windows/hardware/ff537742.aspx

• KSNODETYPE mappings are the preferred solution. However, if these mappings are not sufficient, it is possible to declare a given device as communication-class by adding the .inf driver. To use the .inf method, follow these steps:
  
  

1. Use the AddReg directive to reference a new add-registry section to add endpoint property keys. This step can be skipped if such a section already exists. The following example adds a new Endpoint.AddReg add-registry section under the USBAudio.MyDevice.Interfacesection/method/other element:
   
   

[USBAudio.MyDevice.Interface]

AddReg=Endpoint.AddReg

1. Next, create an add-registry section, if it does not already exist, to add endpoint property keys to the registry. The following example adds the appropriate property key for the first capture endpoint that is declared to be a communication device. The capture endpoint is declared in this INF method for the KSNODETYPE_ANY node:
   
   

[Endpoint.AddReg]

HKR,"EP\\0",%PKEY_AudioEndpoint_Association%,,%KSNODETYPE_ANY%

HKR,"EP\\0",%PKEY_Endpoint_EndpointRoleAffinity%,0x00010001,0x00000204

Note that there are three possible valid values for this key, based on whether the device is a render device, a capture device, or both:

• 0x00000104 A render device of the associated KSNODETYPE descriptor would be tested as a communication device.
  
  
• 0x00000204 A capture device of the associated KSNODETYPE descriptor would be tested as a communication device.
  
  
• 0x00000304 A both render and capture device of the associated KSNODETYPE descriptor would be tested as a communication device.
  
  

1. In the strings section, add the following section for the value of the property keys that are used in step 2:
   
   

PKEY_AudioEndpoint_Association="{1DA5D803-D492-4EDD-8C23-E0C0FFEE7F0E},2"

PKEY_Endpoint_EndpointRoleAffinity = "{b3f8fa53-0004-438e-9003-51a46e139bfc},13"

For more information about writing an INF file, see the Windows Driver Kit documentation.

Target Feature: Device.Audio.Base

Title: Audio driver volume controls are linear

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows RT
  
  
• Windows Server 2008 R2 (x64)
  
  
• Windows Server 2012
  
  

Description

Signal response (as measured by electrical or digital signal level) changes in linearity with the volume control within 3% tolerance. For example: a volume slider change of 10dB should result in an measured volume change within 10dB + or - 0.3dB

Target Feature: Device.Audio.Base

Title: Audio solution that implements topology volume nodes uses a resolution equal to or better than 1.5 dB

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows RT
  
  
• Windows Server 2008 R2 (x64)
  
  
• Windows Server 2012
  
  

Description

Topology volume nodes must have a resolution equal to or better than 1.5dB and implement driver support for volume level as defined in the Windows Driver Kit.

Design NotesSee the Windows Driver Kit, "KSPROPERTY_AUDIO_VOLUMELEVEL."

Target Feature: Device.Audio.Base

Title: Audio device driver supports WAVEFORMATEXTENSIBLE

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows RT
  
  
• Windows Server 2008 R2 (x64)
  
  
• Windows Server 2012
  
  

Description

The audio device driver must support the WAVEFORMATEXTENSIBLE format.

Design Notes

Due to the audio system design in Windows and the availability of a Local Effect (LFX) insert in the audio engine we need to ensure consistency and simplification for audio drivers and the format container that they should expect.

Target Feature: Device.Audio.Base

Title: Audio device is designed to be WaveRT-port-friendly

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows RT
  
  
• Windows Server 2008 R2 (x64)
  
  
• Windows Server 2012
  
  

Description

A UAA HD Audio-compatible implementation meets this requirement automatically. To be considered WaveRT port friendly, the audio subsystem must support the following:

• Cyclic DMA engine with a scatter-gather list.
  
  
• Position register that is separate from other hardware registers (can be a copy).
  
  
• Ability to split samples between pages.
  
  
• Ability to loop on buffers without software intervention.
  
  

This requirement does not apply to external or internal USB audio, Bluetooth, or 1394 audio devices.

Design Notes:

See "A Wave Port Driver for Real-Time Audio Streaming" at http://go.microsoft.com/fwlink/?LinkId=40502.

Target Feature: Device.Audio.Base

Title: Audio device driver is based on the Windows WaveRT miniport WDM driver model

Applicable OS Versions:

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows RT
  
  
• Windows Server 2008 R2 (x64)
  
  
• Windows Server 2012
  
  

Description:

Integrated or discrete audio device driver must be based on the Microsoft Windows WaveRT miniport WDM driver model. Requirement details are defined in the white paper titled "A Wave Port Driver for Real-Time Audio Streaming."

The legacy portsWaveCyclic or WavePCI are not used to support the audio device on Windows.

For device technologies such as USB Audio 1.0 based devices where the audio driver model is not specifically called out, any WDM audio driver model is allowed.

If the audio processing is offloaded to hardware, it is acceptable to use the WaveCyclic driver model.

See the white paper titled "A Wave Port Driver for Real-Time Audio Streaming."

Target Feature: Device.Audio.Base

Title: Audio devices do not glitch during multiple simultaneous streaming

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows RT
  
  
• Windows Server 2012
  
  
• Windows Server 2008 R2 (x64)
  
  
• Windows 7 (x64)
  
  
• Windows 7 (x86)
  
  

Description

Audio device can support 12 simultaneous streams that all make it to the jack with zero glitches both in audio software and offload hardware during such simultaneous streaming. Systems must pass this requirement with audio effects enabled, if that is the default configuration for the product.

Description: This audio device uses the Bluetooth Audio Driver.

Related Requirements

• Device.Audio.Bluetooth.AtleastOneProfileSupport
  
  
• Device.Audio.Bluetooth.AutomaticReconnectAttempt
  
  
• Device.Audio.Bluetooth.ConnectDisconnectBluetooth
  
  
• Device.Audio.Bluetooth.DriverReqs
  
  
• Device.Audio.Bluetooth.HandsFreeCallControl
  
  
• Device.Audio.Bluetooth.HCIDisconnect
  
  
• Device.Audio.Bluetooth.MajorMinorClassID
  
  

Target Feature: Device.Audio.Bluetooth

Title: Bluetooth Audio Device needs to support at least one of the below profiles.

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows RT
  
  
• Windows Server 2012
  
  
• Windows Server 2008 R2 (x64)
  
  
• Windows 7 (x64)
  
  
• Windows 7 (x86)
  
  

Description

The Bluetooth Audio Device must be Bluetooth SIG compliant in at least one of the following profiles:

• A2DP profile as defined in the "Advanced Audio Distribution Profile version 1.2" (A2DP_SPEC_V12) Bluetooth SIG specification.
  
  
• Hands-Free as defined in the "Hands-Free Version 1.5" (HFP 1.5_SPEC_V10) Bluetooth SIG specification.
  
  
• AVRCP as defined in the "Audio/Video Remote Control Profile Version 1.3" (AVRCP_SPEC_V13) Bluetooth SIG specification.
  
  

Target Feature: Device.Audio.Bluetooth

Title: Bluetooth audio devices paired with a PC will automatically attempt to reconnect to the PC after they are powered up or come back into range.

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows RT
  
  
• Windows Server 2012
  
  
• Windows Server 2008 R2 (x64)
  
  
• Windows 7 (x64)
  
  
• Windows 7 (x86)
  
  

Description

The reconnection method must follow the appropriate connection procedures for connection to an Audio Gateway as outlined in the Bluetooth Sig specifications for:

1. Hands-Free Profile
   
   
2. A2DP Profile
   
   
3. AVRCP Profile
   
   

Target Feature: Device.Audio.Bluetooth

Title: Bluetooth audio devices support the properties required for Sound Control Panel to control the connection and disconnection of Bluetooth audio devices.

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows RT
  
  
• Windows Server 2012
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows Server 2008 R2 (x64)
  
  

Description

Bluetooth audio devices support the properties required for Sound Control Panel to control their connection and disconnection.

KSPROPSETID_BtAudio needs to support both:

• KSPROPERTY_ONESHOT_DISCONNECT
  
  
• KSPROPERTY_ONESHOT_RECONNECT
  
  

More info at http://msdn.microsoft.com/library/windows/hardware/ff537446(VS.85).aspx

Target Feature: Device.Audio.Bluetooth

Title: Bluetooth Audio Device Driver Requirements

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows RT
  
  
• Windows Server 2012
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows Server 2008 R2 (x64)
  
  

Description

1. Bluetooth SIG QualificationThe Bluetooth Audio driver must pass the necessary Bluetooth SIG Qualification tests required by the Bluetooth SIG for the profiles listed in the "Bluetooth Profiles" section above.
   
   
2. HID Call ControlThe Bluetooth Audio driver must map the Hands-free call control information to the appropriate HID Call Control messages as defined in the "Windows 7 HID Call Control" specification.
   
   
3. Volume Change NotificationIf volume change notifications are received from the hands-free profile that indicate the volume level of the Bluetooth audio device has changed, the driver must inform the OS of the volume change, consistent with Section 4.28 of the Bluetooth audio Hands-Free specification, "HFP 1.5_SPEC_V10".
   
   

Design Notes

Bluetooth Profiles and SIG QualificationThe Bluetooth Audio Profile documentation is maintained by the Bluetooth SIG. The Bluetooth SIG Qualification is owned and defined by the Bluetooth SIG. Qualification is a necessary pre-condition of the necessary intellectual property license for the Bluetooth wireless technology. Detailed information can be found on the Bluetooth SIG's website at http://www.bluetooth.org.

Volume Change NotificationThe KSEVENTSETID_AudioControlChange is used by the Bluetooth audio driver to notify the OS that the Bluetooth audio device volume level has changed. Not all Bluetooth Hands-free devices will notify the driver of volume changes made by the user. For those that do, the Bluetooth audio driver must use this event to notify the OS of the change. Note that this is not to be used for AVRCP volume notifications as those volume change notifications are handled by the OS. Additional information on KSEVENTSETID_AudioControlChange can be found at http://msdn.microsoft.com

Target Feature: Device.Audio.Bluetooth

Title: Bluetooth audio devices that utilize the Hands Free profile call control platform will comply with this requirement.

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows RT
  
  
• Windows Server 2012
  
  

Description

The document entitled, "Call Control Platform API/DDI" details the usage and implementation of this functionality. This document is available on http://msdn.microsoft.com.

Design Notes

This requirement applies to third parties who create Hands-Free device drivers and opt to use the Bluetooth Call Control platform API/DDI.

Target Feature: Device.Audio.Bluetooth

Title: Bluetooth Audio Devices must complete an HCIDisconnect before powering down

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows RT
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows Server 2008 R2 (x64)
  
  
• Windows Server 2012
  
  

Description

This step is required to allow for timely notification to the system that the device is no longer available. This is needed in order to reroute audio to an alternate audio sink seamlessly when the Bluetooth audio device is turned off providing for a good end user experience.

Target Feature: Device.Audio.Bluetooth

Title: Bluetooth audio devices to expose Major/Minor Class of Device identifier and accurately reflect form factor/primary usage.

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows RT
  
  
• Windows Server 2012
  
  
• Windows Server 2008 R2 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  

Description

Bluetooth audio devices must expose the proper Major and Minor Class of Device identifier. The values chosen must accurately reflect the form factor and primary usage of the device.

Please refer to the following Bluetooth specifications from the Bluetooth Special Interest Group website:

For A2DP devices, class of device ID is defined in Section 5.3 "SDP Interoperability Requirements" of the Advanced Audio Distribution Profile Specification "A2DP_SPEC_V12" document.

For Hands-Free devices, class of device ID is defined in Section 5.5.1 "Class of Device" of the Hands-Free Profile Specification version 1.5 in the "HFP 1.5_SPEC_V10" document.

Description: HardwareAudioProcessing

Related Requirements

• Device.Audio.HardwareAudioProcessing.AudioHardwareOffloading
  
  
• Device.Audio.HardwareAudioProcessing.ETWEvent
  
  
• Device.Audio.HardwareAudioProcessing.IMiniport
  
  

Target Feature: Device.Audio.HardwareAudioProcessing

Title: Hardware that supports offloaded audio render processing meets this requirement

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows RT
  
  
• Windows Server 2012
  
  

Description

If a hardware solution supports offloaded audio render processing, the driver must expose a KS filter and a single KSNODETYPE_AUDIO_ENGINE node with appropriate pin factories connected.

If a hardware solution supports the offloading of audio render processing, mixing, or decoding, the driver must expose a KS filter. For each rendering path through that filter that supports hardware offloading the driver must expose a single KSNODETYPE_AUDIO_ENGINE node, connecting directly to only the following pin factories:

• two KS sink pin factories
  
  
• a single KS source pin factory for reference stream support
  
  

If a driver exposes a KSNODETYPE_AUDIO_ENGINE node, the driver and hardware must support base-level functionality.

If a driver exposes a KSNODETYPE_AUDIO_ENGINE node, the driver and hardware must support the following capabilities:

• Audio mixer with at least 3 simultaneous inputs (2 offload and 1 host process)
  
  
• Volume and mute capabilities both pre- and post-mixing
  
  
• Metering reporting (support for querying per-stream peak values, both pre & post-mix)
  
  
  • For stream metering (pre-mixing), metering levels should be reported after the LFX and before volume control
    
    
  • For endpoint metering (post-mixing), metering levels should be reported:
    
    
    • Before volume control and GFX, when the GFX is an encoder
      
      
    • After the GFX and before volume control, when the GFX is not an encoder
      
      
• Reference stream (support for sending the audio stream post-mix back to the Windows audio stack)
  
  
• The reference stream provided should be the final output to the audio device, or, if encoding is taking place, just prior to encoding.
  
  

If a driver exposes a KSNODETYPE_AUDIO_ENGINE node, the driver must support KSPROPSETID_AudioEngine with certain properties.

If a driver exposes a KSNODETYPE_AUDIO_ENGINE node, the driver must support KSPROPSETID_AudioEngine with the following properties:

• KSPROPERTY_AUDIOENGINE_LFXENABLE
  
  
• KSPROPERTY_AUDIOENGINE_GFXENABLE
  
  
• KSPROPERTY_AUDIOENGINE_MIXFORMAT
  
  
• KSPROPERTY_AUDIOENGINE_DEVICEFORMAT
  
  
• KSPROPERTY_AUDIOENGINE_SUPPORTEDDEVICEFORMATS
  
  
• KSPROPERTY_AUDIOENGINE_DESCRIPTOR
  
  
• KSPROPERTY_AUDIOENGINE_WAVERT_CURRENT_WRITE_POSITION
  
  
• KSPROPERTY_AUDIOENGINE_BUFFER_SIZE_RANGE
  
  
• KSPROPERTY_AUDIOENGINE_LOOPBACK_PROTECTION
  
  
• KSPROPERTY_AUDIOENGINE_VOLUMELEVEL
  
  
• KSPROPERTY_AUDIO_VOLUMELEVEL
  
  
• KSPROPERTY_AUDIO_MUTE
  
  
• KSPROPERTY_AUDIO_PEAKMETER2
  
  
• KSPROPERTY_AUDIO_PRESENTATION_POSITION
  
  

If a driver exposes a KSNODETYPE_AUDIO_ENGINE node, the driver must expose certain pin factories.

If a driver exposes a KSNODETYPE_AUDIO_ENGINE node, the driver must expose the following pin factories:

• Host process pin factory
  
  
  • Must support only a single instance
    
    
• Offload pin factory
  
  
  • Must support at least two instances
    
    
• Loopback pin factory
  
  
  • Must support at least a single instance
    
    

In addition, the following must be met:

• Loopback pins must:
  
  
  • Have a "Possible Global Instances" of at least 1
    
    
  • Support at least 1 instance regardless of what else is going on in the system
    
    
• To enable scenarios like cross-fade, offload-capable endpoints must support 1 loopback pin instance + 1 host pin instance + each of the following in isolation, assuming no other offload endpoints are being used at the time:
  
  
  • Any required PCM format + Any required PCM format (the same, or different)
    
    
  • Any required PCM format + Any required MP3 format
    
    
  • Any required MP3 format + Any required MP3 format
    
    
  • Any required PCM format + Any required mono or stereo AAC format
    
    
  • Any required MP3 format + Any required mono or stereo AAC format
    
    
  • Any required mono or stereo AAC format + Any required mono or stereo AAC format
    
    
• The loopback pin must support
  
  
  • The HW mix format
    
    
  • The device format (which can be publically queried from the endpoint property store)
    
    

If a hardware solution supports offloaded audio render processing, the same functionality provided in hardware (for example: processing or effects) must be available in software as well.

In order to provide a consistent user experience and prevent confusion when a user enables or configures functionality that exists in only hardware or only software, the capabilities provided must be equal in both hardware and software.

If a driver exposes a KSNODETYPE_AUDIO_ENGINE node, the driver must support streaming specific PCM formats.

Description

If a driver exposes a KSNODETYPE_AUDIO_ENGINE node, the driver must support streaming the following PCM formats on the offload pins:

• Sampling rates:
  
  
• 8 kHz
  
  
• 11.025 kHz
  
  
• 16 kHz
  
  
• 22.050 kHz
  
  
• 32 kHz
  
  
• 44.1 kHz
  
  
• 48 kHz
  
  
• 88.2 kHz
  
  
• 96 kHz
  
  
• 176.4 kHz
  
  
• 192 kHz
  
  
• Bit Depths:
  
  
• 8-bit
  
  
• 16-bit
  
  
• 24-bit
  
  
• Channel configurations of 1.0, 2.0,2.1, 3.1, 4.0, 5.0 and 5.1
  
  

If hardware supports offloaded audio render processing, the steady-state latency for real-time PCM audio must be less than 20 ms.

If hardware supports offloaded audio render processing, the steady-state latency (as measured between the render KS endpoint and the capture KS endpoint on the same device with all processing disabled and the smallest supported buffer sizes being used) must be less than 20 ms.

If a hardware solution supports offloaded audio render processing, the startup latency must be less than 80 ms for compressed formats and 15ms for PCM.

If hardware supports offloaded audio render processing, the startup latency (as defined as the time between just before KSCreatePin and the audio play position beginning to advance) must be less than 80 ms for compressed formats and 15ms for PCM.

If a hardware solution supports offloaded audio render processing, the hardware must support certain buffer sizes.

If a hardware solution supports offloaded audio render processing, the hardware must support buffer sizes:

• As large as (or larger than) 1 second
  
  
• As small as (or smaller than) 10 milliseconds
  
  

Times above assume an audio format of 2 channels, 48 kHz, 16-bit PCM.

If a hardware solution supports offloaded audio render processing, the pause or stop latency must be less than 10ms.

If a hardware solution supports offloaded audio render processing, the pause or stop latency (as measured between a pause/stop command and the audio pausing/stopping) must be less than 10ms.

The CPU consumption by an audio driver must be less than 5% and memory usage must be less than 100MB.

An audio driver must not consume more than 5% of the total CPU processing available and must not consume more than 100MB of system RAM.

Systems that support connected standby must support certain codecs and processing capabilities.

In order to ensure a high-quality user experience on systems that support connected standby where the in-box Windows codecs may be unavailable, the follow codecs and processing functionality are required:

• MP3 decoder
  
  
  • all MPEG formats except VBR
    
    
  • Decode requirement is limited to mono and stereo formats; decoder must be able to accept multichannel MP3 content, but is only required to decode the stereo content
    
    

AAC decoder

Channel configurations

• Mono
  
  
• Stereo
  
  
• 3.0
  
  
• 4.0 (L, R, C, Rear)
  
  
• 5.0
  
  
• 5.1
  
  

Sample rates

All AAC sample rates

Bit rates

All bit rates

Profile levels

• 0x28 AAC L1
  
  
• 0x29 AAC L2
  
  
• 0x2A AAC L4
  
  
• 0x2B AAC L5
  
  
• 0x2C High Efficiency AAC Profile L2
  
  
• 0x30 High Efficiency AAC v2 Profile L2
  
  

Payload types

• 0 Raw
  
  
• 1 ADTS
  
  

Audio Object types:

• 2 AAC LC
  
  
• 5 SBR
  
  
• 29 PS
  
  
• Sample rate converter
  
  

All decoding and processing functionality provided must be exposed via support for the corresponding KS properties via the Portcls WaveRT driver.

Target Feature: Device.Audio.HardwareAudioProcessing

Title:If a hardware solution supports offloaded audio render processing, then the driver must raise an ETW event to report glitches detected by the hardware audio engine.

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows RT
  
  
• Windows Server 2012
  
  

Description

The audio driver needs to raise an Event Tracing for Windows (ETW) event to report glitches detected by the HW Audio Engine. This event should at least include the reason of the glitching and the DMA buffer information.

The following events are defined for the miniport to reports events through Portcls interface callbacks.

typedef enum 
{
eMINIPORT_IHV_DEFINED = 0, 
eMINIPORT_BUFFER_COMPLETE,
eMINIPORT_PIN_STATE,
eMINIPORT_GET_STREAM_POS,
eMINIPORT_SET_WAVERT_BUFFER_WRITE_POS,
eMINIPORT_GET_PRESENTATION_POS,
eMINIPORT_PROGRAM_DMA,
eMINIPORT_GLITCH_REPORT
} ePcMiniportEngineEvent;

Target Feature: Device.Audio.HardwareAudioProcessing

Title:If a hardware solution supports offloaded audio render processing, the driver must implement IMiniportAudioEngineNode and IMiniportStreamAudioEngineNode

Applicable OS Versions

• Windows Server 2012
  
  
• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows RT
  
  

Description

IMiniportAudioEngineNode contains a list of methods related to the offload KS properties targeting the audio engine node via KS filter handle. A miniport driver's WaveRT miniport class needs to inherit not only from IMiniportWaveRT interface, it also needs to inherit IMiniportAudioEngineNode interface and implement all the defined methods.

IMiniportStreamAudioEngineNode contains a list of methods related to the offload KS properties targeting the audio engine node via pin instance handle. A miniport driver's WaveRT miniport class needs to inherit not only from IMiniportWaveRTStreamNotification interface, it also needs to inherit IMiniportStreamAudioEngineNode interface and implement all the defined methods.

Description This audio device uses the HD Audio Driver.

Related Requirements

• Device.Audio.HDAudio.2AudioChannelsForHDMIorDisplayPort
  
  
• Device.Audio.HDAudio.AnalogJackDetection
  
  
• Device.Audio.HDAudio.DefaultAssociationNotZero
  
  
• Device.Audio.HDAudio.DigitalJackDetection
  
  
• Device.Audio.HDAudio.HDAudioCodecAdditionalReqs
  
  
• Device.Audio.HDAudio.HDAudioSpecCompliance
  
  
• Device.Audio.HDAudio.HDMIDCN
  
  
• Device.Audio.HDAudio.HDMIKSPROPERTYJACKSINKINFO
  
  
• Device.Audio.HDAudio.INFHasDeviceID
  
  
• Device.Audio.HDAudio.LowPowerDCN
  
  
• Device.Audio.HDAudio.OneCodecPortOneConnector
  
  
• Device.Audio.HDAudio.PinConfigPortConnectivity
  
  
• Device.Audio.HDAudio.PnPCodecDeviceID
  
  
• Device.Audio.HDAudio.UniqueSequenceNumbers
  
  

Target Feature: Device.Audio.HDAudio

Title:Display adapter or chipset with HDMI audio or DisplayPort audio capabilities must implement two channel audio support that is compliant with the HD Audio specification

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows RT
  
  
• Windows Server 2008 R2 (x64)
  
  
• Windows Server 2012
  
  

Description

A display subsystem on a platform that does not support connected standby but supports HDMI audio or DisplayPort audio capabilities must implement a minimum of two channel audio support compliant with HD Audio specification.

The minimum requirement is to use an HD Audio compliant solution exposing an SPDIF Output with a static format support of Stereo PCM, 16 bit depth with sampling rate of 44.1kHz and 48kHz.

HDMI endpoints do not have to be based on HD Audio if they are a part of Systems that support connected standby.

Additional information on how to expose an SPDIF Output in an HD Audio compliant controller/codec configuration can be found in the Intel HD Audio specification.

Expose the logical independent HDMI Audio or DisplayPort audio device as outlined below to be exposed as an HDMI Audio device in Windows:

Intel HMDI Audio HD Audio Spec ECR:Pin complex.PinCaps.HdmiCapable == 1, AND PinConfig.DefDevice = DigitalOtherOut (0x5)General/Geometric location irrelevant here

or

Intel HD Audio 1.0 method:Pin config general location is internal (1) AND geometric location is "Special1" (0x8)AND PinConfig.DefDevice = DigitalOtherOut (0x5)Pincaps.HdmiCapable is irrelevant here.Also, see the UAA Hardware Design Guidelines available at http://go.microsoft.com/fwlink/?linkid=50734.

Target Feature: Device.Audio.HDAudio

Title: HD Audio solution supports jack-presence detection for analog jacks

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows RT
  
  
• Windows Server 2008 R2 (x64)
  
  
• Windows Server 2012
  
  

Description

The HD Audio codec and the system board must implement HD Audio-compliant jack-presence detection for analog jacks. Presence detection implies that the codec with required system components (jack connector and jack detection circuit) must be able to detect the presence of jack insertion into and jack removal from the input/output connectors that the codec is using. When this occurs an unsolicited response is sent so that software can be notified without constantly polling the device. Implementation of unsolicited response support for jack detection events is required for Windows although it may be worded as optional in the HD Audio specification.

This requirement is unrelated to the feature of automatic sensing of what the peripheral might be. Sensing by using impedance matching is not required.

This requirement specifically means that the codec implements presence detection on each exposed pin that is connected to a system connecter (jack) and that the system board implements an audio jack detection circuit (HD Audio Specification section 7.4.2) external to the codec for each jack on the system. This requirement does not apply to device types defined in the HD Audio codec's pin configuration register defaults as a Line Connector device using an RCA type physical connector.

See the Microsoft UAA HD Audio Pin Configuration Programming Guidelines white paper for additional clarifications on the specified jack connectors that require jack detection.http://msdn.microsoft.com/library/windows/hardware/gg463015.aspx

Target Feature: Device.Audio.HDAudio

Title: HD Audio devices that expose a digital output must meet HD audio design change notification "Copy Bit Clarification".

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows Server 2008 R2 (x64)
  
  
• Windows Server 2012
  
  
• Windows RT
  
  

Description

Audio devices that expose a digital output must meet HD audio design change notification "Copy Bit Clarification".

Refer to DCN_-_Copy_Bit_Polarity_Clarification_rev1p0.pdf

Target Feature: Device.Audio.HDAudio

Title: Values in the Default Association field of the HD Audio codec pin configuration register are not set to zero (reserved value)

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows RT
  
  
• Windows Server 2008 R2 (x64)
  
  
• Windows Server 2012
  
  

Description

The value zero is reserved and must never be used as a default association value.

Target Feature: Device.Audio.HDAudio

Title: HD Audio solution supports jack-presence detection for digital jacks

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows RT
  
  
• Windows Server 2008 R2 (x64)
  
  
• Windows Server 2012
  
  

Description

The HD Audio codec and the system board must implement HD Audio-compliant jack-presence detection for digital jacks. Presence detection implies that the codec with required system components (jack connector and jack detection circuit) must be able to detect the presence of jack insertion into and jack removal from the input/output connectors that the codec is using except for S/PDIF jacks. When this occurs an unsolicited response is sent so that software can be notified without constantly polling the device. Implementation of unsolicited response support for jack detection events is required for Windows although it may be worded as optional in the HD Audio specification.

This requirement is unrelated to the feature of automatic sensing of what the peripheral might be.

Target Feature: Device.Audio.HDAudio

Title: HD Audio codec supports additional requirements not specified in the Intel High Definition Audio specification

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows RT
  
  
• Windows Server 2012
  
  
• Windows Server 2008 R2 (x64)
  
  

Description

To be UAA compliant, an HD Audio codec must implement the following features, which are not necessarily required by Intel High Definition Audio Specification:

• Speaker compensation is the only valid scenario for audio signal processing of an audio stream by a codec, and then it is valid only if the speakers are hardwired to the pin complex that contains the processing node (such as integrated laptop speakers). This requirement does not apply to decryption of protected audio streams.
  
  
• When all of an HDAudio codec's widgets are configured in the benign processing state, the codec performs no nonlinear or time-variant processing on the audio streams that pass through it.
  
  
• Software must be able to set all processing nodes to the benign processing state, and the codec must function according to UAA baseline requirements while in this state.
  
  
• An HDAudio codec must be accessible only through the HDAudio bus controller. The codec must not expose registers or other hardware mechanisms that are accessible through either memory or I/O address space. This requirement does not encompass HDMI or DisplayPort. For HDMI or DisplayPort, please refer to the HD audio HDMI DCN.
  
  
• Modem and audio functionality must not be combined. Although the same piece of silicon can house both modem and audio devices, the functions must be separate devices and must not share any software or hardware resources (such as ADCs or DACs).
  
  
• When the HD Audio link is in a running state (HD Audio controller is in D0), UAA-compliant HD Audio codecs must respond to commands even when powered down in all required device power-management states. In effect, the digital section of the codec must remain powered.
  
  
• Codecs must respond to a verb even if addressed at a nonexistent widget or if the verb itself is not valid.
  
  
• Function group nodes must have node IDs in the range 0 to 127. This restriction does not apply to node IDs for widget nodes.
  
  
• In a system with one or more HDAudio codecs, the system BIOS must initialize the Configuration Default Register for each codec pin widget based on the system configuration/implementation of the HD Audio codec while considering the Microsoft Pin Configuration Programming Guidelines so that the UAA HDAudio function class driver's topology parser can create a functional device topology for the codec. The default data in the HD Audio codec pin configuration registers must not misrepresent the hardware capabilities, and the Configuration Default Registers must not be null (all zeros).
  
  
• A function group in an HDAudio codec must expose a nonzero subsystem ID. The BIOS overwrites the subsystem ID if necessary. If the BIOS cannot program the subsystem ID or if it does so incorrectly, the hardware must supply a default, vendor-specific subsystem ID.
  
  

Target Feature: Device.Audio.HDAudio

Title: HD Audio codec for audio complies with the Intel High Definition Audio specification

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows RT
  
  
• Windows Server 2008 R2 (x64)
  
  
• Windows Server 2012
  
  

Description

If the codec is for an audio implementation, it must be implemented according to Intel High Definition Audio Specification, Revision 1.0, and updated when commercially possible to comply with HD Audio specification DCRs.

Target Feature: Device.Audio.HDAudio

Title: If hardware supports multi-channel HDMI or DisplayPort audio consistent with the method defined by HD Audio, then the hardware must comply with the HD Audio HDMI Design Change Notifications (DCN).

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows RT
  
  
• Windows Server 2008 R2 (x64)
  
  
• Windows Server 2012
  
  

Description

If hardware supports multi-channel HDMI or DisplayPort audio consistent with the method defined by HD Audio, then the hardware must comply with the HD Audio HDMI Design Change Notifications (DCN).

Design Notes

If hardware supports HDMI or DisplayPort audio and implements any of the verbs listed below, the hardware must comply with the following HD Audio DCNs:

HDA034-A2: HDMI Content Protection and Multi-Channel SupportHDA039-A: HDMI/ELD Memory StructureHDA036-A: DisplayPort Support and HDMI Miscellaneous Corrections

If hardware supports HDMI or DisplayPort audio, implements any of the verbs listed below and supports the transmission of high bit-rate (HBR) formats, the hardware must comply with the HD Audio DCN HDA035-A: HDMI High Bit Rate Support.

Verbs

F2Fh (Get HDMI ELD Data)

F2Dh (Get Converter Channel Count)

72Dh (Set Converter Channel Count)

F2Eh (Get HDMI Data Island Packet - Size Info)

72Eh (Set HDMI Data Island Packet - Size Info)

F30h (Get HDMI Data Island Packet - Index)

730h (Set HDMI Data Island Packet - Index)

F31h (Get HDMI Data Island Packet - Data)

731h (Set HDMI Data Island Packet - Data)

F32h (Get HDMI Data Island Packet - Transmit-Control)

732h (Set HDMI Data Island Packet - Transmit-3Control)

F33h (Get Content Protection Control)

733h (Set Content Protection Control)

F34h (Get Converter Channel to HDMI Slot Mapping)

Target Feature: Device.Audio.HDAudio

Title: Audio drivers using HD audio specification and exposing HDMI or DisplayPort endpoint support the KSPROPERTY_JACK_SINK_INFO property

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows RT
  
  
• Windows Server 2008 R2 (x64)
  
  
• Windows Server 2012
  
  

Description

Audio drivers that expose HDMI or DisplayPort endpoints must support the KSPROPERTY_JACK_SINK_INFO property.

Design Notes

For every endpoint exposed by an audio driver that supports HDMI or DisplayPort audio, the driver must respond to a KSPROPERTY_JACK_SINK_INFO request with a KSJACK_SINK_INFORMATION structure. The structure shall be correctly populated.

Target Feature: Device.Audio.HDAudio

Title: INF file for HD Audio codec includes properly formatted device ID string for each supported codec device

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows RT
  
  
• Windows Server 2008 R2 (x64)
  
  
• Windows Server 2012
  
  

Description

Vendors that supply custom HD Audio function drivers must include an INF file that follows guidelines for device identification strings that are defined in Plug and Play Guidelines for High Definition Audio Devices, "INF Files for HD Audio Codecs."

Design Notes

See Guidelines at http://msdn.microsoft.com/library/windows/hardware/gg463015.aspx.

Target Feature: Device.Audio.HDAudio

Title: If HD Audio codec supports HD Audio Low-Power DCN then it needs to implements the Low-Power specification correctly in hardware, firmware, and third-party software (driver)

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows RT
  
  
• Windows Server 2008 R2 (x64)
  
  
• Windows Server 2012
  
  

Description

An HD audio Low-Power Design Change Notification (DCN) compatible HD Audio 1.0 based codec implements Low-Power capabilities according to the Low-Power specification and Microsoft UAA Hardware Design Guidelines.

Design Notes

See the RAND licensed Intel HD Audio specification, the HD Audio Low-Power DCN amendment to that specification and the Microsoft UAA Hardware Design Guidelines

Target Feature: Device.Audio.HDAudio

Title: A single HD Audio codec port is used for a single connector

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows RT
  
  
• Windows Server 2008 R2 (x64)
  
  
• Windows Server 2012
  
  

Description

Each HD Audio codec port connects to one and only one audio source, destination, or jack. For compatibility with the UAA class driver do not double-up on input or output ports in ways that cannot be exposed to the class driver through the information in the pin configuration registers.

Designs that use GPIOs under control of third-party function drivers must default to an appropriate hardware configuration when the UAA class driver is loaded.

Exceptions

• Combination jacks (headphone/S/PDIF) are allowed if the digital output is exposed as a separate, independent always on device using the HD Audio pin configuration register values and the analog section of the jack supports jack presence detection.
  
  
• Combination jacks that have both a speaker and a microphone are also acceptable provided the connector supports microphone and speaker jack presence detection.
  
  
• There is another exception to this requirement with regards to an audio device pin that feeds two different connectors intended for SPDIF protocol content. In the case where a system or device exposes an RCA jack (Co-ax) and an optical output for the SPDIF protocol stream from one codec pin this is permitted only if the audio driver exposes the pin as outlined in the design note section below
  
  
• It is also acceptable to build a system that has two headphone jacks fed by the same HD Audio pin.
  
  

Design Notes

An array of jack descriptions can also be used to show that a pair of jacks is equivalent. The following example would indicate to the user that the yellow RCA jack and the black "digital optical" jack will carry the same signal:

KSJACK_DESCRIPTION ar_SPDIF_Jacks[] = 
{
// jack 1
{
(SPEAKER_FRONT_LEFT | SPEAKER_FRONT_RIGHT), // ChannelMapping (L,R)
RGB(255,255,0), // Color (yellow)
eConnTypeRCA, // ConnectionType (RCA)
eGeoLocRear, // GeoLocation
eGenLocPrimaryBox, // PortConnection
TRUE // IsConnected
},
// jack 2
{
(SPEAKER_FRONT_LEFT | SPEAKER_FRONT_RIGHT), // (L,R)
RGB(0,0,0), // (black)
eConnTypeOptical, // (optical)
eGeoLocRear,
eGenLocPrimaryBox,
TRUE
}
};

Clarification: This exception has nothing to do with HDMI Audio, it only covers SPDIF on two physically different SPDIF connectors and this exception does NOT allow HDMI Audio outputs to share a codec pin with SPDIF. That is still prohibited.

Target Feature: Device.Audio.HDAudio

Title: Pin configuration register for an HD Audio codec has specific settings for port connectivity field depending on implementation

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows RT
  
  
• Windows Server 2008 R2 (x64)
  
  
• Windows Server 2012
  
  

Description

A pin widget's port connectivity value of 0x01 (No Connection) is valid only when a system in which the HD Audio codec resides has no jack or integrated device attached to the pin widget. A port connectivity setting of 0x02 (10b) should be used only in those cases where a trace on a circuit board directly connects the codec and an integrated device such as a speaker amplifier or microphone. A port connectivity setting of 0x03 (011b) is specifically disallowed. Each pin widget must connect to a single audio endpoint.

Target Feature: Device.Audio.HDAudio

Title: HD Audio codec follows Plug and Play requirements for codec device identification

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows RT
  
  
• Windows Server 2012
  
  
• Windows Server 2008 R2 (x64)
  
  

Description

HD Audio codecs must comply with the Plug and Play requirements for proper identification that are described in Plug and Play Guidelines for High Definition Audio Devices, "HD Audio Codec."

Design Notes

See Guidelines at http://msdn.microsoft.com/library/windows/hardware/gg462962.aspx.

Target Feature: Device.Audio.HDAudio

Title: HD Audio Codec Pin configuration register defaults: Sequence numbers within the same default association are unique

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows RT
  
  
• Windows Server 2008 R2 (x64)
  
  
• Windows Server 2012
  
  

Description

In the data configured by the BIOS or in the default values from the codec manufacturer, the sequence numbers within the pin configuration register's default association must be unique within the same association except for association 0xf, in which all instances should support Sequence ==0.

Design Notes

See Pin Configuration Guidelines for High Definition Audio Devices, at http://go.microsoft.com/fwlink/?LinkId=58572.

Description: This audio device uses HD Audio, Bluetooth, or USB Audio Drivers

Related Requirements

• Device.Audio.UAACompliance.TestUsingBluetoothClassDriver
  
  
• Device.Audio.UAACompliance.UAA
  
  

Target Feature: Device.Audio.UAACompliance

Title: Bluetooth devices tested using Bluetooth class driver

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows RT
  
  
• Windows Server 2012
  
  
• Windows Server 2008 R2 (x64)
  
  
• Windows 7 (x64)
  
  
• Windows 7 (x86)
  
  

Description

Bluetooth devices (for example: headset or speakers) need to use Windows Bluetooth Audio Class drivers for certification.

Target Feature: Device.Audio.UAACompliance

Title: Audio device is compliant with one of the appropriate technology specifications supported by the UAA initiative

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows RT
  
  
• Windows Server 2008 R2 (x64)
  
  
• Windows Server 2012
  
  

Description

An audio device must comply with the appropriate standard as supported by the Microsoft Universal Audio Architecture Initiative. The supported standards are USB Audio, IEEE 1394 Audio, Bluetooth Audio and High Definition Audio. The relevant Windows audio class driver loads, runs, and passes functionality tests on the implementation. This includes meeting minimum performance requirements as defined in the Microsoft UAA Hardware Design Guidelines.

This requirement does not apply to systems that support connected standby or devices that support USB Audio 2.0.

Design Notes

See "Universal Audio Architecture" at http://go.microsoft.com/fwlink/?LinkId=40631.

See "USB Audio Devices and Windows" at http://go.microsoft.com/fwlink/?LinkId=40632.

Description: This audio device uses the USB Audio Driver.

Related Requirements

• Device.Audio.USB.HIDCommunications
  
  
• Device.Audio.USB.HIDControls
  
  
• Device.Audio.USB.MicArray
  
  
• Device.Audio.USB.USB
  
  

Target Feature: Device.Audio.USB

Title: Audio capable and video capable and audio/video capable USB communication devices implement HID controls according to USB HID Specifications

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows RT
  
  
• Windows Server 2008 R2 (x64)
  
  
• Windows Server 2012
  
  

Description

Communication devices that implement a USB HID interface must be compliant with the USB Device Class Definition for Human Interface Devices (HID), Version 1.1, and USB Usage Tables for HID Power Devices, Version 1.12.

Devices may not use Reserved usages from any Standard Usage Page.

Scenario

It is very easy for me to use my PC for Internet voice communication with my family and colleagues because my PCs audio devices tell Windows about their role and my VOIP application can automatically find the right device for the job without any input from me.

When I use my PC for voice communication with my family or colleagues I can easily understand them and they can easily understand me. I can take and place my calls regardless of other audio activity on my PC. With my PCs audio solution I have a quality calling experience comparable to todays wired telephones and/or speakerphones.

Design Notes

Design and Implementation Note See the Windows Driver Kit, "HID and Windows."

Target Feature: Device.Audio.USB

Title: USB audio device uses USB HID audio controls to keep the operating system informed of user interactions with the device

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows RT
  
  
• Windows Server 2008 R2 (x64)
  
  
• Windows Server 2012
  
  

Description

USB audio devices must use USB HID specification-compliant HID to control basic functions. If volume adjustment controls are implemented on the USB audio device, it must declare itself as a consumer control device (usage 0x01), as defined in Consumer Page (page 0x0C) in the USB Usage Tables for HID Power Devices, Release 1.1, and in Windows support for HID-based audio controls.

Design Notes

See "HID Audio Controls and Windows" at http://go.microsoft.com/fwlink/?LinkId=40491.

Target Feature: Device.Audio.USB

Title: Standalone USB Audio based microphone array device complies with the Microsoft USB Audio 1.0 design guidelines and Microsoft Microphone Array Design Guidelines

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows RT
  
  
• Windows Server 2008 R2 (x64)
  
  
• Windows Server 2012
  
  

Description

An externally connected USB based microphone array device must comply with the UAA-supported technology standard, must comply with the USB Device Class Definition for Audio Devices 1.0, and must be implemented according to the guidelines in "Microphone Array Support in Windows Vista."

The device must report itself and its capabilities according to the design guidelines in the Microsoft USB Audio Microphone Array Design Guidelines.

Target Feature: Device.Audio.USB

Title: USB Audio Device follows UAA USB Audio Design Guidelines

Applicable OS Versions

• Windows 8 (x86)
  
  
• Windows 8 (x64)
  
  
• Windows 7 (x86)
  
  
• Windows 7 (x64)
  
  
• Windows RT
  
  
• Windows Server 2008 R2 (x64)
  
  
• Windows Server 2012
  
  

Description

A USB audio-based audio device in a stand-alone external form factor or in an AVR or in other permutations follows the Microsoft UAA USB Audio Design Guidelines.

Design Notes

See Microsoft UAA USB Audio Design Guidelines at http://go.microsoft.com/fwlink/?LinkId=50734.