Support

Email support@dfacto.ai — we reply within 2 business days. Bugs and build problems are better as GitHub issues, where the answer is public and helps the next person.

Nowhere. Audiowire has never been released on any platform. You can build the engine, the background service and the command-line client from source and run them against a fake backend, which is genuinely useful for reading the code and useless for routing audio. The install guide covers building.

Expected, on macOS and Windows. On macOS an unsigned AudioServerPlugIn is silently ignored on a Mac with SIP enabled, and there is no Developer ID certificate yet — the one machine where the driver has loaded runs SIP with its filesystem protections switched off, which is not something anyone should be asked to do. On Windows the kernel driver has never been compiled at all. On Linux a virtual device does appear, and audio does round-trip through it.

Also expected, and it is the honest limit of the platform today. The device works as a loopback cable: what is played to it comes back out of it at unity gain. What does not yet reach it is the mix you built — sources, per-wire gain and the matrix are computed by the engine and then have nowhere to go, because the shared-memory transport between the engine and the driver has never carried a frame. The bug behind that is found and fixed in the driver source; installing the fixed driver needs root and has not been done, so nothing about it is proven.

This is the one real support answer we already have, and it cost four failed attempts to find: PipeWire on its own links nothing. Without a session manager — WirePlumber — the nodes appear, playback hangs until it is killed, and the capture is silent, with no error anywhere explaining why. A desktop always has one running; a container and a minimal server install do not. Start one, and the same test passes.

Because a virtual audio device is a driver. On macOS it is an AudioServerPlugIn that must live in /Library/Audio/Plug-Ins/HAL, which only root can write; on Windows it is a kernel-mode driver. Linux needs no driver at all. The background service never runs as root and is built so that it cannot ask to: elevation happens once, in a separate installer, and never again.

No, and that is settled rather than undecided. A HAL plug-in installing into /Library/Audio/Plug-Ins/HAL cannot be sandboxed, so the App Store is closed to this kind of product. Direct download only.

Not yet applicable — no key has ever been issued. When one has: the key is the licence, it is verified offline by a signature check on your own machine, and it therefore keeps working with no internet access. There is no account to log into and no activation server to be down.

macOS 14 or later (14.4 for per-app capture); Windows 10 build 1809 or later (build 20348 for per-app capture); Linux with PipeWire 0.3.4x or later. These are the targets in the spec — none of them has a shipping build.

The user guide is written ahead of the product, so behaviour is specified before it is built, and every page that describes something which has never run on real hardware says so. Start with concepts, or troubleshooting if something is already misbehaving.