Renardo's Ableton backend can automate parameters with TimeVar at up to 300Hz via AbletonOSC

The Ableton Live backend in Renardo connects via AbletonOSC and supports parameter automation that updates at up to 300Hz, far beyond MIDI CC resolution. Any player attribute that maps to a Live device parameter can be driven by a var or linvar: p1 >> synth.out(filter_cutoff=var([20, 127], 8)) varies the filter cutoff in Live every 8 beats. This is achieved via OSC control rather than MIDI automation, enabling live continuous parameter modulation from Renardo code. Additionally, MIDI note output and clip triggering (trigger a scene or specific clip slot) coexist in the same backend.

Examples

# Automate Ableton filter with linvar:
p1 >> synth.out(degree=0, filter_cutoff=linvar([20, 127], 8))
# Trigger clips:
p3 >> bass.out(clip=P[0, 1, 2], dur=4)

Assessment

Why does the Ableton backend use OSC rather than MIDI CC for parameter automation? What is the practical benefit of 300Hz update rate vs. MIDI’s ~31 Hz CC rate?