Remote Control (OSC)

Drive Prismatik from a Stream Deck, a console macro, or anything that speaks OSC. Transport, markers and the mixer, on physical buttons.

What this is for

Two jobs, and they are different.

Running a show — Conductor. Play, next, mute the click, set a level, on a button you can hit without looking.

Marking cues — Timeliner. A foot switch or a Stream Deck key dropping a marker on a named layer, so your hand never leaves the desk while you listen.

Stream Deck

A Stream Deck talks to Prismatik through Bitfocus Companion, which speaks OSC. There is no separate Stream Deck setup — configure Companion and the keys follow.

1. In Prismatik, open Conductor or Timeliner and press Enable OSC. It listens on UDP 8000.
2. In Companion, add a generic OSC connection pointed at the machine running Prismatik, port 8000.
3. Give a button an OSC: Send message action, and paste one of the addresses below into it. Leave the arguments empty.

Both tools list every address in the app with click-to-copy, and show the last address received along with what it resolved to — so a button that does nothing tells you whether the message arrived at all.

How the addresses work

Every command is address-only, with no arguments. A button press sends a bare string. Anything that needs a value has its own address — /prismatik/mixer/volume/50 rather than a volume address carrying 0.5.

That is deliberate: it means every command is copy-pasteable with nothing to configure, which is the difference between setting up thirty buttons in five minutes and in an hour.

Matching ignores case and tolerates a trailing slash.

Volume takes any percentage

The table lists every 5%, to stay readable. Any whole number from 0 to 100 works, listed or not — /prismatik/mixer/volume/37 is valid.

Values outside 0–100 are refused rather than clamped. A controller sending 150 is misconfigured, and quietly treating that as full volume would hide it.

Marker layers are 0–9

Layer 0 is the global layer, and 1–9 are the first nine layers of the track — the same as Timeliner’s numpad bindings, so the keyboard and a Stream Deck mean the same thing.

An address for a layer that does not exist on the current track drops the marker on the global layer rather than doing nothing.

The addresses

Transport

Set

Marker

Mixer

Which tool answers what

Not every command applies everywhere. Both tools ignore what does not.

Each tool also lists only its own commands: Timeliner shows no track addresses, and Conductor shows no marker addresses. Conductor’s track list is as long as the loaded setlist, so /set/track/9 on a five-track set does not resolve.

Troubleshooting

A button does nothing

Check the Last received line in the tool. If nothing appears, the message is not arriving — check Companion’s target IP and that both machines are on the same subnet. If the address appears marked (unknown), it reached Prismatik but did not match — either a typo or a command that tool does not offer, since each tool only resolves its own list.

The address arrives but nothing happens

The command resolved but that tool does not act on it — see the table above. Volume up and down are the usual case: they are listed everywhere but only Conductor moves on them.

Port 8000 is already in use

Cuepoints uses the same default, so the two cannot listen at once on one machine.

Related

• Conductor — running a set
• Timeliner — marking cues

Source

src/renderer/src/utils/osc-commands.ts