Before you begin
- A real class-compliant USB MIDI controller/cable or compatible Bluetooth MIDI device for connection testing.
- Stage for MIDI learn, mod-wheel/quick-control mapping, Chords and Arpeggiator; Player for Transposer.
Connect a USB MIDI keyboard
- Tap Refresh MIDI Sources after connecting a keyboard.
- Use Capture to start or pause the MIDI event log.
Use a USB data cable and an adapter/hub supported by your Android device. Some controllers need external power or a powered hub. Connect the controller, grant any Android permission prompt, then open Midi Settings and refresh sources.
Tap Settings, then Midi Settings in the category list, scrolling if needed. Use the back arrow to return to the list.
The source list should show the controller connected. Turn on Capture and play a note or move a controller to inspect incoming messages. A powered LED on the keyboard does not prove the cable carries MIDI data.
- Connect and power the real controller using a data-capable cable.
- Open Midi Settings and choose Refresh MIDI Sources.
- Enable Capture, play a note, and check the note event before trying to learn a control.
- In channel Attributes > Input, choose Any device or include the connected source.
Bluetooth MIDI and Android settings
- Tap Pair new device to start Android pairing; MIDI support depends on the controller and companion app.
Enable Bluetooth and put the MIDI device into its discoverable/connection mode according to its own manual. Android connection and permission prompts vary by OS/device. The current app has no dedicated Bluetooth MIDI scanning/pairing screen: it opens MIDI devices exposed by Android’s MIDI service. Return to InPraise Keys and check Refresh MIDI Sources; a device must appear there and send events. Pairing status in Android alone is not proof that MIDI is available to the app.
Bluetooth MIDI and Bluetooth audio are separate. A wireless MIDI controller can drive the app while audio uses a wired output. Avoid assuming wireless headphones will have acceptable live-playing latency.
Learn a control
- Tap a gray control, then move the MIDI control you want to assign.
Start MIDI Learn from the relevant control/menu or from Midi Settings. Select the intended target, move one hardware knob/fader/button, and finish or cancel the learning session. Test the mapping at a safe volume before using it onstage.
For note-range boundaries use Input > Learn Key. For CC1 expression, use the mod-wheel mapping controls. Check Ignore Mod Wheel/Sustain/Pitch Bend on channels that should not respond.
- Verify incoming messages with Capture first.
- Begin learning the intended control and move a single hardware control.
- Exit Learn and test the mapped target through its full useful range.
- Save the rig and recall it to verify the intended setup.
MIDI Transposer — Player
- Use +12 for a one-octave increase.
Add Transposer in FX > MIDI FX. It shifts MIDI notes before the instrument renders them. Its octave/semitone controls define the shift; bypass returns the original note input. This differs from the audio Pitch Shifter, which processes an already rendered signal.
MIDI Chords — Stage
- Tap + Chord to add a chord, or + Chord Family to add a group.
Add Chords in MIDI FX. Create an input-note assignment and edit its output notes. The keyboard view shows Input and Output; capture or choose the intended notes, then test one trigger at a time. Apply Full Major/Minor fills a chord scheme; Remove Note and Remove All Chords clear assignments, so confirm before removing work.
MIDI Arpeggiator — Stage
- Set the arpeggiator rate here; choose a direction with the arrow buttons.
Add Arpeggiator in MIDI FX and double-tap its card. Choose a direction button (up, down or the other displayed orders), set Rate, and use Variation and Oct to adjust variation and octave span. Choose a Pattern for the step-velocity shape; adjust its faders, then hold notes to hear the rhythmic output. Latch retains the phrase after keys are released; stop or disable it deliberately before changing presets. The pattern controls expose the step velocities for editing.
Keep the app tempo appropriate when using musical rate divisions. Test interaction with Chords carefully: generating several notes before an arpeggiator changes the phrase compared with processing single notes.
Expected result
What you should have now
You can verify MIDI arrival before configuring mappings and distinguish note processing from audio effects.
Common problems
- Controller is absent
- Check USB data support/power or Bluetooth compatibility and permission prompts, then refresh sources.
- Capture receives events but a channel is silent
- Review source filters, key bounds, plan restrictions and sound readiness.
- Mapping controls are locked
- MIDI Learn and expressive mapping require Stage or Pro.
- A phrase continues after release
- Check arpeggiator Latch and sustain; use Panic if notes get stuck.