ml.Distance by alkman: Click-Free Distance and Panning
Most spatial tools in Live ask you to think in terms of wet/dry and pre-delay. ml.Distance asks you to think in terms of how far away the sound is and where it sits left to right. That difference in framing matters more than it sounds, because once distance is a single automatable value, the moves you make stop being mix decisions and start being arrangement decisions.
The device is alkman's alternative graphical interface for Robert Henke's original ml.Distance, with one functional change: distance and panning values are interpolated rather than jumping, and an extra smooth parameter sets how long that interpolation takes. That is the entire pitch, and it is a good one.
Why interpolation is the whole point
Anyone who has automated a spatial parameter with a MIDI controller or a steep automation ramp knows the failure mode: the value jumps between steps, and you hear clicks. On a sparse pad you might get away with it. On a percussive or sustained source, those discontinuities are the first thing the ear locks onto.
alkman's version smooths the path between values instead of snapping to them. The smooth control decides how lazy that path is. Short settings keep the response tight enough for performance gestures; longer settings turn a hard twist of a knob into a slow drift, which means you can write coarse automation and let the device do the fine work.
Practically, that changes how you author moves. You no longer need dense automation breakpoints to avoid artefacts. Draw two or three nodes, set smooth to taste, and the transition takes care of itself. It also makes the device genuinely mappable to a physical knob, which the original was harder to use for.
Version 1.1 fixed panning so it works when distance is set to 0 — worth knowing if you want pure lateral movement with no depth change. Version 1.2 fixed GUI elements rendering blurry on non-retina screens, a small thing that matters if you're squinting at a laptop on stage.
Three ways to put it in a session
A call-and-response vocal or lead. Put ml.Distance directly on the track, not a return. Leave the main phrase close and centred, then automate distance upward on the answering phrase so the repeat sits further back, with a small pan offset. Because the interpolation is doing the work, you can automate that across a single bar without hearing the move stutter. Set smooth short enough that the change lands on the beat rather than smearing past it.
A percussion layer that moves through the arrangement. Duplicate a shaker or rim loop, mute the original, and drop ml.Distance on the copy. Write a slow distance curve across sixteen or thirty-two bars so the layer walks from far to near across a build, with a matching pan sweep. With a long smooth setting, your automation can be blocky and the result will still be continuous. This is the use case where the device replaces three or four automation lanes of volume, filter and pan with one idea.
Live performance on a controller. Map distance and pan to two knobs, leave smooth at a medium setting, and treat the device as a hands-on positioning tool during a set. Throw a synth stab into the back of the room and pull it forward on the drop. The reason this works at all is the interpolation — with raw values, fast knob movement would be audibly steppy. Mono or near-mono sources give the clearest sense of placement; a wide stereo pad will smear the effect.
If you need the pitch-shifting side of movement rather than just placement, alkman has published a separate doppler version of the effect; the device description points to it.
What 58k downloads and a 5/5 rating tell you
58,532 downloads is a large number for a device that does one specific thing and is, by its author's own framing, a reworked interface for someone else's patch. The 5/5 rating across 21 comments backs that up. When a device is narrow and highly rated, it usually means the people who installed it knew exactly what they wanted and got it.
The other number worth reading is the update history. Added in January 2019, last updated 30 June 2025, currently at version 1.2. Six years of maintenance on a free utility is unusual, and both logged updates are responses to real user problems rather than feature padding. That is a reasonable signal that it will keep working through Live updates.
Requirements are Live 10.0.5 and Max 8.0.3, so anyone on a current install is covered. The license is Attribution-NonCommercial-ShareAlike, which matters if you plan to modify the patch and redistribute it, or bundle it into something commercial — check the terms before you do either.
Where it sits among comparable audio effects
The nearest relative in the audio effect catalogue is Circular Doppler by monolake, which shares the spatial premise but automates it for you: two virtual microphones rotate around a single source, with doppler delays, distance-dependent amplitude modulation and filtering, all synced to song position for reproducible results. That sync is the key difference. Circular Doppler gives you a repeatable orbit; ml.Distance gives you manual control over a static position that you move yourself. Pick the first for a rhythmic, self-running effect, the second when you want to decide where the sound is at every moment.
TapeStop by zalo, at 54,272 downloads and also rated 5/5, is a different kind of one-gesture performance device — a transport effect rather than a spatial one — but it lives in the same part of a performer's rack: mapped to a knob or a button, used in the moment, not in the mix. Same for Reverser by jabbone, a beat repeat that reverses the slice, at version 5.03 after a long maintenance history and 41 comments. If you're building a performance chain, these three cover placement, transport and slice mangling with very little overlap.
Ganz Graf Mod X by synnack is the odd one out in this group — a mod of vh's Ganz Graf with Max interface objects swapped for live.* ones so presets save to the Live library. It is included here because it shares an approach with ml.Distance: take an existing patch, fix the interface layer, make it behave like a proper Live device. That kind of rework is undervalued, and both devices have the download counts to show that users notice.
Who should skip it
- If you only need static placement. Live's own utility and panning tools handle a fixed position fine. ml.Distance earns its slot when the position changes.
- If you want a self-running, tempo-locked spatial effect. Circular Doppler's song-position sync gives you reproducibility that a manually automated device won't.
- If you need pitch movement. Distance and panning are what this device interpolates. The separate doppler variant exists for a reason.
- If your project is commercial and involves redistributing a modified patch. The NonCommercial-ShareAlike license constrains that.
- If you already run the original ml.Distance and never hear clicks. Some workflows never hit the problem alkman solved. If yours doesn't, the upgrade is cosmetic.
First session to try
Load it on a mono synth line. Set distance to 0, move panning only, and confirm you hear the lateral movement — that is the 1.1 fix in action, and it tells you the device is behaving. Then leave the pan static and automate distance alone across eight bars, once with smooth at its shortest useful setting and once long. The difference between those two passes is the argument for installing this version rather than the original.
From there, the device stops being an effect and becomes a placement decision you make per part. If you're stocking a performance rack more broadly, the current audio effect roundup covers what else deserves a slot.