A Max for Live device bridges an external OSC control surface to Live via the LOM

To drive Ableton Live from a custom OSC surface, three layers connect: (1) an OSC controller app (here Open Stage Control, but the pattern fits TouchOSC, LK, or custom code), (2) a Max for Live device loaded on a Live track that translates incoming OSC into LOM commands and sends state back out as OSC, and (3) Live’s session state reached through the LOM. The device only works once the send/receive UDP ports set in Open Stage Control match those in the Max device — that port pairing establishes the bidirectional channel. The M4L device is the indispensable translation shim: neither the controller app nor Live can talk to the other without it.

Examples

Workflow: open the Live set, load the Max device on a track, run Open Stage Control, and set its send/receive ports to match the Max device; the OSC surface then controls the first clip. A maintained drop-in alternative to a hand-built device is the AbletonOSC remote script.

Assessment

Draw the three-layer flow (controller -> M4L device -> Live) for launching a clip, and identify which layer converts an OSC message into a LOM command.