Learn OpenKeys from the first cable connection to a complete live performance. Every lesson uses clear steps, real interface images, and practical checks.
Get one playable piano-and-pad patch working before exploring advanced controls.
Follow one safe path from connected equipment to a rehearsed Verse–Chorus performance. Check a step only after its verification succeeds.
Verify: soft and hard notes both register, with no stuck notes.
Verify: leaving and reopening the setlist returns to the intended patch.
Verify: the piano remains clear and the combined loudest playing does not clip.
Verify: every recall restores the expected levels and active layers.
Verify: recalling each scene changes both the sound and visible lyric section.
Verify: five presses cause exactly one intended change each. Without a controller, verify the on-screen scene buttons.
Verify: sound, scene highlight, lyrics, MIDI control, CPU, and audio remain correct after reopening.
You proved the entire path—not only the individual screens. Continue with the full guide to refine the rig.
Build the signal path in a fixed order so MIDI, audio, and power problems are easy to isolate.
Play several notes and look for MIDI activity. If the app responds, verify the selected audio output. Raise the OpenKeys master first, then the interface, then the speakers.
Test the lowest and highest keys you expect to use.
Four levels keep preparation separate from performance.
Create and order setlists, build patches, balance layers, add effects, save scenes, prepare OpenNotes, and assign MIDI controls.
Choose patches and scenes, read notes, use OpenPads for transitions, and keep edit controls locked unless a deliberate change is needed.
Simple ruleThe setlist chooses the order. The patch chooses the sounds. A scene chooses the state of those sounds for a musical moment.
Organize the whole service before changing individual sounds.
Use Copy and Paste to setlist to make an independent copy in another setlist. If the patch has unsaved changes, deliberately choose whether to save and copy the working version or copy the last saved version.
Rename and reorder patches so their screen order matches the performance order.
Export individual patches when sharing one setup. Export the setlist when preserving the full order. Import into the intended destination and verify every external SoundFont reference afterward.
OpenNotes has its own backup; keep it with the setlist and source sound files.
The mixer is the central sound workspace. Each channel is one layer in the current patch.
SET opens layer configuration. FX opens effects. M mutes. S isolates the layer for checking.
The fader sets the musical balance. The meter shows signal level. Leave enough headroom for harder playing and combined layers.
Choose a SoundFont and preset for an empty layer. Audition across the actual keyboard range before committing.
Set low/high key range, transpose, octave, velocity response, sustain behavior, pitch bend, and Mod Wheel behavior for the layer.
Choose the controlling keyboard or MIDI channel, use MIDI Learn where offered, and verify Bluetooth MIDI separately before the service.
Use envelope, filters, reverb, delay, chorus, drive, compressor, arpeggiator, or sequencer only when the layer’s musical role requires them. Follow the displayed signal chain.
Use one repeated musical phrase while making decisions so every comparison is fair.
A scene stores a playable state of the current patch so one tap can move the arrangement from Intro to Verse, Chorus, Bridge, or Ending.
Tap a named scene to restore its captured track state. The active scene is indicated in the strip.
Set the track levels and states first. Tap +, give the scene a musical name, then save it.
Recall the scene, make the mixer changes, then use Update selected scene. Recall another scene and return to verify it.
Test the scene button, MIDI control, and OpenNotes cue separately. OpenPads and OpenNotes recall existing scenes; create and edit them from the mixer.
Use a sustained pad beneath speaking moments and transitions without occupying both hands.
Choose the OpenPads sound source, import or select a supported SoundFont/preset, and test all twelve note buttons. Match the displayed key to the song before engaging Latch.
Balance its dedicated volume, assign volume MIDI Learn when needed, and shape its effect chain separately from mixer layers. Use Release to end the pad cleanly and confirm its tail does not overlap the next key.
Create searchable song documents, divide them into sections, and keep scenes beside the lyrics in Performance Mode.
Change text size, pinch to zoom, select Paper, Dark, or OLED display, choose sharps or flats, and transpose displayed chords without rewriting the stored song.
Use the song-part buttons, auto-scroll, manual scrolling, MIDI actions, or a scene’s bound cue. Test every method before the live set.
The performance layout gives most of the screen to lyrics while keeping song parts and patch scenes within reach.
Assign only the actions you need while playing. The best mapping is easy to reach and hard to trigger accidentally.
A saved patch depends on its external sound files remaining available to the device.
Choose the lowest-latency mode that remains stable on the actual device, interface, and busiest patch.
Select the app theme and preview its stage contrast. Confirm text, active controls, meters, and scene selection remain readable under venue lighting.
Set master-related behavior and inspect rendered output. Use the recent-change and recovery controls only after understanding what state they restore.
Choose engine mode, output route, sample rate or USB format where supported, background behavior, and recovery options. Restart and retest after important changes.
Review connected USB and Bluetooth controllers, enable only the keyboards meant to play, and confirm channel/input behavior.
Use the built-in quick-start and recovery guidance when working directly on the device.
Check the installed version, official update route, support, and community links before reporting a reproducible problem.
| Mode | Frame size | Use it when | If unstable |
|---|---|---|---|
| OpenKeys Native | 64 frames | The supported device and connection remain clean under the heaviest patch. | Move to Low Latency Mode. |
| Low Latency Mode | 128 frames | You need responsive playing with more stability margin. | Move to Standard Mode or simplify the patch. |
| Standard Mode | 256 frames | Reliability is more important than the shortest response. | Reduce layers/effects and inspect the connection. |
Use the large scene grid when you need bigger recall targets than the mixer strip. It recalls the current patch’s scenes and shows MIDI assignments; edit scene content from the Scene editor.
On a phone, the dedicated keyboard view combines the performance keyboard, scene strip, and track controls. Use it for rehearsal or emergency playing, and verify octave/range before the song.
Check one system at a time: power, cable, permission, device selection, then patch configuration.
Confirm keyboard power, reconnect the USB cable, approve Android device access, and inspect the MIDI device list. Try another cable or hub port before rebuilding the patch.
Check the selected audio output, master level, channel mute states, interface gain, and physical speaker path. Start with levels low before reconnecting output hardware.
Choose the next safer latency mode, close unnecessary background activity, and retest the busiest scene. Remove unnecessary layers or heavy effects before adding more processing.
Confirm the active setlist and patch. Recall the scene, inspect its stored mixer state and OpenNotes cue, repair the binding, save it, switch away, and recall it again.
Check whether the source file was moved, renamed, or deleted. Restore it to its stable location or select it again, save the patch, and reopen it to verify.
Confirm the currently selected audio configuration and the feature access reported by the installed build. Do not switch audio modes mid-performance; use the prepared fallback instead.
Test the largest scene, remove unused layers, shorten or bypass unnecessary effects, use smaller required SoundFonts, and choose a safer buffer mode. Rehearse after each single change.
Reliability comes from rehearsing the complete system—including transitions and recovery—not just individual sounds.