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>
| Control | Argument | Notes |
|---|---|---|
| mute | 0 / 1 | boolean |
| gain | dB, −60 … +12 | absolute level; a value outside the range is held to it |
| delay | ms, −10 … +10 | relative step, not an absolute time |
| polarity | 0 / 1 | boolean |
| xover-bypass | 0 / 1 | boolean; 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
| Address | Argument | Notes |
|---|---|---|
| /omnissiah/dev/<serial>/master-volume | dB, −60 … +12 | absolute |
| /omnissiah/dev/<serial>/master-volume/fader | 0.0 – 1.0 | position along the console curve |
| /omnissiah/dev/<serial>/matrix/<row>/<input> | 0 – 2 | matrix cell gain |
| /omnissiah/dev/<serial>/identify | none | flashes/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
| Address | Argument | Notes |
|---|---|---|
| /omnissiah/app/rc-bypass | 0 / 1 | boolean; bypasses room correction |
| /omnissiah/app/loopback-bypass | 0 / 1 | boolean |
| /omnissiah/app/test-noise | 0 / 1 | boolean |
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
| Address | Argument | Notes |
|---|---|---|
| /omnissiah/subscribe | port, 1–65535 | echo 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:
| Address | Argument | Meaning |
|---|---|---|
| the address itself | none, or 1, or 0 | press, press, release |
| + /fader | 0.0 – 1.0 | where a fader sits on its travel |
| + /value | the parameter's own units | set 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.
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.