A Clip Slot is the container; firing it via OSC triggers play/pause regardless of whether a clip exists

In Live’s Object Model, a Clip Slot is the cell at the intersection of a track (column) and scene (row). It may be empty or contain a Clip. AbletonOSC exposes /live/clip_slot/fire <track_index> <clip_index>, which fires the clip slot’s play/pause behaviour — equivalent to clicking the clip slot cell in Live. If a clip is present, it starts/stops. If the slot is empty but has a stop button, firing stops the track. This is a more session-oriented command than /live/clip/fire (which requires a clip to exist and addresses it directly). The Clip Slot API also provides /live/clip_slot/create_clip (creates an empty MIDI clip in the slot), /live/clip_slot/delete_clip, /live/clip_slot/get/has_clip, and /live/clip_slot/duplicate_clip_to.

Examples

Fire clip slot (0,0): /live/clip_slot/fire 0 0. Check if a clip exists: /live/clip_slot/get/has_clip 0 0 → (0, 0, 1). Create a 4-beat MIDI clip: /live/clip_slot/create_clip 0 0 4.

Assessment

What is the difference between /live/clip_slot/fire and /live/clip/fire? When would firing an empty clip slot be useful?