Before you begin
- InPraise Keys installed on a supported Android phone or tablet, with the sounds you want ready in Download Manager.
- The connection and power requirements for your Android device, MIDI keyboard and audio interface. Check the exact models before buying adapters.
- Free Demo is enough to check connections using available keys and sounds. Player and above remove the timed-session and muted-key restrictions for performance.
1. Choose a practice or stage rig
- Play a key to audition the current sound.
You can start with the onscreen keyboard and a wired listening output. An external MIDI keyboard makes playing more comfortable; a USB audio interface adds a convenient connection to headphones and a PA. MIDI carries performance messages. The sound is generated by InPraise Keys and leaves through the selected audio output.
For a stage rig, plan three things together: MIDI into the Android device, audio out to your mixer, and enough power for the complete setup. Use the equipment you already own for an initial test before choosing upgrades.
| Item | Practice | Stage setup |
|---|---|---|
| Android phone or tablet | Supported Android version, ready sounds and enough storage. | The same device, tested with the full setlist and its heaviest presets. |
| Wired headphones | Use a headphone jack or an Android-compatible USB DAC/adapter. | Use the interface’s headphone output to check the sound before involving the PA. |
| MIDI keyboard | Optional; the onscreen keyboard works. | USB MIDI with a data cable, or DIN MIDI through a compatible USB-MIDI device. |
| Audio interface | Optional if your wired output is satisfactory. | Android-compatible USB audio, a headphone output and suitable line outputs for the mixer. |
| USB hub and power | Needed when your connections exceed the available ports. | Enough data ports, a compatible charging path and adequate power for every peripheral. |
| Audio cables / DI | Short cables to local speakers when needed. | Correct left/right cables; use an appropriate stereo DI or isolator when the mixer connection requires it. |
| Stand and spare cables | Keep the device and USB connectors supported. | A secure mount, accessible controls, strain relief and known-working spare data/audio cables. |
2. Check compatibility before choosing an interface
USB class compliance means a device follows a standard USB protocol rather than depending on a desktop driver. It is a useful starting point, but it does not establish compatibility with every Android device or every USB audio mode. Check the manufacturer’s Android guidance, power requirements and supported sample rates for the exact model.
For audio, look for a working 44.1 or 48 kHz stereo playback mode, a headphone output and the connections your mixer expects. For a USB MIDI keyboard, confirm a class-compliant MIDI mode and use a cable that transfers data. A connector shaped like USB-C does not tell you whether the cable, hub or device supports the required features.
Check that your phone or tablet supports USB host/OTG operation. If you intend to charge while using USB peripherals, confirm that the device and hub support that combination. A powered hub supplying a keyboard does not automatically mean the Android device is charging.
USB MIDI input
- Class-compliant USB MIDI mode
- Android USB host/OTG support
- Source appears in Midi Settings
USB audio output
- Supported stereo playback mode
- Android recognizes the interface
- Active device appears in Audio settings
Power while connected
- Device supports USB host use
- Hub supports the required charging path
- Android reports that it is charging
3. Connect a USB-C stage rig
A compatible USB-C hub can share the device’s port between a MIDI keyboard, an audio interface and charging. Connect the charger to the hub’s marked PD input, not to an arbitrary data port. Supply a separately powered interface or keyboard using its own manufacturer-approved power connection when required.
Size the power supply for the device, hub and connected peripherals according to their specifications. The wattage printed on a charger alone does not prove that a hub provides enough power at each port. Check the Android charging indicator and peripheral stability during a full rehearsal.
MIDI into the app
- USB MIDI keyboard
- Hub data port
- Android / InPraise Keys
Audio out of the app
- Android / InPraise Keys
- Hub data port
- USB audio interface
- Mixer / monitors
Power
- Compatible charger
- Hub PD input
- Android + powered peripherals
- Lower the PA and interface output levels while connecting the rig.
- Connect the compatible charger to the hub’s PD input and attach the hub’s host cable to the Android device.
- Connect the keyboard’s USB-to-host port to a hub data port using a data cable. Connect the interface’s USB data port to another hub data port.
- Connect any required separate peripheral power supplies. Then connect wired headphones to the interface.
- Open InPraise Keys, allow its USB access request if presented, and verify the actual audio and MIDI devices in Settings.
4. Connect a keyboard with five-pin MIDI
If the keyboard uses traditional five-pin DIN MIDI, connect its MIDI OUT to MIDI IN on a compatible USB-MIDI adapter or an audio interface that includes MIDI input. The USB device then carries those note messages to Android. An audio interface without MIDI sockets cannot accept a DIN MIDI cable.
A keyboard’s sustain pedal normally plugs into the keyboard, which sends the pedal messages with its notes. Select the incoming source and inspect it in InPraise Keys before creating mappings. Bluetooth audio pairing is not a MIDI connection; the current app uses MIDI devices exposed by Android and does not provide its own BLE MIDI scanner.
Note and pedal messages
- Keyboard MIDI OUT
- USB-MIDI device MIDI IN
- USB data connection
- Android / InPraise Keys
5. Send clean audio to headphones and the PA
An interface’s headphone output is a useful first listening point. For the PA, connect its left/right line outputs to suitable mixer inputs using the interface and mixer manufacturers’ cable guidance. If your source is an unbalanced headphone output, a suitable stereo DI can convert the feed for a balanced connection to the stage box. Agree the input type and levels with your sound engineer.
A headphone socket carries left and right channels in one stereo plug. A balanced mixer input normally receives one channel. Use a proper stereo breakout into two inputs or a stereo DI; a single stereo-to-balanced cable can produce an incomplete or hollow sound. Label the left and right feeds.
If the venue needs mono, enable Mono Mode in Settings > Audio and listen to the result before soundcheck. A stereo breakout separates channels; it does not sum them to mono. Confirm that your pad and reverb textures still work when summed.
| Output | Connect to | Check |
|---|---|---|
| Interface headphone output | Wired headphones | Start with the headphone level low and verify the app’s mix. |
| Interface line outputs L/R | Appropriate mixer line inputs, or a DI when required | Use the correct cables and establish levels without clipping. |
| 3.5 mm headphone jack / USB DAC | Stereo breakout to suitable inputs or a stereo DI | Keep unbalanced runs short; preserve left and right until intentionally summing. |
| Mono PA feed | An agreed mono input/feed | Use the app’s Mono Mode and audition the complete mix. |
Local headphone check
- InPraise Keys audio output
- Interface headphone output
- Wired headphones
Stereo PA feed
- Interface line outputs L/R
- Two suitable mixer inputs or stereo DI
- Label left and right at the mixer
Agreed mono feed
- Enable Mono Mode in Audio settings
- Audition the summed app output
- Connect to the agreed mono input
6. Verify your first sound in InPraise Keys
- Choose the audio output device here.
- Select the audio sample rate here.
- Use Capture to start or pause the MIDI event log.
Tap Settings, then Audio in the category list, scrolling if needed. Use the back arrow to return to the list.
Check the Output row’s active device, not just that a USB cable is attached. The USB Audio Driver row appears when a USB interface is available. Leave the current driver selected initially; if the device has no sound or crackles after basic cable/power checks, try the alternative Signature or Studio driver and retest.
- Load one ready piano or other simple instrument. Play an available onscreen key through the wired output.
- Choose the intended device in Audio > Output and confirm the Active label. Start the patch if the screen asks you to start playback.
- Open Settings > Midi Settings. Select the keyboard source when needed, press keys and use Capture to check incoming note and sustain messages.
- Compare the onscreen keyboard with the MIDI keyboard. If onscreen notes work but MIDI notes do not, resolve MIDI input/channel/range settings before changing the audio buffer.
- Test the interface’s headphones, then bring up the PA levels with the sound engineer. Clear unwanted Mute/Solo controls and check both stereo sides.
7. Rehearse with the complete rig
- Show stats for nerds reveals live audio path details.
- Reported output latency includes the device audio path.
Keep the device supported and its controls reachable without pulling on USB connectors. Give it ventilation while charging. Set up notification/focus preferences so an unexpected alert does not interrupt the performance, then verify that those preferences still allow the app and your peripherals to work.
Run the full setlist with the actual charger, hub, keyboard, interface and monitoring path. Include sustained chords, dense layers, preset changes and the recording workflow if you will use it. Check that the device keeps charging, the peripherals remain connected, and the sound stays clean after the rig warms up.
- Finish required sound downloads and open each performance preset before going offline.
- Rehearse your loudest and most complex passages, then check stereo/mono behavior with the sound engineer.
- Write down the working output, driver, sample rate and buffer, and label the essential cables.
- Keep a known-working spare data cable and a simple wired listening path available for troubleshooting.
Expected result
What you should have now
You can identify the MIDI, audio and power paths; play the app from your controller; hear clean wired audio; and repeat the setup with a tested connection to your mixer. Physical compatibility and performance are established by rehearsal on your own rig.
Common problems
- The interface lights up but is missing from Output
- Check USB host support, the data cable, hub data port, USB permission and interface power. Test a supported direct connection to isolate the hub, then check the manufacturer’s Android requirements.
- The phone is not charging
- Confirm the charger is connected to PD input, the hub and phone support charging while hosting USB, and the negotiated power is adequate. Powering peripherals is a separate check from charging the phone.
- Onscreen notes play, but keyboard notes do not
- Inspect Midi Settings > Capture, the selected source, MIDI channel and playable range. Check that a DIN cable runs from keyboard OUT to adapter IN. MIDI messages are not audio.
- Audio reaches headphones but not the PA
- Check interface line-output levels, left/right cables, mixer input type, channel Mute and PA routing with your sound engineer.
- The sound is hollow or one side is missing
- Verify the stereo breakout and both mixer channels. Avoid treating a stereo headphone plug as a single balanced channel; intentionally sum to mono when required.
- There is hum when the charger or PA is connected
- Compare the interface’s headphones with the PA feed. Ask the sound engineer to check balanced cabling and suitable audio isolation/DI; keep mains protective grounding intact.
- The USB device disconnects during rehearsal
- Check peripheral power, hub compatibility and cable strain. Remove unnecessary peripherals, use a known-working data cable, and repeat the warm rehearsal test.