Most Orba problems come down to four things: a low battery, a charge-only USB cable, an out-of-date app or firmware, or a stale Bluetooth pairing. Work through the checks below in order and most issues clear in under ten minutes.
This guide covers Orba, Orba 2 and Orba 3, and replaces our older one-problem-per-page articles.
Quick checklist before anything else
- Charge the Orba for at least 30 minutes with a known-good USB-C cable and wall adapter.
- Restart the Orba (hold the power button until it switches off, then turn it back on).
- Update the Artiphon app on your phone and close any other music apps.
- Check for a firmware update in the app and let it finish without locking your phone.
- Try a second device (another phone, tablet or computer) to see whether the problem follows the Orba or the device.
Bluetooth won’t pair or keeps dropping
- Remove the old pairing. In your phone’s Bluetooth settings, forget the Orba, then pair again from inside the Artiphon app rather than from the system menu.
- One host at a time. An Orba connected to a laptop will not show up properly on your phone. Disconnect it everywhere else first.
- Distance and interference. Keep the Orba within a couple of metres, away from Wi-Fi routers and wireless earbuds charging cases.
- Permissions. On iOS and Android, the app needs Bluetooth (and on some Android phones, location) permission to find nearby devices.
After a major iOS or Android update, a fresh pairing fixes most “it worked yesterday” problems.
Computer doesn’t see the Orba over USB
Many cheap USB-C cables only carry power. If the Orba charges but never appears as a MIDI device, swap to a data cable, ideally the one that came in the box. On older laptops with only USB-A ports, use a quality USB-A to USB-C data cable or a powered hub rather than a passive adapter chain.
Then check that your DAW is looking for it: the Orba should appear as a MIDI input in the DAW’s MIDI or controller settings. Enable it as an input and arm a software instrument track.
MIDI mapping problems
- Notes play but the wrong sound triggers: check which MIDI channel each Orba mode sends on and match the DAW track to it.
- Tilt or pressure does nothing: the receiving synth must understand MIDI CC or MPE. Turn on MPE mode in the synth, or map the Orba’s controls with the DAW’s MIDI learn.
- Stuck notes: send “all notes off” (most DAWs have a panic button) and check for a MIDI loop where the DAW sends notes back to the Orba.
Latency in home setups
Bluetooth MIDI adds a little delay compared with USB. For recording, use USB-C and set your audio interface buffer to 128 samples or lower. For practice, Bluetooth is fine. If you hear the Orba’s own speaker and the DAW at the same time, turn the Orba’s volume down so you only monitor one.
Firmware update fails
- Charge above 50% before updating.
- Keep the phone unlocked and the app open for the whole update.
- Turn off battery-saver mode on the phone.
- If the update stalls, restart both devices and try again over a fresh pairing.
If an Orba will not start after a failed update, contact Artiphon support with your serial number before trying anything drastic.
Battery drains quickly
Brightness, speaker volume and haptics all use power. Lower the volume when using headphones, unpair Bluetooth when you use USB, and switch the Orba off rather than leaving it idle. Lithium batteries also age: an Orba used daily for several years will not last as long per charge as a new one. Store it partly charged if you will not use it for weeks.
Pads feel unresponsive or too sensitive
Clean the surface with a soft, slightly damp microfibre cloth; skin oil and dust affect touch response. Sensitivity settings live in the app, so adjust them there before assuming a hardware fault. Cold hands also register less reliably, so warm up before a session.
Care and lifespan
- Carry it in a padded case: small hard cases.
- Keep it out of hot cars and direct sun.
- Do not use alcohol or solvent cleaners on the touch surface.




[…] Not detected or MIDI misbehaving? See Orba troubleshooting. […]