Small messages.
Big moves.
Use external MIDI CC messages to request playback and navigation through a compatible connected controller.
Performance command table.
Send these on the song program’s listening channel, initially channel 16. Set Petal’s Incoming MIDI channel to suit your controller. These commands are implemented by Petal-compatible firmware; verify your device’s firmware support.
| Action | CC | Value |
|---|---|---|
| Play | 101 | 3 |
| Pause | 101 | 4 |
| Stop | 101 | 5 |
| Previous section | 101 | 6 |
| Next section | 101 | 7 |
| Go to song | 102 | Song position, 0–127 |
Song positions start at zero.
For CC 102, value 0 selects the first song in the performance, value 1 the second, and so on. This is a position in the running order, not a song’s name or library identifier.
To request the third song, send CC 102 with value 2 on the configured incoming channel. Open the intended performance first.
How a footswitch starts playback.
The controller sends a request back to the app, which performs navigation and playback. These CCs do not directly start playback without an app connection. Previous and next song are not assigned additional CC 101 values in the current implementation; use CC 102 to choose a song by position.
Control Change numbers and values are 7-bit MIDI data: 0–127. Device-specific preset controls are separate from this Petal performance command table.