WASAPI Driver for ASIO – open-source driver for using Cubase, no interface (beta coming soon)

ok thank you!

Hi everyone, and thanks again @Psychlist1972 for the guidance. Version 0.9.9 is out as a public beta:

Repo (GPL-3.0): GitHub - irregbex/WASAPI-Driver-for-ASIO: Free, open-source ASIO driver for Windows 10/11 on top of WASAPI (IAudioClient3). Use Cubase, Ableton, Resolve and other DAWs without an audio interface. Shared or Exclusive mode, x64/x86/Arm64X. · GitHub
Download: Releases · irregbex/WASAPI-Driver-for-ASIO · GitHub

What’s done:

  • IAudioClient3: runs at the device’s native rate (10 ms period here) with an internal sinc resampler when the project rate differs.
  • Arm64X: one DLL (ARM64 + ARM64EC), built with MSVC on a GitHub Windows ARM64 runner and verified with dumpbin. The installer registers it once, so native ARM64 and emulated x64 hosts both use it. Not tested on real Arm hardware yet - testers welcome.
  • Hardening: exception barriers on every entry point, host argument validation, bounded waits on device I/O, plus fixes from a full review (CODE-REVIEW.txt).
  • Tests: 18 offline suites incl. fuzzing under ASan/UBSan; a release only builds if all pass. The test tool also hammers the real driver with invalid host calls.
  • TraceLogging: own provider and GUID, a .wprp profile and Start/Stop trace scripts for bug reports. No audio data is traced.
  • Shared mode by default, so the DAW and the rest of Windows can play at the same time; Exclusive mode is optional.

Tested for hours in Cubase 15 and DaVinci Resolve (Bluetooth, sleep/resume, buffer and rate changes). Reports welcome on GitHub Issues.

@Psychlist1972, a question about code signing: Azure Artifact Signing isn’t available to individual developers in my country (Chile), so my plan is to apply to SignPath Foundation (free certificates for open-source projects, signing only builds from the public GitHub Actions pipeline). Before I apply: is a SignPath Foundation certificate a good path for an ASIO driver DLL and its installer from the Windows point of view (SmartScreen reputation, Smart App Control, the upcoming Baseline Security Mode)? Or would you recommend a different option for an individual open-source developer outside the US/Canada?

Thanks!

Oh? I haven’t heard that before. Thanks for the info. Is there any website with background knowledge for this? Any list of devices that offer <10ms latency?

I think @Psychlist1972 gave an answer before or I read it somewhere. 10ms is a system limitation. It’s the lowest it can go because it is the smallest chunk of data y will process. But some systems can do less.

The current ASIO oficial drivers are closed source so I don’t have access to a lot of internal information,

I don’t have a list of devices anywhere that support IAudioClient3. As I recall, no USB devices with our current UAC2 driver will return anything lower than 10ms, but some on-board audio does. But it’s been a decade since I looked at that.

Audio clients request a specific periodicity from the audio engine with the PeriodInFrames parameter to IAudioClient3::InitializeSharedAudioStream. The value of PeriodInFrames must be an integral multiple of the value returned in the pFundamentalPeriodInFrames parameter. PeriodInFrames must also be greater than or equal to the value returned in pMinPeriodInFrames and less than or equal to the value of pMaxPeriodInFrames.

For example, for a 44100 kHz format, GetSharedModeEnginePeriod might return:

  • pDefaultPeriodInFrames = 448 frames (about 10.16 milliseconds)
  • pFundamentalPeriodInFrames = 4 frames (about 0.09 milliseconds)
  • pMinPeriodInFrames = 48 frames (about 1.09 milliseconds)
  • pMaxPeriodInFrames = 448 frames (same as the default)
    Allowed values for the PeriodInFrames parameter to InitializeSharedAudioStream would include 48 and 448. They would also include things like 96 and 128.

They would NOT include 4 (which is smaller than the minimum allowed value) or 98 (which is not a multiple of the fundamental) or 1000 (which is larger than the maximum allowed value).

Pete
Microsoft

Appears so.

Open source: SignPath Foundation

If your project is open source, SignPath Foundation offers free code signing for qualifying open-source projects. The program provides OV-level certificate signing through a managed pipeline. Check the SignPath Foundation website for eligibility requirements and the application process.

ASIO drivers aren’t really “drivers”, so validation / signing falls into the same category as apps.

Pete
Microsoft

Thank you for the information!

Also, I’ve found some stuff out, I’ll update the documentation to reflect this information. No wonder the latest ASIO driver never worked for me. It may have worked well enough for other people.

Since this keeps coming up, here is the short answer once and for all.

Steinberg ships two generic drivers: the old “Generic Low Latency ASIO Driver” (no longer developed) and the current “Steinberg built-in ASIO Driver” 1.0.9. Note that the built-in driver’s panel still shows the old name in Spanish, French and Italian, which adds to the confusion. This is a Steinberg error, not mine.

What WASAPI Driver for ASIO does differently (tested on my machine):

  • Follows the Windows default output. The built-in driver only lists specific devices; you must pick one by hand.
  • Bluetooth: with the built-in driver the headphones must already be connected when you select them, and if they disconnect the selection is lost and you have to set it again. Mine moves to the next device and comes back by itself when the headphones reconnect.
  • Shared mode: the built-in driver is shared too (other apps keep playing), but its shared mode is tied to one fixed device: it does not follow Windows and does not survive a disconnect. Mine is shared by default and follows the system, with Exclusive as an option. The old Generic driver is exclusive and silences other apps.
  • Up to 3 extra devices with clock-drift correction, routing and per-app loopback.
  • Arm64X DLL for Windows on Arm, plus a 32-bit DLL.
  • Logs, a diagnostics tool, an automatic host test and TraceLogging for bug reports.
  • Open source (GPL-3.0).

If the Steinberg driver works for you, keep using it. If you need any of the above, try this one. Full comparison table in the README: GitHub - irregbex/WASAPI-Driver-for-ASIO: Free, open-source ASIO driver for Windows 10/11 on top of WASAPI (IAudioClient3). Use Cubase, Ableton, Resolve and other DAWs without an audio interface. Shared or Exclusive mode, x64/x86/Arm64X. · GitHub

Lenovo Ideapad Slim 5X
Snapdragon X Plus (Qualcomm Aqstic) 44100Hz

  • Buffer 256 → 18.1 ms
  • Buffer 128 → 14.4 ms
  • Buffer 64 → 12.9 ms
  • Buffer 32 → 12.2 ms

@Jari_Junttila thank you, that is the first report from a Snapdragon X machine. Your numbers look consistent with Shared mode: after subtracting the buffer, about 11.5 ms stays constant (the Windows engine period), which is why going from 64 to 32 barely helps. Could you tell me:

  1. Was this WASAPI Driver for ASIO, and which version (title of its control panel)?
  2. Is your Cubase the native Arm64 build or the x64 one running under emulation?
  3. Is the figure the output latency, the input latency or both added?
  4. Shared or Exclusive mode?
    If it was this driver, it would also help a lot if you could run WasapiDriverTest (Start menu > WASAPI Driver for ASIO) and post the “Summary” block: on your machine it exercises the Arm64EC half of the Arm64X DLL.

Thank you!

@irregular

  1. Latest version 0.9.10
  2. Cubase ARM(the one they offer)
  3. It was only output
  4. Those were Shared mode, Exclusive mode just added more latency
    I´ll do the test as soon as I can
    WasapiDriver-diagnostics.zip (5.4 KB)

in my latop with Windows 11 it works fine and I´m currently using it.

At my home studio with Windows 11 and Audient interface it has too much latency for recording not close to Audient asio driver, it has similar latency to steinberg driver.

Hello @Jari_Junttila Thank you for the information!

@diegoalejo15 Awesome that it works on your laptop! and in your home studio, yes, that is to be expected. My intention in working in this driver is the added functionality like bluetooth connecting quickly. Thank you for the information! it really does help!

WASAPI Driver for ASIO - final status (0.9.15) and project pause

Hi all, a last update before I put this project on hold.

Current version: 0.9.15 (public beta, free, open source, GPLv3)

What works well (tested on Windows 11 x64 with Cubase 15):

  • Playback through any Windows device: built-in sound, USB, HDMI and Bluetooth headphones, in Shared mode with low latency (IAudioClient3). Hours of use, device switching (Bluetooth on/off) and sleep/resume without errors.
  • Rate conversion when the project and the device run at different rates (built-in sinc, optional soxr).
  • Recording in Shared mode: clean at buffers 256 and 512 since 0.9.12 (tested with a Steinberg UR22mkII).
  • Native ARM64 hosts on Windows on Arm (thanks Jari for testing on a Snapdragon X Plus).

Known limitation (KI-13, not fixed):

  • Recording in Exclusive mode with a buffer smaller than the device’s capture period (256 at 44.1 kHz in my tests) does not work correctly: input drops and the output runs late. I tried several fixes in 0.9.12 - 0.9.15 and none solved it, so I am documenting it instead of guessing further.
  • Workaround: use Shared mode, or Exclusive with a buffer of 512 or larger.
  • If you have an interface with its own ASIO driver, that driver will always be the better choice for recording. This project is meant for the devices that have no ASIO driver.

Also worth knowing:

  • Current DaVinci Resolve versions have an I/O Engine called “System Audio” that uses Windows audio directly, so you do not need an ASIO driver there.
  • The x64-on-Arm (ARM64EC) half of the Arm64X build is still untested on real hardware.

Everything is documented in KNOWN-ISSUES.txt, FAQ.txt and TEST-GUIDE.txt inside the download. The project stays online and bug reports on GitHub are welcome, but development is paused for now.

Thanks to Pete for the hardening and signing advice, to Jari for the Arm tests, and to everyone who tried it and reported back.

I just found this information here in the Dorico Forum, from one of the developers.

This is new for me, so I thought you would like to know this as well.

Hello @JuergenP I’m off work on wednesday so I’ll check it then. Thank you!

Hello @JuergenP The older Built in ASIO Driver was wrongly named in 4 of the 6 languages. I can only think that this driver was not given much thought. This made me have to explain why I was running an old version. I was not, I was just in spanish, here is a chart with the wrong names, this was a Steinberg problem, not mine,

What is interesting is that it made my double check what they were saying in another thread and this is what I was able to solve:

So, while the stock Built-in ASIO driver can work as Shared it can only be called “”“Shared”“” but it works behind Windows and the volume control is not part of windows. This is not the approach that I was looking for in the driver that I vibecoded…

Anyways…

WASAPI Driver for ASIO 0.9.16 - tested with Cubase 16 on release day

Hi all, a short update now that Cubase 16 is out.

Version 0.9.16 (public beta, free, open source, GPLv3):

0.9.16 has the same driver code as 0.9.15. I tested it with Cubase 16.0.0 (x64, Windows 11) on its release day and only the version number and the documents changed.

Short video introduction (2.5 minutes, English) of WASAPI Driver for ASIO 0.9.16, tested with Cubase 16:

It shows what the driver does, how to install it, where to select it in the new Cubase 16 Settings window, and what to try if something doesn’t sound right. The default settings should work for most setups.1

What I tested in Cubase 16:

  • Selecting the driver in the new Edit > Settings > Audio window. The panel opens from the button next to “Audio Driver”.
  • Changing the buffer 256 → 512 → 256 while the project plays (Settings is non-modal now): 0 glitches.
  • The new ASIO-Guard levels (Level 5): 0 glitches.
  • Bluetooth earbuds into the case and back: output moved to the speakers and back by itself.
  • Recording from a Steinberg UR22mkII in Shared mode at buffer 256: inputs clean.

Good to know:

  • Cubase 16 stops the transport when it opens an ASIO control panel. That is Cubase, not the driver: press Play again after closing the panel (FAQ 26).
  • With the UR22mkII (Yamaha Steinberg USB Driver) in Shared mode the “Output glitches” counter grows slowly although nothing is audible. It happens without a DAW too, so it comes from the device driver side (KNOWN-ISSUES KI-14).
  • KI-13 is still open: recording in Exclusive mode with a buffer smaller than the device’s capture period does not work correctly. Use Shared mode, or Exclusive at 512 or larger.

Reports with other DAWs and devices are welcome on GitHub (COMPATIBILITY.txt explains how).