Getting started
What AUTO/PILOT is, what you need, and the shortest path to a working rig.
AUTO/PILOT sits between your controllers and everything they should be driving — decks, effects, lighting, video — and turns that mess of cables and protocols into one programmable performance surface.
What you need
- macOS 13+ or Windows 10/11 (64-bit)
- One license pack (each pack unlocks 3 device activations)
- At least one MIDI, OSC or HID device — a controller, a foot switch, anything
The five-minute version
- Buy a license pack from the store. One payment, no subscription.
- Download the build for your platform from the downloads page. It is gated behind your license.
- Install and launch. The app asks you to sign in once.
- Sign in. The app claims one activation slot and caches an offline license, so it will keep running with no network from then on.
- Build your first map. Open Mappings → New, move a control on your hardware, pick a destination, save.
Concepts
| Concept | What it is |
|---|---|
| Route | A single input → output binding. A fader to a filter, a pad to a cue. |
| Macro | An ordered list of actions fired as one unit. |
| Scene | A named snapshot of routes and macro states you can recall live. |
| Surface | A physical device as AUTO/PILOT sees it, with its own layout. |
| Activation | One machine, holding one slot from your license pack. |
Where to go next
- Installation — platform specifics and permissions
- Licensing & offline behaviour — how the license actually works
- Device activations — managing your three slots
- Troubleshooting — when something is not behaving