Automated summary
Provides an Ableton Live Object Model (LOM) Python API reference for building Remote Scripts and control surfaces.
Strengths
- Domain-specific reference files for song, tracks, clips, devices, browser, views, and more.
- Explains object hierarchy, property access modes, main-thread scheduling, and canonical paths.
- Includes a coverage checklist mapping official LOM objects to reference files.
Limitations
- Documentation-only skill; it does not execute code or test scripts inside Ableton Live.
- Assumes an existing Ableton Live Remote Scripts setup.
- Details may vary by Live version.
Use when writing or debugging Ableton Live Python Remote Scripts or control surface integrations.
Avoid for general Python work or Max for Live patching that does not involve the LOM.
Security analysis
SafeThe skill is a documentation reference for Ableton Live's Python Remote Scripts API. It contains benign code examples for reading and modifying Live Set state, with no instructions to execute untrusted code, delete files, exfiltrate data, disable safety mechanisms, or perform obfuscated actions.
No concerns found
How this analysis is madeExamples
Using the Ableton LOM, write a Python Remote Script ControlSurface that sets the Live Set tempo to 120 BPM and starts playback when the script initializes.Show me how to add a tempo listener in an Ableton Remote Script so a control surface LED updates whenever the song tempo changes.How do I access and set the first parameter of the first device on track 2 using canonical LOM paths in a Remote Script?name: ableton-lom description: Ableton Live Object Model (LOM) API reference for Python Remote Scripts and control surface development.
Ableton Live Object Model (LOM) API Reference
This skill provides comprehensive documentation for the Ableton Live Python API used in Remote Scripts. The API is accessed through the _Framework.ControlSurface base class and provides programmatic control over every aspect of a Live Set.
Quick Start
from _Framework.ControlSurface import ControlSurface
class MyScript(ControlSurface):
def __init__(self, c_instance):
ControlSurface.__init__(self, c_instance)
self._song = self.song() # Access the Live Set (Song object)
app = self.application() # Access the Application object
Core Objects Hierarchy
Application
├── browser (instruments, sounds, drums, audio_effects, midi_effects)
├── control_surfaces[] → ControlSurface
└── Song (live_set)
├── tempo, is_playing, loop, metronome
├── tracks[] → Track
│ ├── clip_slots[] → ClipSlot → Clip
│ ├── devices[] → Device → DeviceParameter
│ ├── mixer_device → MixerDevice
│ └── view → Track.View
├── return_tracks[] → Track
├── master_track → Track
├── scenes[] → Scene
├── cue_points[] → CuePoint
├── groove_pool → GroovePool → Groove
├── tuning_system → TuningSystem
└── view → Song.View
Reference Files by Domain
Load the appropriate reference file based on what you're working with:
| Domain | File | Use When | |--------|------|----------| | Song & Transport | references/song.md | Working with tempo, playback, time signatures, loops, cue points | | Tracks | references/track.md | Creating/modifying tracks, routing, arm/solo/mute, meters | | Clips & MIDI | references/clip.md | Creating clips, adding/editing MIDI notes, clip properties, warping | | Devices | references/device.md | Loading devices, accessing parameters, device chains | | Specialized Devices | references/specialized-devices.md | Simpler, Wavetable, Looper, Compressor, EQ8, Drift, etc. | | Rack Devices | references/rack.md | Instrument/Audio/MIDI/Drum Racks, chains, macros, drum pads | | Session View | references/session.md | Scenes, clip slots, launching, Session View navigation | | Views & UI | references/views.md | Application.View, Song.View, Track.View, Clip.View, Device.View | | Browser | references/browser.md | Browsing/loading instruments, effects, samples, presets | | Control Surfaces | references/control-surface.md | Accessing configured surfaces, grabbing controls/MIDI, SysEx | | Grooves & Tuning | references/grooves-tuning.md | Groove pool, tuning systems | | Coverage Checklist | references/lom-coverage.md | Official Cycling '74 LOM object-to-file audit map |
Key Concepts
Property Access Modes
- read-only: Can only get the value
- read-write: Can get and set the value
- observable: Can add listeners with
add_<property>_listener(callback)
Threading
All state modifications MUST happen on Ableton's main thread:
def modify_state():
self._song.tempo = 120.0
self.schedule_message(0, modify_state) # Schedule for main thread
Canonical Paths
Objects are accessed via paths like live_set tracks 0 devices 1 parameters 2. Use these to understand the object hierarchy.
Special root paths include live_set (current Song), live_app (Application), control_surfaces N (configured ControlSurface), and this_device (the Device containing the Max for Live live.path object that receives goto this_device).
Common Patterns
Iterate tracks and clips:
for track in self._song.tracks:
for slot in track.clip_slots:
if slot.has_clip:
clip = slot.clip
# Work with clip
Add a listener:
def on_tempo_changed():
self.log_message("Tempo: " + str(self._song.tempo))
self._song.add_tempo_listener(on_tempo_changed)
Access device parameters:
device = track.devices[0]
for param in device.parameters:
self.log_message(param.name + ": " + str(param.value))
Version Compatibility
This documentation covers Live 12.3. Key version notes:
- Live 11+: Python 3 required
- Live 11.0+: GroovePool, Groove classes added
- Live 12.3+:
insert_device(),insert_chain(), AB Compare features added
Important Notes
- The API is officially undocumented by Ableton - this reference is based on community documentation from Cycling '74's Max for Live LOM reference
- Always test Remote Scripts with a backup of your Live Set
- Some operations may cause crashes if called from wrong thread
- Observable properties can be used to build reactive UIs
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/ableton-live-object-model-lom-api-mryiqiws/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/ableton-live-object-model-lom-api-mryiqiws' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/ableton-live-object-model-lom-api-mryiqiws/download' --output '.skill-downloads/ableton-live-object-model-lom-api-mryiqiws/SKILL.md.part' && mv '.skill-downloads/ableton-live-object-model-lom-api-mryiqiws/SKILL.md.part' '.skill-downloads/ableton-live-object-model-lom-api-mryiqiws/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/ableton-live-object-model-lom-api-mryiqiws/SKILL.md' && test -s '.skill-downloads/ableton-live-object-model-lom-api-mryiqiws/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/ableton-lom' && cp -R '.skill-downloads/ableton-live-object-model-lom-api-mryiqiws' '.claude/skills/ableton-lom'Cursor
test -f '.skill-downloads/ableton-live-object-model-lom-api-mryiqiws/SKILL.md' && test -s '.skill-downloads/ableton-live-object-model-lom-api-mryiqiws/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/ableton-lom' && cp -R '.skill-downloads/ableton-live-object-model-lom-api-mryiqiws' '.cursor/skills/ableton-lom'Codex
test -f '.skill-downloads/ableton-live-object-model-lom-api-mryiqiws/SKILL.md' && test -s '.skill-downloads/ableton-live-object-model-lom-api-mryiqiws/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/ableton-lom' && cp -R '.skill-downloads/ableton-live-object-model-lom-api-mryiqiws' '.agents/skills/ableton-lom'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/ableton-live-object-model-lom-api-mryiqiws'openskills read 'ableton-live-object-model-lom-api-mryiqiws'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/ableton-live-object-model-lom-api-mryiqiws/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.