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

Hi everyone!

For 20 years I’ve been asking Steinberg for a simple, low-latency driver that lets Cubase work with a Windows’ HD Audio driver work, much the way Ableton Live can just use your computer’s built-in audio driver without an audio interface. I never had the time to write my own driver. Recently I started using AI at work, and on a whim I thought: “what if I try this?” So I “vibe-coded” it together with Claude Cowork, and to my surprise, it worked… extremely well!

The result is WASAPI Driver for ASIO, a free, open-source (GPLv3) ASIO driver for Windows 10/11 that runs on top of Windows’ own audio system. It has been my daily driver in Cubase 15 for a while now, and I’m really happy with it.

What it does:

  • Lets Cubase use your computer’s built-in audio, HDMI monitors or Bluetooth headphones, with no extra hardware.
  • Uses low-latency Windows audio, as low as your laptop’s audio driver allows.
  • Windows sounds keep playing while Cubase is open (YouTube, Spotify, notifications…).
  • Adjustable buffer size, plus the option to combine more than one device.
  • A clean control panel with live meters, CPU load and dropout counters
  • Extremely well documented.
  • Also works in DaVinci Resolve, not just music software.
  • Pretty demoscene visuals because I’m old.

It complements Steinberg’s built-in ASIO Driver, aimed at people who want a bit more control and flexibility.

A public beta will open soon, and I’d especially love testers with notebooks and different audio hardware. I’ll post the download link here when it’s ready.

Thanks, and see you in the beta!

Not affiliated with Steinberg. ASIO is a registered trademark of Steinberg Media Technologies GmbH.

And also, to any programmer like me who have any questions… no… I did not program this. Claude Code did this. We are passing a frontier and to be frank… it is really scary. The funny this is is that I really am a programmer. :wink:

Love you all. :heart:


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

Hi all, a last update before I put this project on hold. Had to make a new one to check for Cubase 16 compatibility

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.

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).

Nice :slight_smile:

Three requests

  • For low-latency, please use IAudioClient3 if you’re using WASAPI. I assume you are given you mention low-latency, but wanted to double-check.
  • Please compile/link for Arm64X as well as x64. Arm64X is the type of binary that contains both Arm64 classic and Arm64EC in the same file, so it can be used by any app on Arm64 devices. Explanation here.
  • If you don’t already have a code-signing cert recognized by Windows, grab an Azure Artifact Signing account and code sign your installer and all the binaries inside it. Without code signing, many people will be unable to download it, and also Windows will block it by default in many cases (more of that coming in the future with Baseline Security Mode)

Pete
Microsoft

Thank you. Your feedback made a real difference. Here’s an update. Of course, this is still ViveCoded and untested thoroughly. I’ll begin soon. Oh, and I have no Arm64 hardware myself.

Claude’s comments:

IAudioClient3 / low latency (done today)
Before, the driver only used IAudioClient3 when the ASIO sample rate matched the Windows mix format; otherwise it fell back to standard shared mode with AUTOCONVERTPCM. As of today it always opens the device with InitializeSharedAudioStream at the device’s own rate and minimum period, and does the sample-rate conversion inside the driver (fixed-ratio, high-quality sinc). The reported latencies now include the converter delay, so recordings stay aligned. In my offline tests (Claude’s offline) the round-trip matches the reported latency to within a sample. It still needs testing on real hardware, which is next on my list.

Arm64X
Agreed, and thanks for the article. Right now I ship x64, x86 and plain Arm64, which as you point out only covers native Arm64 hosts. I’ll build Arm64X with MSVC on a GitHub Arm64 runner, so x64 hosts running under emulation and native Arm64 hosts can both load the same DLL. It will be in place before the public beta.

Code signing
Completely agree that unsigned downloads won’t fly, especially with Baseline Security Mode coming. Unfortunately, Azure Artifact Signing currently only accepts individual developers from the US and Canada, and I’m in Chile. My plan is to apply to the SignPath Foundation program for open-source projects once the repository is public, and sign the installer and every binary inside it. If you know of a better route for individual developers outside the US and Canada, I’d love to hear it.

Public beta coming soon. Thanks again for taking the time!

I don’t want to make any assumptions about your experience in the area, so please take the lessons-learned here as trying to help our mutual customers.

Having done a lot with Claude Opus 5 and 5.5 over the past months, here is an additional prompt you’ll want to throw it before you have a public release:

Harden this against untrusted, buggy, or malicious data from consuming apps and any external dependencies. Create fuzz tests to ensure the ASIO component continues to work and does not leak access into the hosting process or crash it. Re-review all code and ensure no leaking exceptions, and that UAF, TOCTOU, ABBA lock races, buffer overruns, and similar types of bugs are all correctly handled or avoided. Afterwards, remove any unused/dead code in the project and summarize the changes made.

You may also want it to verify that there are no infinite timeouts waiting on device IO, as those cause no end of problems, and not all devices (or their drivers) behave properly.

and if you don’t have them already:

Create a full set of unit tests, including the untrusted data fuzz tests, that fully exercises all code paths in the ASIO component. If needed, create a full ASIO host scaffold to run the tests. Require all tests pass before any release. Create new tests for any new features or bug fixes as you make them.

Finally, for customer testing, ensure the ASIO driver is instrumented with TraceLogging and that there’s a .wprp for it that can be shared with customers who are having problems. Otherwise, you will be just completely guessing. Here’s the .wprp we use for MIDI:

The MIDI Troubleshooting app has a page that runs the customer through the trace.

Hope that helps

Pete
Microsoft

Hello! Oh I’m not experienced in this. I am a programmer but never at this level. I’m glad to learn more though. Thank you for yout input. I’ll post more stuff when I get things setup.

Thank you.

Glad to help. On the trace logging, you can point your agent, when online, at the MIDI source code at GitHub - microsoft/MIDI: Windows MIDI Services · GitHub for how we do it. You don’t have the same constraints, but we don’t trace any private data from the customer. In our case, that means no MIDI messages (unless compiled to debug). In your case, that would mean no actual audio samples/packets.

The “TraceLoggingWrite” in this code is an example:

Implementation is here:

Despite the scary name, the logging only kicks in when there’s a trace listener like wpr.exe attached.

Pete
Microsoft

Hello Mr. Pete,

We can definitely start trying out stuff! I’ve never uploaded code to Github so I guess I will depend on anyone else trying it, but it has finished most tests and scenarios we suggested.

It actually runs very well. 10ms is the lowest it can go but this is due to hardware limitations. I welcome more suggestions.

Regards!

Felipe Cuadra.

Didn´t work on my ARM laptop, says can´t find hardware.
Lenovo Ideapad Slim 5X
Snapdragon X Plus
16 Gb

Hello!,

Well yes, it has not been made for ARM laptop. I don’t have an ARM laptop and I cannot do any testing in them. Would you be available for the testing?

@Psychlist1972 Can I get Microsoft Chile to “lend” me an ARM laptop for testing? I won’t keep it. I’ve got too many laptops already.

Regards.

Felipe C.

@irregular
Of course i can be tester, I use latest Cubase ARM version on my laptop, but i am not coder so I can´t compile anything, never worked for me., so installer needed

I don’t have any contacts in the region, unfortunately, and I don’t think they’ll have laptops to loan out if so.

If you are on GitHub, you can use the Arm64 GitHub runners for CI/CD if you have sufficiently good unit tests and they can be used without an actual kernel driver present. In the MIDI Repo, we have a “minmidi” driver that we can use in CI/CD. You could ask your agent to create a test harness for you, maybe with a similar type of driver, for audio.

Pete
Microsoft

BTW, if you are using Microsoft’s tools, they all cross-compile.

For Arm64, you want to compile to Arm64X which combines both classic Arm64 and Arm64EC. In that way, it will work no matter what kind of app is running on the Arm64 device, emulated or native. Note that Cubase itself is compiled to Arm64EC so it needs the Arm64X compiled library to load it on Arm.

I think I posted this earlier, but here it is again in case it helps.

Pete
Microsoft

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 · 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.

- Code signing: applying to SignPath Foundation (Azure Artifact Signing isn’t available to individuals here). Until then the beta is unsigned. Tested for hours in Cubase 15 and DaVinci Resolve (Bluetooth, sleep/resume, buffer and rate changes). Reports welcome on GitHub Issues.

Any comments are welcome.

Now it works perfectly on my windows ARM. Very nice job :+1:

Hello! I’m glad you find it useful. Just a reminder that it is all vibecoded with Claude. I am a programmer but I don’t have this kind of knowledge. I was trying to get back some projects and I thought I might ask Claude for a driver. I always needed this driver and I requested it for years! xD

Question. What software are you using it with? what driver did you use before?

Thank you!

Just small test with cubase 15 and groove agent 6, also tested the venus theory demo project .
Build in steinberg driver before, but also testing asio4all

I didn’t know Asio4all worked in arm64x, cool!

Thank you!

In that case, it’s running emulated, and an Arm64EC process can load x64 components running under emulation.

That is, unless they came out with a new version I was unaware of.

Pete
Microsoft

If you guys get a chance can you test latency in Arm64x?

Thank you!

WASAPI latency on an Arm64 device is going to be about the same as on x64. It ultimately depends on the underlying driver.

WASAPI Shared is around 10ms
WASAPI Exclusive can get into the single digits
WASAPI Shared Low Latency 100% depends on the underlying device supporting it, but can also get into the single digits.

Pete
Microsoft