Free tool
MIDI Show Control Message Builder
Build a MIDI Show Control message: choose the device ID, the command format and a command such as GO, STOP or LOAD, add a cue number, and read the system exclusive bytes with every field explained.
Runs entirely in your browser; nothing is sent or uploaded. The URL updates as you work, so a message can be shared as a link.
Message
Choose who the message is for, what kind of equipment it is for, and the command.
127 addresses every device.
Leave empty for the current cue
Needs a cue number
Needs a cue list
Encoded message
- Length
- 13 bytes
- Command
- GO (01)
Hex
F0 7F 01 02 01 01 31 32 2E 35 00 31 F7
Byte by byte
| Field | Bytes | Meaning |
|---|---|---|
| Start of SysEx | F0 | F0 |
| Universal real time | 7F | 7F |
| Device ID | 01 | Individual device 1 |
| MIDI Show Control | 02 | Sub-ID 02 |
| Command format | 01 | Lighting (General) |
| Command | 01 | GO |
| Cue number | 31 32 2E 35 | "12.5" as ASCII |
| Delimiter | 00 | Ends the cue number |
| Cue list | 31 | "1" as ASCII |
| End of SysEx | F7 | F7 |
CueSync sends MIDI Show Control GO, STOP and RESUME with a cue number as standard SysEx. With a free account you can run the demo show and tour the app in read-only mode. Download for Mac, free account.
The commands this builder writes
Each command has a number, and the data that follows it depends on the command.
| Number | Command | Data |
|---|---|---|
| 01 | GO | Cue number, optional cue list, optional cue path |
| 02 | STOP | Cue number, optional cue list, optional cue path |
| 03 | RESUME | Cue number, optional cue list, optional cue path |
| 05 | LOAD | Cue number, optional cue list, optional cue path |
| 07 | FIRE | One macro number, 0 to 127 |
| 08 | ALL_OFF | None |
| 0A | RESET | None |
| 0B | GO_OFF | Cue number, optional cue list, optional cue path |
MIDI Show Control questions, answered
- What does a MIDI Show Control message look like?
- It is a system exclusive message: F0, 7F for universal real time, a device ID, 02 for MIDI Show Control, a command format, a command, any data, and F7 to finish. GO cue 12.5 in list 1 for device 1, Lighting General, is F0 7F 01 02 01 01 31 32 2E 35 00 31 F7.
- What is the device ID?
- The address of the receiving device. 00 to 6F are individual devices, 70 to 7E are optional groups, and 7F is all-call, which every device of the matching command format answers. A device only responds when both its device ID and the command format match.
- What is the command format?
- The kind of equipment the message is for. 01 is general lighting, 10 general sound, 30 general video, and 7F addresses every type. The format decides which devices act on the message, so a lighting console and a sound system on the same device ID can be told apart.
- How is the cue number written?
- As ASCII text. The digits 0 to 9 are bytes 30 to 39 and the decimal point is 2E, so cue 12.5 is 31 32 2E 35. The cue list follows after a 00 byte, and the cue path after another. A list needs a cue number before it, and a path needs a list.
- Why are TIMED_GO, SET and RESTORE missing?
- Their data layouts (a time, a control number and value) are not covered by this builder, and a wrong byte there would be worse than none. The builder covers GO, STOP, RESUME, LOAD, GO_OFF, FIRE, ALL_OFF and RESET.
- Does this send the message?
- No. It builds the bytes. Send them with whatever MIDI interface or software you use, or compare them with what a device transmits when you are checking a connection.