Tantrum Audio

Appendix E — OSC address reference

Covers Omnissiah v0.1.6e

All chapters

Direct parameter-level addresses, for anything that talks OSC and doesn't need a macro: QLab, Max, REAPER, a lighting/show-control desk, or a hand-built TouchOSC layout. Every address needs the /omnissiah root: an address that doesn't start with it is ignored. Send no argument to a boolean address to have Omnissiah echo its current state back to you rather than changing it. Add /toggle to a boolean address to flip it regardless of the value sent. Omnissiah answers every address only whilst OSC listening is On on the Macros page (see Chapter 18 — Control macros). A calibration run or a measurement refuses control addresses while it is running, and no state is echoed during it. Omnissiah also broadcasts state changes to recently-seen peers as they happen, not just in reply to your own messages, but only for mute, polarity and xover-bypass. gain, master-volume and matrix deliberately don't broadcast: there's no safe way to read a continuously changing value back without it racing a macro or the app's own UI writing the same control.

Outputs

/omnissiah/out/<serial>/<n>/<control>

ControlArgumentNotes
mute0 / 1boolean
gaindB, −60 … +12absolute level; a value outside the range is held to it
delayms, −10 … +10relative step, not an absolute time
polarity0 / 1boolean
xover-bypass0 / 1boolean; only on outputs with a crossover

Add /fader to gain and send a position from 0.0 to 1.0 instead of dB, e.g. /omnissiah/out/ABC123/1/gain/fader. The position runs along the same console curve as a macro fader, so unity sits three quarters of the way up. /fader is only accepted on gain. /toggle is only accepted on the boolean controls.

<serial> is the device's serial number, or loopback for the loopback processor. <n> is the output number, counting from 1 in the device's own output order. Add /toggle to any boolean control above to flip it, e.g. /omnissiah/out/ABC123/1/mute/toggle.

Devices

AddressArgumentNotes
/omnissiah/dev/<serial>/master-volumedB, −60 … +12absolute
/omnissiah/dev/<serial>/master-volume/fader0.0 – 1.0position along the console curve
/omnissiah/dev/<serial>/matrix/<row>/<input>0 – 2matrix cell gain
/omnissiah/dev/<serial>/identifynoneflashes/identifies the device

In a matrix address, <row> is the matrix row as the device names it (for example out_1) and <input> is the input's label in lowercase, with any run of other characters turned into a single -, cut to 32 characters. A row or input the device doesn't have is ignored.

App-wide

AddressArgumentNotes
/omnissiah/app/rc-bypass0 / 1boolean; bypasses room correction
/omnissiah/app/loopback-bypass0 / 1boolean
/omnissiah/app/test-noise0 / 1boolean

There is no address for Apply Correction, or for any other recipe. To apply a correction from OSC, put an Apply Correction step in a macro and send that macro's own address (see below).

Subscribing to echo

AddressArgumentNotes
/omnissiah/subscribeport, 1–65535echo broadcasts for this sender go to this port instead

By default, echo goes back to whatever port your last message came from. Send /omnissiah/subscribe <port> once to redirect it, if your OSC client listens on a fixed port that's different from the one it sends on.

Macros

A macro has no fixed address. You give it one when you add an OSC trigger, and the app suggests /omnissiah/macro/<name> to start with. Whatever you choose, these three work:

AddressArgumentMeaning
the address itselfnone, or 1, or 0press, press, release
+ /fader0.0 – 1.0where a fader sits on its travel
+ /valuethe parameter's own unitsset it to exactly this

So a macro bound to /omnissiah/macro/monitors also answers to /omnissiah/macro/monitors/fader and /omnissiah/macro/monitors/value.

The rules an address has to keep:

  • It starts /omnissiah/.
  • Each part after that is 1–32 characters of lowercase letters, digits, _ or -.
  • Its first part can't be out, dev, app or subscribe, which are the canonical addresses above.
  • It can't end in /fader or /value, because those are the two suffixes in the table.

See Chapter 18 — Control macros.

Note

Output numbering follows the device's own output order. If a firmware update ever reorders a device's outputs, the addresses at each number move with them: a saved TouchOSC layout or Companion page built against /omnissiah/out/<serial>/1/... would then be driving a different output than before.

This manual is licensed to owners of Omnissiah for using the product. It may not be used to build competing software.

Tantrum Audio logo in footer
Tantrum Audio Instagram Share Widget
Tantrum Audio Facebook Share Widget

© Tantrum Audio 2026

Content on this site may not be used to build competing software.