New Ableton M4L Device Cooking...MIDICLOCK w/o Latency!

So if I understand correctly, your clock will compensate for the track latency, I guess by sending out the clock pulses ahead of time so that the device “feels” in sync even though it is playing earlier than it should? That’s a clever way to approach it if so.

Does this also help with clock stability at all? I found that the clock from Ableton leads to a detectable amount of jitter e.g. on a drum machine with 1/16th hi hats (this is well documented around the internet and the blame is usually laid at modern operating systems/audio interfaces for not having a way to accurately schedule MIDI messages) - I’ve been using Overbridge to make my Digitakt the clock master instead as I described in another thread (Overbridge makes a great MIDI clock source) but would be interesting if you’ve solved/improved this somehow!

1 Like