MIDI

How RigWork sends MIDI - and how to get other devices to trigger RigWork.

Web MIDI

RigWork uses the Web MIDI API built into Chrome and Edge. There's no driver to install, no bridge app, no virtual cable - if your MIDI interface shows up in your OS, RigWork can see it.

Connecting

Click the MIDI button in the sidebar. Your browser will prompt for MIDI access permission - click Allow. Once granted, RigWork connects to every MIDI output and input it can find and shows a count in the sidebar.

Browser compatibility

Browser	Web MIDI
Chrome / Chromium	Native support - recommended
Edge	Native support
Firefox	Not supported natively - requires WebMIDI extension
Safari (macOS/iOS)	Not supported natively - requires Jazz-Plugin or similar

For live use, Chrome on a Windows or macOS laptop is the most reliable setup. Chrome on Android also works if your interface has a USB-C adapter.

MIDI Output

When you fire a preset, RigWork sends to all connected MIDI outputs. If you have multiple interfaces connected, all of them receive the messages. If you only want a subset, disconnect the ones you don't need (unplug them) before connecting in RigWork.

What gets sent

For each device in the preset that has CC values captured: all CC messages on that device's channel, in CC number order
For each device in the preset that has a PC number assigned: one Program Change message on that device's channel

MIDI Input - PC Trigger

RigWork can listen on its MIDI inputs and auto-fire a preset when it receives a Program Change message. This is how you integrate RigWork with Ableton, a DAW, or a MIDI controller:

Your timeline / controller sends a single PC message on a configured channel
RigWork receives it, looks up which preset has that PC number assigned
RigWork fires the preset - CCs + PCs go out to all your pedals

This means your DAW only needs to send one MIDI event per section. RigWork handles the fan-out to all the individual pedals.

Trigger Channel

Use the trigger ch selector in the sidebar to choose which incoming MIDI channel RigWork listens on for PC triggers. Options:

Any - responds to PC on any channel
Ch 1–16 - only responds to PC on the selected channel

Set this to a dedicated channel (e.g. Ch 16) so RigWork doesn't accidentally fire from MIDI messages intended for other devices.

MIDI IN indicator

The MIDI IN dot in the sidebar flashes green each time RigWork receives a PC message on the trigger channel. Use this to confirm the signal is arriving before you're on stage.

Typical Signal Chains

Ableton → RigWork → pedals

Ableton timeline has one MIDI clip per song section. Each clip sends PC [n] on Ch 16. RigWork receives it and fires the mapped preset - distributing CCs and PCs to all 8 pedals simultaneously.

Ableton never needs to know about individual pedal CC maps. One event, full rig state.

MIDI pedalboard → RigWork → pedals

A MIDI foot controller (e.g. RJM Mini Effect Gizmo, Disaster Area DMC) sends PC to RigWork. RigWork fires the preset. Your feet control RigWork, RigWork controls the board.

Standalone

No external MIDI trigger. You tap sections manually in Show Mode on a tablet. RigWork fires the preset over USB to your MIDI interface and out to the pedals.

MIDI Interface Notes

RigWork works with any class-compliant USB MIDI interface. Common options used with setups like this:

iConnectMIDI4+ - connects iPad + desktop simultaneously, 4 DIN ports
MOTU micro / express - low-latency, USB, multiple DIN ports
Roland UM-ONE - smallest/cheapest, one DIN in + out
Any USB-C audio interface with MIDI DIN - RME, Focusrite, etc.

← Back to Manual · Next: Rig Rundown →