Open Setup → Monitoring while the trigger is hit live: compare the exact message (type, channel, data) shown there against what you configured as the trigger, including channel and wildcard settings.
Automatic responses fire as soon as their part activates, optionally after a delay, optionally ramping to an end value over time. Manual responses wait for their own separate MIDI hit before firing — useful for an ad-lib cue that shouldn't happen every time the part plays.
Yes — Setup → Info → Diagnostics → "Send Log" shares the on-device log through the share sheet, e.g. to email it for support.
Yes. Export a whole Song Book, individual songs, or your custom hardware profiles from the "…" menu as a file, then AirDrop or email it — the recipient taps the file and it imports straight into their copy of MIDIPerformer.
No. Profiles are a shortcut — they let you pick named controls ("Kick", "Fader 1") instead of raw MIDI numbers, and enable smarter MIDI Learn. Every trigger and response can also be built entirely by hand (message type, channel, data bytes).
No. The Info screen (Setup → Info) confirms nothing is collected, nothing is transmitted, everything is stored on-device only, and there are no third-party components.
Set a response's Duration above zero, then choose a start value, end value, and curve (Linear or S-Curve). MIDIPerformer steps the output value across that time span instead of jumping instantly — handy for slow fades.
Turn on "Learn triggers from MIDI in" once, in Setup → App. After that, while any trigger field is open for editing, hit the real pad or move the real control on your gear — the message is captured and the fields fill themselves in, including automatic wildcards when the hit matches a known hardware profile control.
Tap the title at the top of the Performance screen, pick your song book and playlist (or a single song), tap Done. Three taps.
Swipe up or down on the Now/Next panel to manually step the part forward or back, or use the chevron buttons to jump between songs. No need to stop the show.
No. Unlock editing in Setup → Connectivity and tap Reassign. It bulk-remaps every trigger and response from the old remote (optionally filtered by channel and message type) to the new one, across all song books or just the ones you pick. This is permanent once applied, so double-check before confirming.
For USB gear, tap "Refresh MIDI devices" in the Scan & Advertise sheet. For Bluetooth, make sure the device is in pairing/discoverable mode and use the Bluetooth central browser in that same sheet. Once added, check that Listen is turned on for it in the device's detail screen.
Turn on "Advertise to remote centrals" in the Scan & Advertise sheet and set a recognizable device name — the console can then discover MIDIPerformer as a Bluetooth MIDI peripheral and connect to it directly.
Green = connected, orange = known but currently disconnected, gray = offline.
It marks that field as a wildcard — "any channel," "any velocity," etc. — so a trigger still fires even if that particular value varies hit to hit.
It toggles editing mode. Lock it before a show so nothing can be changed by accident mid-performance; unlock it whenever you want to edit songs, triggers, or settings.
A freeform spoken-word item — stage talk between songs. It works just like a song (title, color, optional trigger, parts) but has no author or tempo, and can be dropped into a playlist alongside your songs.
A Song Book is your whole library for a show or repertoire — all songs, banters, and playlists. A Playlist is one ordered set list built from the songs and banters in that book.
Live Performance mode, the playlist/set-list manager, MIDI response scheduling (delays and ramps), unlimited songs and parts, the full hardware profile library, and multi-remote support. Monthly and annual plans are available, and past purchases can be recovered with "Restore Purchases."
The last MIDI message MIDIPerformer actually received — a live sanity check that your gear is still talking to the app.
The song-level trigger (or banter-level) jumps straight to that item from anywhere — e.g. a dedicated program change per tune from a footswitch. A part's trigger only matters while that song is active, and advances it to the next part.
Setup → Monitoring shows a live log of the last 20 incoming messages, and includes a panel to manually send test messages to any destination — useful for confirming your console reacts the way you expect, before the show.
Live Performance is part of MIDIPerformer Pro. Setup and Song Book are fully usable on the free tier for building your show; Pro unlocks actually running it live, along with the playlist manager, MIDI response scheduling (delays/ramps), the full hardware profile library, and multi-remote support.