LiveSet · mapping
MIDI mapping without a setup step
Bring your own controller and there is no template to hunt for. The engine reads the port name, recognises the device, and maps it by the role of each control, pads as a grid, faders as a bank, knobs as a bank, transport as transport. No Learn step. The roles grow to fit the project you are playing.
Mapped by role
The engine binds each control by what it is on the device: a pad grid stays a pad grid whatever note numbers it happens to send. Swap a Push for an APC mini mid-set and the mapping carries over, because both have a pad grid, a fader bank and a knob bank.
Pad grid
The 8×8 on a Launchpad, the pads on a Maschine. Bound as a grid, so it becomes the scene matrix or the step grid without you assigning a single note.
Fader bank
A row of faders reads as a bank. Add a seventh track and the seventh fader has somewhere to go: the roles grow to fit the project.
Knob bank
Encoders and pots land on effect and mixer parameters as a set, in the order they sit on the panel. The MIDI numbers never come into it.
Transport
Play, stop, record and the nudge keys map to transport wherever the controller keeps them. The same buttons, whatever the box.
Honest about every controller
Around sixty-nine controllers, each with its confidence shown
Recognising a controller is easy to claim and hard to promise, so every entry in the table carries one of four tiers, recorded in the same file the app reads. A number on its own would be worth very little here. What the table is for is telling you which of the 69 we have actually had our hands on.
Verified
Checked against the manufacturer’s own MIDI implementation chart and carried with a citation URL. A build test fails any Verified entry that has no source, so the tier cannot quietly rot.
Community-derived
Mapped from shared community knowledge, with no manufacturer document. Marked plainly as such, with an open invitation to test it and report back.
Tentative
The MIDI parses and the roles line up on paper, but nobody has confirmed it on the hardware. Honest about the gap, which we do not hide.
Clock / manual only
A device with its own sequencer. The engine takes its clock and its notes and leaves its grid alone.
The families it knows
A recognised device auto-binds the moment it connects. These are the families with documented maps in the engine today.
Novation
Launchpad Mini, Pro and X, plus the Launchkey keyboards. The first family mapped end to end, and the reference for how a pad grid becomes a scene matrix.
Native Instruments
Maschine Mk3, Plus, Jam and Mikro, alongside the Komplete Kontrol keyboards. Pads, encoders and the transport row all carry roles.
Ableton Push
Push 2 is Verified against Ableton’s published map. Push 3 speaks the same MIDI and is carried Community-derived until it is confirmed on hardware.
Akai
APC40 Mk2 and APC mini for the grid, MPK Mini for pads and knobs, Fire for the step lane. Akai documents its MIDI well, which the tiers reflect.
Arturia
KeyStep, BeatStep and KeyLab. Arturia scatters its knobs across hand-picked CC numbers. The engine maps them by position regardless.
Elektron
Digitakt, Syntakt and Octatrack, taken as clock and notes only. They keep their own sequencers. The engine syncs and listens without ever steering.
Past the first plug-in
Macros
Auto-recognition gets you playing. Underneath it the engine carries the mapping depth a working rig needs: fan-out, MIDI Learn, pinning, LED feedback, and a mapping file you can take to the next venue.
Macro fan-out
One control can move many things. A single knob dispatches to several commands at once, or drives a macro whose targets each have their own range, curve and amount. One hand, a whole gesture.
MIDI Learn
For anything the engine has not already recognised: arm the target, wiggle the control, commit. A learned binding overrides the role for that port, so a personal map wins where you want it to.
Per-deck pinning
Pin a controller to one deck and it stays there. Four channel strips can each own a deck, so the same physical fader always means the same thing under the lights.
LED feedback
Pad and button lights are driven back out for several families, Launchpad, Push 2, the Akai APC and Fire, Launch Control XL and Maschine Mk3, so the surface shows what is playing and what is armed.
Seventeen rig presets
Curated pairings of two to four controllers, ready to pick as a starting rig, an APC40 next to a Launch Control XL, and the like, and never built from nothing.
Portable .rigmap.json
Export your whole mapping as a plain, versioned JSON file and carry it on a USB stick. Import is lenient: a bad entry is dropped and never fatal, which keeps hand- or machine-written files safe.
Where it stands
What the engine does, and what the app shows today
The recognition engine and the parametric roles are the substance here, and they are what make a controller work the moment it is plugged in. A few things sit outside the on-screen surface: the rig-mapping studio ships without controller photographs, there is no mapping-conflict detection, and soft-takeover: the guard that stops a knob jumping when its value differs from the parameter, is set in the mapping and never toggled on screen.