yeh well there will definitely be no drifting if it is not receiving midi clock, because that means the clock would be generated internally by the device itself
also depending on your setup you may not need it - but if you want to hit “play” on your computer and then have the sequencer of another device start running at the same time, you have to do it (there are other more complicated ways of getting that done without sending clock but you may not be up to it)
if you dont need this to happen, just have each device use their own midi clock (dont sync them) and just set them all to the same tempo
I think the suggested solution given by elektron is to use the Octatrack as a midi clock master, and then have Ableton sync to that… but its still gonna drift, its just the nature of the beast
for some reason, no one ever implements a setting like “clock drift tolerance”… so it will drift by like a few 0.1s of a BPM all over the place, but usually not more than that… so if you are syncing to 120 bpms, you will see the slave drifting from 120.1 to 120.4 or down to 119.8 or something like this… and i dont know why there is not a setting for “tolerance” so that if the clock drifts less than a full 1.0 BPM, it would be ignored - seems like that would solve a lot of problems but apparently nobody has thought of that