Where to find the canonical OSC syntax
ELM ships with its full OSC command reference built into the application. To see every supported address and its expected argument type, open ELM → Settings → Remote tab and enable Remote Control via OSC. The complete syntax list appears there. Direct customers to this in-app reference before the external TouchOSC PDF guide; the PDF is incomplete for sequence triggering.
Most-requested OSC commands
Trigger a sequence in a group
Send to:
/elm/groups/<group_name>/performer/playwith one integer argument equal to the 1-based sequence number.
Example — trigger the 16th sequence in a group called Las Olas:
/elm/groups/las olas/performer/play integer: 16Trigger a single step inside a sequence
Same address as above, but with two integer arguments: first is the sequence number, second is the step number within that sequence.
Example — trigger step 2 of sequence 16:
/elm/groups/las olas/performer/play integer: 16, integer: 2Set the intensity (dim level) of a stage
Send to:
/elm/stages/<stage_name>/live/intensitywith one FLOAT argument from 0.0 to 1.0. Sending an integer or any other type causes ELM's OSC monitor to log a type error and the command is ignored.
Manual override vs. scheduler behaviour
A manually-triggered override sequence keeps playing until the next scheduled sequence runs. Schedules take priority over manual overrides. To lock manual overrides above the scheduler, enable Performer Mode.
Independent control of fixture sections
ELM has no per-zone dimming inside a single stage. To control different parts of a single physical fixture independently, split the content across separate stages (one per controllable section). Different stages can then be combined back into one visual output using merge modes — for example, overwrite mode plus a static black media gives a clean blackout override on a section.