MIDI clock (slave) improvements in Live 8.2.4b1

[pepezabala]

Anyone tried looper on a slaved Live? I had ugly artifacts and freakouts of the looper device on a slaved Live and stopped using sync mainly because of this. But if this works better now I will try again.

Yes, I tried it and it sucks. Not just in Live. I stay away from even step sequencers running inside a slave syncing host application. Effects I use though - that works like a charm - are LFOs to drive plugin parameters, beat depending delays and tremolo stuff etc.

Loopers in general need to spin freely, if you mash stuff up for a show, so syncing the host application is definitely the way to go. If you let Live's Looper be the master ("set tempo") I guess it will work better?

well in our case it's not that easy, as we use two computers on stage, and want to use loopers on both of them. Anyway, beatmatching two laptops without sync is not so hard once you got used to it. I did not experience them drifting, but mostly we end a song after maximum 10 minutes, that helps probably.

[alyessamoore]

your post is really nice..i like it

[stuartm]

The problem with Live starting as clock slave after loading a set has been fixed in 8.2.5b1:

When loading a Live Set while receiving MIDI clock in Live 8.2.4b3, Live would immediately start the playback of the Set.

[rpacker]

I just tried 8.2.5 and the MIDI clock sync is working beautifully, it is very, very stable. Bravo Ableton! Now just stabalize MIDI clock send and you'll have it nailed.

[LeifonMars]

I too tried Live being slave for my Octatrack and it was rock solid. Amazing difference from what it used to be. Well done Abes.

[QUAZAR]

YEAH!! I'm really, really happy that for the first time I could use Live as a slave to my Machinedrum. Thanks Ableton! Been waiting for this for a long long time..