Windows Universal Audio Drivers - Windows Drivers (2023)

In Windows 10 you can write a universal audio driver that works on many types of hardware. This topic discusses the benefits of this approach as well as the differences between the platforms. In addition to the universal Windows drivers for audio, Windows continues to support legacy audio driver technologies such as WDM.

Introduction to Universal Windows Drivers for Audio

IHVs can develop a universal Windows driver that works on all devices (desktops, laptops, tablets, phones). This can reduce development time and costs for initial code development and subsequent maintenance.

These tools are available to develop universal Windows drivers:

• Visual Studio 2015: Set Target Platform equal to Universal. For more information on configuring the driver development environment, seeIntroduction to Universal Windows Drivers.

• APIValidator Tool - You can use the ApiValidator.exe tool to verify that the APIs called by your driver are valid for a Universal Windows Driver. This tool is part of the Windows Driver Kit (WDK) for Windows 10 and runs automatically when using Visual Studio 2015. For more information, seeUniversal Windows driver validation.

• DDI Reference Documentation: The DDI reference documentation has been updated to indicate which DDIs are supported by Universal Windows Drivers. For more information, seeAudio Device Reference.

Build a universal audio driver

For step-by-step instructions, seeIntroduction to Universal Windows Drivers. Here is a summary of the steps:

1. Load the universal audio sysvad sampler to use as a starting point for your universal audio driver. Alternatively, you can start with the blank WDM driver template and add the universal sysvad sample code as needed for your audio driver.

2. Set the target platform to "Universal" in the project properties.

3. Create an installation package: If your target device is a device running Windows 10 for desktop editions (Home, Pro, Enterprise, and Education), use a configurable INF file. If your target is a device running Windows 10 Mobile, use PkgGen to generate an .spkg file.

4. Build, install, deploy, and debug drivers for Windows 10 Desktop or Windows 10 Mobile editions.

   (Video) UA Support: How to use Volt for Windows System Audio

sample code

Sysvad and SwapAPO have become examples of universal Windows drivers. For more information, seeSample audio driver.

Programming interfaces available for universal Windows drivers for audio

Beginning with Windows 10, DPIs are part of OneCoreUAP-based editions of Windows. With this common set, you can write a universal Windows driver. These drivers run on Windows 10 Desktop and editions of Windows 10 Mobile and other versions of Windows 10.

The following DDIs are available when working with universal audio drivers.

• Audio-Controller-Event-Sets

• Audio Controller Interfaces

• Property sets for audio controllers

• Audio Controller Structures

• Audio Topology Node

• High Definition Audio DDI Reference

• Audio driver reference for the port class

Convert an existing audio driver to a universal Windows driver

Follow these steps to convert an existing audio driver to a Universal Windows driver.

1. Determine if existing driver calls are running on OneCoreUAP Windows. See the Requirements section on the reference pages. For more information, seeAudio Device Reference.

2. Recompile your driver as a universal windows driver. Set the target platform to "Universal" in the project properties.

   (Video) How to Download and Update Realtek HD Audio Driver on Windows 10 or Windows 11

3. Use the ApiValidator.exe tool to verify that the DDIs called by your driver are valid for a Universal Windows driver. This tool is part of the Windows Driver Kit (WDK) for Windows 10 and runs automatically when using Visual Studio 2015. For more information, seeUniversal Windows driver validation.

4. If the driver calls interfaces that are not part of OneCoreUAP, the compiler reports errors.

5. Replace these calls with workaround calls, workaround code, or write a new handler.

Creating an audio driver installation with components

overview

Divide the driver installation process into the following components for smoother, more reliable installation and better support for component maintenance.

• DSP (if any) and codec
• Apo
• OEM customizations

Optionally, separate INF files can be used for DSP and codec.

This diagram summarizes a component audio setup.

A separate INF extension file is used to customize each core controller component for a specific system. Customizations include tuning parameters and other system-specific settings. For more information, seeUsing an INF file extension.

An INF extension file must be a universal INF file. For more information, seeUsing a universal INF file.

For information about adding software using INF files, seeUsing a component INF filemiDCH design principles and best practices.

Send INF files in components

APO-INF packages must be sent to Partner Center separately from the base driver package. For more information on creating packages, seeIntroduction to Windows HLK.

SYSVAD component INF files

An example of INF files with components can be found in thesysvad/TabletAudioMuestra, sin github.

The traditional INF files are still available in the SYSVAD sampler.

Configure APO manufacturer specific functions and tuning parameters

All system-specific settings, parameters, and APO provider settings must be installed via an extension INF package. In many cases this is easily possible with theINF AddReg-Direktive. In more complex cases a tuning file can be used.

Basic driver packages should not rely on these customizations to work (although functionality may of course be limited).

UWP audio settings apps

Use hardware application support (HSA) for a Windows Universal Audio Driver to implement an end-user interface. For more information, seeHardware Support Application (HSA) steps for driver developers.

Programmatic release of UWP hardware support apps

Use the Windows Shell APIs to programmatically launch a hardware-enabled UWP app based on a controller event (such as when a new audio device is connected). Windows 10 Shell APIs support a method of launching the UWP UI based on feature activation or directly viaIApplicationActivationManager. For more details on the automated launch of UWP apps, seeAutomate the launch of Windows 10 UWP apps.

Using the APO Device Driver Provider and the AudioModules API

The Audio Module API/DDI was designed to standardize the communication transport (but not the protocol) for commands passed between a user-mode UWP app or service to a kernel driver module or script block. Audio modules require a driver that implements the correct DDI to support module enumeration and communication. Commands are passed in binary and the interpretation/definition is left to the creator.

Audio modules are not designed to facilitate direct communication between a UWP app and APO software running on the audio engine.

For more information on audio modules, seeImplementation of audio module communicationmiConfigure and query audio device modules.

Structure of APO HWID chains

APO Hardware IDs contain standard information and strings defined by the manufacturer.

They are structured as follows:

SWC\VEN_v(4)&AID_a(4)&SUBSYS_ n(4)s(4) &REV_r(4)SWC\VEN_v(4)&AID_a(4)&SUBSYS_ n(4)s(4)SWC\VEN_v(4)&AID_a( 4)

Where from:

• v(4) is the 4-digit identifier for the APO device manufacturer. This is managed by Microsoft.
• a(4) is the 4-digit identifier for the APO, defined by the APO provider.
• n(4) is the 4-digit identifier that PCI SIG assigns to the subsystem vendor for the parent device. Usually this is the OEM ID.
• s(4) is the manufacturer-defined 4-digit subsystem identifier for the parent device. Usually this is the OEM product identifier.

Plug and Play INF version and date evaluation for driver update

The Windows Plug and Play system evaluates the date and version of the driver to determine which driver to install when multiple drivers are present. For more information, seeHow Windows classifies drivers.

To enable use of the latest driver, make sure to update the date and version for each new driver release.

APO driver registry key

For APO/Audio driver registry keys set by third parties, use HKR.

Use a Windows service to facilitate UWP <-> APO communication

A windows service is not strictly required to manage user mode components like APO. However, if your design includes an RPC server to facilitate UWP <-> APO communication, we recommend implementing this functionality in a Windows service that controls the execution of APO in the audio engine.

Create Sysvad Universal Audio Sample for Windows 10 Desktop

Follow the steps below to build the sysvad sample for the Windows 10 desktop.

1. Locate the desktop INF file (tabletaudiosample.inf) and set the Vendor Name to a value like "Contoso".

2. In Solution Explorer, select and hold (or right-click) the sysvad solution and select Configuration Manager. If you are deploying a 64-bit version of Windows, set the target platform to x64. Make sure the platform configuration and settings are the same for all projects.

3. Build all projects in the sysvad solution.

4. Locate the output directory to create the build. For example, it could be in a directory like this:

   C:\Programmarchive (x86)\Windows Kits\10\src\audio\sysvad\x64\Debug\package

5. Copy the following files to the system where you want to install the sysvad driver:

Install and test the driver

Follow these steps to install the driver usingPnpUtilno target system.

1. Open an administrator command prompt and type the following in the directory where you copied the driver files.

   pnputil -i -a tabletaudiosample.inf

2. The sysvad driver installation should be complete. If errors occur, you can check this file for additional information:%windir%\inf\setupapi.dev.log

3. In Device Manager, from the View menu, select Devices by Type. In the device tree, locate Microsoft Virtual Audio Device (WDM) – Sysvad Example. It is usually located in the Sound, video and game controllers node.

4. On the target computer, open the Control Panel and navigate tohardware and such>Manage audio devices. In the Sound dialog box, select the speaker icon labeled Microsoft Virtual Audio Device (WDM) – Sysvad Example and select Set as default but not OK. This keeps the sound dialog open.

   (Video) Optimizing your Windows Computer for Audio

5. Locate an MP3 or other audio file on the target computer and double click to play it. Then, in the Sound dialog box, verify that the volume meter associated with the Microsoft Virtual Audio Device (WDM) driver is active: Sysvad Sample.