In progress

WireLezz

A low-latency wireless headphone system that carries the computer's audio to a phone over Wi-Fi: an app and AU / VST3 plug-in on the Mac, receiver on Android. Test build 0.7.1 is available to members; test results and downloads are below.

AUVST3AndroidWi-FiLow latencyC++JUCEOboeGuitar

Mac · AU / VST3 · Android · Wi-Fi

Your phone and wired headphones become a wireless studio monitor.

You cannot play guitar through Bluetooth headphones: the sound arrives 150–250 ms after your fingers. WireLezz carries the computer's audio to a phone over home Wi-Fi; the headphones plug into the phone with a cable. Everything in your DAW (amp, effects, virtual instruments) reaches your ears as is, and you can walk around the room without being tied to the computer. The protocol, audio engine, Mac plug-in and Android receiver were written from scratch.

~19ms best end-to-end (estimated)
0.67ms packet size
0compression
20kHz flat response
−87dB distortion + wobble
4phones tested

How it works

Sender on the computer, receiver on the phone; every millisecond in between is measured.

Sender on the Mac

The WireLezz Send plug-in (AU / VST3) sits on the master output, passes audio through untouched and sends it to the phone at the same time; it adds no latency itself. Tested in Logic and Reaper. A small tool can also send from any audio input without a DAW.

Uncompressed, tiny packets

Audio travels as 16-bit PCM in 0.67 ms (32-sample) UDP packets; no codec, no codec delay. Each packet also carries a copy of the previous one, so a single lost packet is covered without adding latency. Packets are marked for Wi-Fi's priority "voice" class.

Adaptive buffer

Wi-Fi delivers packets unevenly. The receiver keeps the smallest safe buffer based on the worst moment of the last few seconds: it trims latency when the network is calm and grows its margin after a stall. Clock drift between the devices is corrected with inaudibly small speed changes (±100 ppm).

Android receiver

Uses the phone's fastest audio path (AAudio, exclusive MMAP when available) and Wi-Fi's low-latency mode. It finds the Mac on the network and reconnects on its own. An old phone can be turned into a dedicated receiver that opens straight into WireLezz.

Test results: phones

Same sender (wired Mac), same 5 GHz network, four different receiver phones.

PhoneAndroidAudio pathAndroid outputEnd-to-end
Samsung Galaxy A3617exclusive MMAP, 96 frames~7–8 ms19–29 ms
Realme 1113shared, 256 frames15–17 ms23–27 ms
Tecno Pova 312shared, 256 frames17–18 ms27–35 ms
Redmi Note 6 Pro9shared, 192 frames, underruns~30 ms~60 ms

End-to-end figures are the receiver's own estimate: network, buffer and Android output added up; the DAW buffer and audio interface on the computer are not included. An acoustic loopback measurement has not been done yet. The Samsung was measured on its speaker; a headphone adapter may change the figure. For comparison: Bluetooth headphones are 150–250 ms.

Test results: network and computer

Latency depends most on the phone and on how the computer reaches the network.

SetupEnd-to-endNote
Mac mini wired to the router, Reaper, guitar23–27 msmost stable setup
MacBook on Wi-Fi, Logic, guitar34–38 msaudio crosses the air twice
MacBook joined directly to the phone's hotspot28–34 msbetter on paper, felt slower by ear
Mac on Wi-Fi with AirDrop/Handoff (AWDL) on~115 ms31 ms with AWDL off
DAW buffer at 512 samples40–60 msconstant dropouts; the plug-in now warns

A cable still wins

With the computer wired to the router, audio makes a single wireless hop. A laptop on Wi-Fi adds ~10 ms and more jitter.

AWDL, the silent enemy

macOS uses AWDL for AirDrop and Handoff and occasionally moves the Wi-Fi radio to another channel: 40–170 ms stalls. Turn it off while the Mac is on Wi-Fi.

A hotspot on the same channel

A forgotten phone hotspot broadcasting on the router's 5 GHz channel made the receiver retransmit 29% of its packets; switching it off cut the longest gap from 132 ms to 27 ms.

Choosing a phone

Recommended: Android 10 or later with low-latency audio. Android 9 has no low-latency Wi-Fi mode, and older phones can spend 30 ms on audio output alone.

Test results: sound quality

Two flaws heard by ear were measured, fixed and turned into tests.

MeasurementFirst buildNow
15 kHz tone level (with clock drift)−1.30 dB0.00 dB
19 kHz tone level−2.65 dB−0.13 dB
Wobble + distortion at 10 kHz (50 ppm drift)−29 dB−87 … −92 dB
Distortion + noise at 1 kHz−75 dB−87 dB

In the first build the guitar's top end sounded dull and slightly smeared. Two causes: the 4-point interpolation used for fractional reads rolled off the highs, and the speed correction that absorbs clock drift swung up to ±1500 ppm, wobbling the treble. Interpolation moved to a 32-point windowed sinc and speed correction was capped at ±100 ppm. In a side-by-side listen afterwards, the only remaining difference was level.

Automated tests

Every change runs through a simulation of real Wi-Fi's bad moments.

Scenario (90 s)Average bufferResult
Clean network3.9 msno dropouts, no clicks
80 ppm clock drift between devices3.5 msdrift caught as −62 ppm, no dropouts once settled
Typical Wi-Fi jitter (1.5 ms)~15 msno clicks
1% packet loss~10 ms9532 chunks recovered from the redundant copy, no clicks
A single 100 ms outage—accumulated delay skipped quietly, back to normal in seconds
10 s of bad Wi-Fi, then calm—safety margin back to normal within 30 s

A real-UDP loopback test, protocol tests and 1–19 kHz tone level and THD+N measurements also run automatically. The Mac plug-in passes pluginval (strictness 7) and Apple's auval validation.

Early access

WireLezz is in testing and available to members only: the Mac app and plug-in (Apple Silicon and Intel, macOS 11+) and the Android receiver are in the Download section below. Windows, Linux and iPhone builds are on the way; join the list and I will email you when they are out.

Last updated: 2026-11-15