home/ atoms/ live-object-model-hierarchy

The Live Object Model organises Live's entire state as a tree: Song > Tracks > Clips/Devices > Parameters

The Live Object Model (LOM) is Ableton’s Python API that exposes every controllable element of a Live session as a tree of objects. At the root is Song — containing global state (tempo, record mode, metronome), tracks, scenes, and cue points. Each Track contains clip slots (indexed by scene row), devices, and mixer parameters. Each Clip Slot optionally contains a Clip; each Device contains Parameters. AbletonOSC mirrors this tree in its OSC address namespace: /live/song/…, /live/track/…, /live/clip/…, /live/device/… Indices into the tree are always zero-based. Understanding the LOM hierarchy is prerequisite to constructing any AbletonOSC command, because every address includes the object path and zero-based indices as arguments.

Examples

To get the volume of the first track: /live/track/get/volume 0 → returns (0, volume_value). To get the name of the clip in track 1, scene 2: /live/clip/get/name 1 2. To set a device parameter: /live/device/set/parameter/value 0 0 5 0.75 — track 0, device 0, parameter 5, value 0.75.

Assessment

Given the OSC address /live/device/get/parameter/value, identify what the three integer arguments refer to. Draw a two-level diagram showing which LOM objects are children of Track.

“The project's aim is to expose the entire [Live Object Model](https://docs.cycling74.com/max8/vignettes/live_object_model) API ([full API docs](https://structure-void.com/PythonLiveAPI_documentation/Live11.0.xml)),”
corpus · abletonosc-osc-control-interface-for-ableton-live-live-objec · chunk 3