Forget latency

Thunderbolt™ Beta Driver for Windows

Now compatible with Discrete 4, Discrete 8, Orion Studio, Zen Tour, Orion 32+, Goliath HD, Goliath and Zen Studio+.

Antelope Audio Windows Thunderbolt™ Driver

Windows Thunderbolt™ Driver Beta

The long-awaited Windows Thunderbolt™ Driver is now in Beta testing phase. It’s currently available for almost all Antelope Audio Thunderbolt™ interfaces. It’s still being tested but it’s stable, fast and maintains low latency levels even on busy sessions.

Тhe driver was built by Antelope Audio from the ground-up with stability and low latency in mind.

Here’s all the info you need in order to try it out for yourself.

Supported devices

The Windows Thunderbolt™ driver requires special firmware support and will work only with the following devices: Discrete 4, Discrete 8, Orion Sudio Rev2017, Orion Sudio, Zen Tour, Orion 32+, Goliath HD, Goliath and Zen Studio+

The driver also requires the latest Control Panel and Manager Service.
Make sure you’re using the latest firmware versions.

Features and limitations

The Antelope Audio Windows Thunderbolt™ Driver is still in Beta. Even though it’s currently stable, not all functionalities are implemented and some limitations are present.
The devices are not yet Windows certified and should be manually allowed to operate.

Windows Thunderbolt™ Driver Beta features

• Ultra-low (down to sub-millisecond digital round-trip) latency ASIO playback and recording
• Accurate digital latency reporting for correct DAW delay compensation
• Low CPU requirements and support for working in Power Saver mode

Driver limitations

• Currently the driver supports only ASIO
• Windows Audio (Port Class Audio) is currently not supported. Until we have support, you can use third-party tools like VB-Audio VoiceMeeter to play Windows Audio over ASIO
• Only one device at a time is supported
• Only one ASIO application at a time is supported

Getting Started

System requirements

Windows 10 PCs supporting Thunderbolt™ 2 or Thunderbolt™ 3
Thunderbolt™ controller (either integrated or via add-on card)
Thunderbolt™ software from Intel should be installed (please check your motherboard manufacturer to download the driver)

Setting Up

  1. Make sure you have “Thunderbolt™ Software” installed.
  2. Download and install the latest Antelope Audio Windows Thunderbolt™ Driver.
  3. Connect the device. A warning will appear stating “This device may not work properly”. The warning appears because the device is not yet certified for Windows, you can safely ignore it.
    A prompt may appear to ask if the device can connect. Select “Always Connect”.
  4. Download and install the Antelope Launcher from here.
  5. Open the Antelope Launcher and update.
  6. You should be ready to go. Configure your device from the Control Panel and use your favorite DAW to playback and record!
  7. Please note that Windows Audio is not yet supported, only ASIO. Check the Advanced section for a workaround using third-party software.

If we can be of assistance, please do not hesitate to contact us at

You can download the Thunderbolt™ Beta Driver for Windows from the following links:

Download Thunderbolt driver for Windows 10 (64-bit)

Download Thunderbolt driver for Windows 10 (32-bit)


Q: What do I need to connect my device via Thunderbolt™?

A: You’ll need a computer, equipped with a motherboard that supports Thunderbolt. If the motherboard doesn’t have a Thunderbolt™ port, you’ll also need a Thunderbolt™ AIC (Add-in Card). You’ll need a Thunderbolt™ 2 cable. If the port on your computer or AIC is Thunderbolt™ 3 (Type-C) you’ll also need a Thunderbolt™ 3 to Thunderbolt™ 2 adapter.

Q: Is there a list of supported configurations?

A: Every computer with a Thunderbolt™ 2 or Thunderbolt™ 3 support should work.

Q: My computer doesn't have a Thunderbolt™ port. Can I install a Thunderbolt™ AIC (Add-in Card)?

A: It depends. Thunderbolt™ requires explicit support from your motherboard. Check your motherboard specifications or contact the manufacturer to see if it supports a Thunderbolt™ AIC.

Q: I have a computer with USB Type-C port, will the driver work?

A: It depends. All Thunderbolt™ 3 ports are Type-C. However, not all USB Type-C ports support Thunderbolt. Type-C ports that do so will have the Thunderbolt™ logo besides them. It’s best to check your motherboard documentation to see if your port supports Thunderbolt.

Q: My motherboard doesn't have a Thunderbolt™ port, but supports Thunderbolt™ via an AIC (Add-in Card). What Thunderbolt™ AIC should I use?

A: It’s best to check with your motherboard manufacturer for a list of supported AICs. Typically, you can use an AIC from the same motherboard manufacturer.

Q: Do I need to change any BIOS/UEFI settings in order for Thunderbolt™ to work with the device?

A: Usually the default settings are OK and the device should be able to connect. There might be Thunderbolt™ settings that can prevent the device from connecting. The first one is “Thunderbolt Security” or ” Thunderbolt Authentication”. It should be set to “None” or “User” – depending on the motherboard. The other one is for Thunderbolt™ PCI support. This one should be enabled.

Q: What cable should I use?

A: Since the device port is Thunderbolt™ 2 you’ll need a certified Apple Thunderbolt™ cable.
If you need longer cable, we recommend using an optical cable.

Q: My computer should be supported and configured correctly, however, it still does not detect the device. What should I do?

A: Try updating your BIOS to its latest version. Also, you might want to update the Thunderbolt™ firmware to the latest version. Check your motherboard and Thunderbolt™ AIC (Add-in Card) manufacturer instructions on how to do this.

Known issues

Degraded performance on laptops after Windows April 2018 Update (1803).

Workaround: Disable “Power Throttling” from registry and restart:
Run “regedit”. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power. Create a new Key “PowerThrottling” if not present, and a new DWORD value “PowerThrottlingOff” under the key, then set the value to “1”. Restart the computer.
You can follow this guide for detailed instructions:

Changing the current Power Plan during playback / recording is not supported.

Workaround: Select and configure your Power Plan before starting a playback / recording session.

Upgrading the driver while device is connected MAY lead to Windows requiring a restart.

Workaround: Disconnect the device before upgrading the driver.

Background tasks may disrupt playback in some DAWs.


Some DAWs register themselves to the Multimedia Class Scheduler service (MMCSS), which can throttle the audio processing threads to allow for lower-priority and background tasks to run. This causes background tasks to preempt the DAW and the ASIO driver, which causes spikes and dropouts.
We’re working with Steinberg to fix the issue.


  1. Disable Multimedia Class Scheduler service from the registry:
    Run “regedit”. Go to Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MMCSS. Change the value of “Start” to 4. Restart the computer. This will permanently disable the service.
  2. Set the DAW process priority to real-time. Either start the DAW as Administrator, or set it manually from Task Manager: After you’ve started it, open Task Manager, click on “More Details”, find the DAW, right-click and select “Go to details”, right-click on the process executable and select “Set Priority -> Realtime”. Confirm the prompt by clicking “Change priority”.


Latency reporting

The driver accurately reports digital (i.e. no AD/DA) input and output latency.
The reason why the driver reports only digital latency is the complex routing and various external devices that might be involved. Different channels might be played to/recorded from different destinations/sources. In this case it’s not clear which latency should be reported, and in case of external gear, the driver cannot calculate the latency.
If you can, you can use external tool like CEntrance Latency Test Utility to determine the exact latency and tune your DAW.

Driver tweaking

The driver tries to provide stable playback and recording by adding some safety TX (playback) & RX (recording) offsets to the ASIO buffer. You can experiment with lowering the default values for better latency.
The safety offsets give the driver a little headroom for filling and draining the device internal buffers. This headroom is needed because Windows can add a delay before executing the driver code for various reasons – another driver that takes long time to process an interrupt or a DPC, scheduling other tasks before the DAW, or just a slow/overloaded CPU.
The safety offsets add different delay of samples depending on the sample rate. One unit is equal to 2 samples at 44.1/48kHz, 4 samples at 88.2/96kHz, 8 samples at 176.4/192kHz. This way you don’t need to change the safety offset when switching to a different sample rate.

Using VB-Audio VoiceMeeter for Windows Audio over ASIO

VB-Audio have released a great software VoiceMeeter – that can be used to play Windows Audio using our ASIO driver.
This is only a temporary solution while we develop our native Windows Audio driver.
Once you install it, open the VoiceMeeter application (available in the Start Menu under VB-Audio), and select “ASIO: Antelope Audio Thunderbolt” for Hardware out:
Select “VoiceMeeter Input” as default Windows playback device, and “VoiceMeeter Output” as default recording device.
Note that since our ASIO driver does not support multi-clients at the moment, you cannot use our ASIO driver within a DAW and for VoiceMeeter at the same time. To use a DAW, first select another device for Hardware out in VoiceMeeter before opening the DAW; close the DAW and select back “ASIO: Antelope Audio Thunderbolt” to use Windows Audio again.
Another option is to use the “VoiceMeeter Virtual ASIO” device in your DAW, that can be used together with VoiceMeeter Windows Audio device.
You can check the VoiceMeeter settings and options to achieve better latency. However, the defaults should be stable and good enough for most users. If you’re experiencing clicks and pops, from the VoiceMeeter setting dialog (Menu -> Systems settings / Options…) increase the ASIO buffers size in “Buffering ASIO”.

About Scheduling, Priorities, and Multimedia Class Scheduler Service (MMCSS)

To achieve stability and low-latency the driver needs to process the audio in real-time. While the driver itself is not CPU-intensive, it needs to be scheduled for execution by the OS as soon as data is available. The same applies for the DAWs. In order to guarantee that latency-sensitive applications are scheduled as soon as possible, they run with high (or even real-time) process and thread priority.
Windows provides a special service for multimedia applications – the Multimedia Class Schedule Service (or MMCSS for short). Instead of dealing with scheduling priorities manually, each thread in the application can register itself to the MMCSS, and the service automatically raises the thread priority. Most of the time this works great. However, there is a catch – if the thread exceeds a given time quota, the service drastically lowers the thread priority in order to allow background tasks to run. This means that if you’re using lower buffer sizes and there is another task running in the background, the MMCSS might decide to drop the priority of the DAW and driver threads, the background task will preempt them, and you’ll hear crackling.
Different DAWs behave differently – some of them register with the MMCSS, other manually manage the scheduling priority. We provide a checkbox in the ASIO Settings Control Panel to select whether or not the driver thread itself should register with the MMCSS. It should match the behavior of the DAW.
While it would be best if no background tasks are running during your session, you can’t always guarantee that this is the case. In case you are experiencing crackling due to background tasks taking over the CPU, try toggling the MMCSS registration checkbox in the ASIO Settings Control Panel, or try disabling the MMCSS altogether and manually set the DAW to real-time priority. Check “Known issues” section for instructions on how to do this.

We’re communicating the negative effects of the MMCSS with the maintainers of ASIO Standard (Steinberg) and we’re hoping that more drivers and DAWs can make the MMCSS registration optional.