[WIN] Audio driver types in the standalone app

Audio driver types available in SoundID Reference on Windows explained - features and particularities of each driver, and when to use them. 

 

In this article:

 

Audio drivers on Windows

Audio drivers are software components that enable communication between the operating system and the audio hardware installed in a computer. SoundID Reference drivers receive the audio signal, calibrate and send the corrected audio signal to the output device driver of the designated hardware device:

Flow_1.png

 

Most of the built-in audio solutions such as headphone ports and motherboard audio employ WASAPI drivers by default (WDM, DirectSound, or MME). Most external audio interfaces will include a WDM driver (driver framework developed by Microsoft for Windows) that allows communication with the operating system and other applications, providing support for plug-and-play functionality, power management, and other system features via the Windows Audio Engine.

Most external audio devices support both WASAPI and ASIO drivers, although some are limited to running a single driver at a time. Some audio interfaces are ASIO-exclusive, such as SSL 2+, Presonus Quantum 2626, Focusrite Red 8Pre, and more - such devices will not work with WASAPI drivers. This means ASIO-exclusive devices can be used with DAWs and professional audio applications only, as they are not natively compatible with the Windows Audio Engine for general music playback.

 

Setting up with the driver types in SoundID Reference

SoundID Reference supports four distinct driver types (two WASAPI-based options, and two ASIO-based options):

 

All four driver types are unique, and offer solutions for different needs and requirements. Based on your hardware compatibility, personal preference, or workflow specifics, one of the driver options listed above should work for you. Learn more about each driver type below.

The device and driver type selection is available during the Output Preset creation:

 

WASAPI_output_device.png

WASAPI output device

  1. Launch the SoundID Reference app
  2. Click on Add new output in the bottom-left corner
  3. Select the WASAPI device type
  4. Select one of the WASAPI driver options:
    • Virtual Windows audio driver
    • Windows audio device insert driver (APO)

 

ASIO_output_device.png

ASIO output device

  1. Launch the SoundID Reference app
  2. Click on Add new output in the bottom-left corner
  3. Select the ASIO device type
  4. Select one of the ASIO driver options:
    • Virtual Windows audio to ASIO driver
    • Virtual ASIO to ASIO driver

 

NOTE! It is not possible to change the device type from WASAPI to ASIO (or vice versa) after creating an Output Preset. To access the other device type driver options, you'll need to create a new Output Preset.

 

Virtual Windows audio driver (WASAPI)

The Virtual Windows audio driver will calibrate your entire computer audio (browser, music players, streaming apps, and other apps). This driver type will be using the SoundID Reference Virtual Audio Device, which will be set as your default sound output device when using the SoundID Reference app.

 

  • Ideal for system-wide calibration
  • Uses a virtual audio device
  • Latency performance: 40-160 ms
  • Considerable processing power required
  • Doesn't work with ASIO-exclusive devices
  • Possible clock synchronization issues

 

Learn more about this driver type here: Virtual Windows audio driver (WASAPI)

 

Flow_2_-_BACK.png

Virtual_Device__HOME_.png

 

Windows audio device insert (APO)

The Windows audio insert (APO) is a unique driver type, which acts as an insert on your output device. This driver type will be applied directly onto your output device via the Windows Audio Engine (similar to a plugin in DAW), and won't require a virtual audio device for processing the audio signal. 

 

  • Ideal for systemwide-calibration
  • Doesn't use a virtual audio device
  • Latency performance: 7-10 ms
  • Minimal processing power required
  • No clock synchronization issues
  • Can conflict with other APO drivers in use
  • May be incompatible with some device drivers

 

NOTE! When first selecting this driver type, it can take up to 1 minute to initialize when creating an Output Preset - during this time audio playback will be interrupted. It is possible other APO drivers used by Windows may not allow for this driver to load into the selected output device. 

 

Learn more about this driver type here: Windows audio device insert (APO)

 

Flow_3_-_APO.png

Insert__APO_.png

 

Virtual Windows audio to ASIO driver (WASAPI to ASIO)

This driver will be calibrating your computer audio the same way as the Virtual Windows audio driver, however, the audio signal will be routed from the SoundID Reference app directly to the output device ASIO driver (not going back into the Windows Audio Engine). This way you can benefit from the ASIO driver, especially if your audio interface is ASIO-exclusive.

 

  • Offers system-wide calibration for ASIO-exclusive devices
  • Uses a virtual audio device
  • Latency performance: 40-100 ms
  • Considerable processing power required
  • Can be used in parallel with other ASIO drivers
  • 'Adjust device output gain' setting not available

 

Learn more about this driver type here: Virtual Windows audio to ASIO driver (WASAPI to ASIO)

 

Flow_3_-_Virtual_Winodws_to_ASIO.png

Virtual_Device__WASIO_.png

 

Virtual ASIO to ASIO driver (ASIO to ASIO)

This driver type will calibrate your DAW output (or other audio applications running in ASIO) utilizing a virtual ASIO solution. The audio signal will be routed directly from DAW to your ASIO device, while the processing is taking place in the SoundID Reference standalone app, instead of using the SoundID Reference plugin format. The rest of your system playback won't be calibrated as ASIO drivers are incompatible with the Windows Audio Engine. 

 

  • Can be used as DAW audio output in ASIO
  • Can't be used for system-wide calibration
  • Latency performance: output device latency only
  • Minimal processing power required
  • No clock synchronization issues
  • 'Adjust device output gain' setting not available

 

NOTE! After creating an ASIO to ASIO Output Preset, make sure to assign it as your DAW output (see below). You might have to restart your DAW to see the SoundID Reference virtual ASIO device as an output option after creating the Output Preset.

 

Learn more about this driver type here: Virtual ASIO to ASIO driver (ASIO to ASIO)

 

Flow_4_-_Virtual_ASIO_to_ASIO.png

ASIO_to_ASIO_driver_DAW.png

 

For additional assistance with the SoundID Reference driver types on Windows, see in-depth articles on each driver type here:

Was this article helpful?

4 out of 5 found this helpful

Have more questions? Submit a request

0 comments

Please sign in to leave a comment.