Tutorials · 12 min read

Connect a MIDI keyboard and map controls

Verify real incoming MIDI before learning a controller for your rig.

Your guide, your screenAndroid · landscape
Showing phone screenshots and instructions

Before you begin

  • A compatible real USB or Bluetooth MIDI controller; USB connections need a data-capable cable and sufficient power.
  • Stage or Pro for MIDI Learn and mapping. A ready instrument and wired audio are useful for testing.

1. Establish the connection

Android’s connected-device screen provides the real system context.Pixel 10a
  • Tap Pair new device to start Android pairing; MIDI support depends on the controller and companion app.
InPraise Keys lists actual available MIDI sources.Pixel 10a
  • Tap Refresh MIDI Sources after connecting a keyboard.

The screenshots show real settings on unconnected emulators. They do not claim a successful physical-device connection.

  1. Connect a USB controller with an appropriate data cable/adapter and grant Android prompts. For Bluetooth MIDI, follow the device’s connection instructions and enable Bluetooth in Android.
  2. Tap Settings, then Midi Settings in the category list, scrolling if needed. Use the back arrow to return to the list.
  3. Choose Refresh MIDI Sources and look for the actual controller.
  4. Check Attributes > Input uses Any device or includes that source.

2. Verify messages first

Use Capture to inspect arrival before changing mappings.Pixel 10a
  • Use Capture to start or pause the MIDI event log.

Learning cannot succeed if the app is not receiving the hardware message.

  1. Enable Capture in Midi Settings.
  2. Play one note, release it, then move one knob or fader.
  3. Confirm the intended note/controller messages in the monitor and clear the capture when finished.

3. Learn and test a target

Learn mode reveals the actual eligible control targets.Pixel 10a
  • Tap a gray control, then move the MIDI control you want to assign.

Choose one control at a time and keep audio at a safe level.

  1. Begin MIDI Learn from Midi Settings or the intended target’s learn action.
  2. Select the target and move one hardware control through a small range.
  3. Finish learning and test the target in normal performance mode.
  4. Check the response direction/range and save the intended rig. For CC1 expression, review mod-wheel mappings and Ignore Mod Wheel on the channel.

Expected result

What you should have now

With your controller connected, its real events appear in Capture and the learned target follows the intended hardware control. The emulator captures illustrate configuration, not a hardware test.

Common problems

No source appears
Check cable data support, controller power, Bluetooth MIDI compatibility and Android permissions.
Notes arrive but the sound does not
Review the channel’s source filter, key range and sound/plan readiness.
Wrong target responds
Cancel learning and repeat with one control at a time.