Ableton Link Latency

[jamshark70]

@retroriff

I would like to sync and play an Ableton Live instrument with my SuperCollider SynthDefs.

You might not need LinkClock for this.

LinkClock is to sync the tempo between multiple sequencers. (And in fact, they can be any Link-capable sequencers – you can use Link without Live.)

So… are you using Live as a sequencer here? If you’re using Live as an instrument host only, then LinkClock is irrelevant. (Asking because it sounds, from the issue description, like you’re only loading the instrument in Live but all the control is in SC.)

@retroriff

However the rhythm is not matching because there’s some latency between the Pdefs. I see that Server.default.latency is 0.2 and I have set up the same latency to Ableton Link

There are three latencies involved here: SC server latency, MIDIOut latency, and LinkClock latency. LinkClock latency concerns beat sync, NOT audio or MIDI sync. If you’re not playing sequences in Live and SC together, then you don’t need beat sync. In that case, LinkClock latency won’t fix your problem.

I think MIDIOut latency is what you should be looking at. The behavior might depend on Mac or Windows – which one are you using?

@retroriff

(
MIDIClient.init;
m = MIDIOut.new(0);
l = LinkClock(130/60).latency_(Server.default.latency);

Pdef(\sc, Pbind(\type, \midi, \midicmd, \noteOn, \midiout, m, \chan, 0, \midinote, 36)).play(l).quant_(4);
Pdef(\live, Pbind(\instrument, \kick, \amp, 1, \dur, 1)).play(l).quant_(4);
)

If there is only one Link peer, this is ok, but – if you’re using Link as intended with multiple peers, you shouldn’t create the clock and play immediately. LinkClock needs a little time to find other peers on the network – its timebase may change shortly after creating it. As written, this isn’t a good habit to get into.

But I think in this case you’re not syncing to Live’s clock, so it probably doesn’t matter just now.

hjh