ETC Eos · OSC Message Generator

Build OSC for Eos-family consoles (Eos, Gio, Ion, Element, ETCnomad) — copy the string into Companion, QLab, TouchOSC or any OSC sender.

Command line

Sent as a string to /eos/cmd (or /eos/newcmd). In Eos OSC, # means Enter — without it the command line is set but not run.

Key press

Address /eos/key/<name>. Press sends no argument (full down+up); Down/Up send the edge as a float.

Fire a cue

Address /eos/cue/<list>/<number>/fire — fires the cue directly.

Submaster
1.00

Address /eos/sub/<n> for level (float 0.0–1.0), or /eos/sub/<n>/fire to bump.

Fader (OSC fader bank)
1.00

Address /eos/fader/<bank>/<fader>, float 0.0–1.0. The bank must be created first on the console with /eos/fader/<bank>/config/<count>.

Raw / custom message

Full manual control. The /eos prefix (and User, if set) is still prepended.

Heads up — browsers can't send OSC directly. OSC travels over the network, which web pages can't open. This tool builds the exact message; paste it into a real OSC sender (Bitfocus Companion, QLab, TouchOSC, Open Stage Control — or our own SchwiftyEx) pointed at your Eos console's IP and OSC RX port.
Generated message
Address
Argument

Manual & examples

New to OSC? Do the three steps once, then copy any ready-made example straight into your OSC app. Every message below already uses your prefix and User from the top bar.

STEP 1

Turn on OSC in Eos

On the console: Setup → System Settings → Show Control → OSC. Enable OSC RX and note the OSC RX Port (and choose UDP/TCP to match your sender).

STEP 2

Build a message above

Pick a tab (Command, Key, Cue…), set the fields, and the panel on the right shows the finished message live.

STEP 3

Copy it into an OSC sender

Paste into Companion, QLab, TouchOSC or Open Stage Control, aimed at the console's IP and the OSC RX port from Step 1.

Numbers are examples — channel 1, cue 1/5, sub 1. Swap in your own. All Eos OSC begins with /eos; the command line runs exactly what you'd type, and # is Enter.