Gravity Feed for Ableton Live
Connect Ableton Live through a Max for Live device: read tempo, locators and tracks, write encoder automation.
This guide explains how Ableton Live can work with Spatial9 Gravity Feed. Status: documented route. Live can be controlled from outside through a MIDI Remote Script or a Max for Live device, and it hosts VST3 encoders such as IEM StereoEncoder. Spatial9 has not built or tested a Live adapter.
At a glance
| Item | Detail |
|---|---|
| Status | Documented route, no Spatial9 adapter yet |
| Adapter type | Max for Live device or companion process, sending OSC to the encoder or driving mapped parameters |
| Reads | Tempo, locators and track names, available to Max for Live through the Live Object Model |
| Writes | Encoder parameters, recorded into Arrangement automation |
| Spatial plugin | IEM StereoEncoder (VST2 or VST3) |
Route
- Load IEM StereoEncoder on each spatial track and open its OSC port, one port per instance.
- A Max for Live device reads the tempo, the locators and the track names, and sends the Gravity Feed request with your key.
- Arm automation recording in Arrangement view and play the range. The device sends each planned value at its beat time, either as OSC to the encoder or as a change to the mapped encoder parameter, and Live records it.
Mapping the request
| Gravity Feed field | Live source |
|---|---|
session.tempo_map | Song tempo |
session.sections | Arrangement locators |
tracks[].role | Track names |
tracks[].position | Encoder parameter values |
FAQ
Do I need Max for Live?
It is the easiest way to read the session from inside Live. Without it, enter the tempo and sections in a companion process and send OSC to the encoder.
Does Live support immersive output?
Live works with multichannel plugins, but its own output is stereo or a small number of channels. Ambisonic encoders with a binaural decoder are the usual headphone route.