Device Details

Device Overview

Name/Version: ml.Distance 1.2
Author: alkman  
Description: Alternative graphical interface for Robert Henke's ml.Distance but with a twist. Distance and panning values are interpolated, for avoiding clicks in the sound. The added smooth parameter controls the interpolation time.

*update* 1.2 (1-3-2020) GUI elements are not rendered blurry on non-retina screens

*update* 1.1 (9-4-2019) Panning works also when distance=0

original device here:

review video here:


Device Details

Downloads: 28900
Tags effect, utility
Live Version Used: 10.0.5
Max Version Used: 8.0.3
Date Added: Jan 26 2019 11:58:24
Date Last Updated: May 27 2021 09:42:46
Average Rating (20) 5
Rate this device: (must be logged in to rate devices login)
Device Type: midi_device
URL (optional):
License (more info): AttributionNonCommercialShareAlike

Device Files

Device File: ml.distance.amxd



Nice but the panning doesnt seems to work

coool thing

It is absolutely amazing! Thank's for your work! Maybe, it will be great if it'll have also gain knob to replace utility from tracks.


Binaural systeme. Bravo alkman ?

This is abolutely wonderful!
I spent too many times, automating the highshelf, the reverb and such. But the dampening, and the fact that there so many controls on one device, is really game changing! Props to you man!

The amount of control this device gives is crazy, really well done and build. Awesome work!

seems to be borken now :(

This is my absolute favorite M4L device of all time. It has become a huge part of my sound, I've used it on pretty much every track in every project I've made. Recently I upgraded to Live 11, and this device has stopped working properly. Are there any plans to update it to work with Live 11?

Well done feller. This is really well done and superbly thought out.

It does work with Live 11. Having that said, the first time I opened it on Live 11 it was not working, but when I clicked the edit with Max button it started working fine. I think I had changed audio device output and/or sample rate after loading it, and that confused it somehow (?). But actually I'm not sure, because since then I have not been able to reproduce the bug :/

Login to comment on this device.

[ browse device library ]