Skip to content
No binaries · source builds

There is nothing to download yet

No installer exists for macOS, Windows or Linux, and no release has ever been published. What does exist is the repository, and it builds.

Why there is no installer

A virtual audio device is a driver, and a driver has to be signed before an operating system will load it. macOS needs a Developer ID certificate; Windows needs an EV certificate plus Microsoft attestation. Neither chain has started, and neither is shortened by writing more code. Publishing an unsigned installer would hand you something that fails silently — on macOS with SIP on, an unsigned HAL plug-in is ignored without an error anywhere.

Build it from source

This works today on all three platforms. It needs the pinned stable Rust toolchain from rust-toolchain.toml, and Node 20+ if you want the interface. Neither the engine nor its tests need a driver, audio hardware or root — which is the whole reason the engine could be written before any of the drivers loaded.

clonegit clone https://github.com/deepakmarathe/audiowire.git
buildcargo build --workspace
runcargo run -p aw-daemon -- --backend null --print-socket
testcargo test --workspace

cargo test --workspace runs 129 tests in about 50 seconds against an in-process fake backend. The interface is cd ui && npm install && npm run dev, and it drives a real daemon over a real socket.

What each platform can actually do

Reproduced from docs/spec.md §7. Nothing below is a plan — every line is something that has been observed to happen, or observed not to.

Linux

The one platform where audio has actually made the trip — and the one that is free permanently, because PipeWire already does this natively and charging for it would be indefensible.

  • The virtual device appears as both a sink and a source on PipeWire 1.2.8
  • Audio round-trips through it at unity gain with the channels intact — 369,664 frames, verified
  • A script drove that test, not the background service. The version that does has never been run
  • Per-app capture is not wired to the Linux backend yet
  • Monitors have never played the mix to a real output
  • .deb and .rpm packages build, but none has been published
provebackends/linux/scripts/roundtrip.sh

macOS

Audio round-trips and per-app capture works. What does not work is the part in between: the engine's mix cannot reach the device yet, so a macOS virtual device is a loopback cable with a name.

  • The background service creates, renames, re-channels and deletes the device, and the OS lists it within a second
  • 440/880 Hz round-tripped within 0.41 dB of unity, the other tone at least 51.9 dB down, zero stream faults
  • A process tap reaches the mixer at peak 0.549321 while a second app tapped at the same instant reads 0.000000
  • The engine's mix does not reach the device — the shared-memory path is fixed in the driver source and has never been installed
  • The driver loads on one machine with SIP's filesystem protections off. No stock Mac has loaded it
  • The installer package builds, unsigned, and has never been run. Shipping it needs a Developer ID certificate
drivercd backends/macos/driver && make

Windows

The furthest behind, and honestly so. The kernel driver was written on a Mac and has never been through a compiler.

  • The driver has never been compiled
  • No virtual device, no capture, no monitoring
  • Shipping needs an EV certificate and Microsoft attestation — a 10–17 business-day chain that has not started

Want to be told when there is a real installer?

That is the only thing this site asks for, and the only thing it will ever send: one message, when a row in the status table changes on your operating system.

Install and troubleshooting notes live with the code — docs/user-guide/install.md.