SetPilot vs MIDI

• Swipe to advance the setlist – everyone stays in sync • Import from Google Drive – easily load your lyrics and sheet music • Prepare your next gigs – manage venues, dates, and participants • Build setlists with ease – drag & drop to create and edit • Personalize your display – each musician sees their own sheet music, lyrics, or chord progressions • Autoscroll – hands-free during performances • Metronome – start every song at the right tempo (not just for drummers!) Download SetPilot today and kick the papers and duct tape off the stage! Terms of Use (EULA): https://www.apple.com/legal/internet-services/itunes/dev/stdeula/

MIDIProbe is a pocket MIDI utility for iPhone and iPad that helps you discover, test, and troubleshoot MIDI devices (e.g., controllers, synths, mixers). Pick which endpoints to send to or listen to, fire off the exact MIDI commands you need, and watch a live, timestamped log to verify every message. • Discover USB, Bluetooth, and RTP network MIDI devices, and see detailed info like IDs, serial numbers, and transport type before selecting send/receive targets. - Send MIDI fast with interactive cards: - Notes, Control Change (CC), Program Change, Aftertouch, Pitch Bend; - System Common (Song Position Pointer, Song Select, Tune Request); - Real-Time (Start/Stop/Continue, Clock, Active Sensing, Reset); • Monitor inbound MIDI with a live log or grouped-by-command view, with filters for command types, clear controls, and timestamps. Typical use cases: • Reverse-engineer mixer control quickly:  You have an X32 mixer and want to use a floorboard to mute/unmute channels. Connect both to MIDIProbe, discover the right endpoints, and watch which channel/CC/value combinations actually toggle mutes—then verify your floorboard sends the exact same messages before you risk it live. • Map a foot controller to a multi-FX unit:  You want to configure a floorboard to switch presets/settings on your multi-effects processor. Use MIDIProbe to identify which Program Changes or CCs trigger the functions you need, then confirm the outgoing messages match your intended mapping. • Confirm keyboard controller channel routing:  Check whether your keyboard is transmitting on the correct MIDI channel (or accidentally sending Omni), and verify splits/layers are hitting the channels your synth or app expects. • Validate DAW controller templates:  Debug pad controller mappings for Ableton/Logic/Cubase—see exactly which notes/CCs each pad/knob/fader is sending, catch duplicated CC numbers, and confirm bank switching. • Troubleshoot “why doesn’t it respond?” fast:  If your synth/module isn’t reacting, use MIDIProbe to confirm whether it’s receiving anything at all, whether the messages are on the wrong channel, or whether you’re sending the wrong command type. • Verify pitch bend and high-resolution CCs:  Check pitch bend ranges and whether devices send 14-bit (MSB/LSB) pairs correctly for smooth parameter changes. • Build and test custom hardware/software:  If you’re developing MIDI controller firmware or a MIDI iOS/macOS app, use MIDIProbe as your “known good” sender/receiver to test parsing, edge cases, and message timing. If you’re into this kind of thing, MIDIProbe is for you.