No Learn step, what auto-recognise means

Every live-performance DAW I’d used before LiveSet started with the same wizard. You plug in a Maschine. The app pops up a “configure your controller” dialog. You click “next” nineteen times, you accept the default mapping and discover ten minutes later that the pads don’t match the screen because the wizard mapped them by MIDI note instead of physical position.

The wizard is a polite confession. The app doesn’t know your controller. It’s asking you to teach it. The reason every DAW has one is that every DAW gave up.

What plugging in does

When you plug a USB controller into LiveSet, three things happen in roughly fifty milliseconds.

First, we read the USB descriptor. Every device on USB advertises its name. “Maschine MK3” or “MPC Live II” or “Launch Control XL” come through as plain strings. That alone is enough for ninety percent of the work.

Second, we look up the device in our spec database. We ship a YAML file with the controller spec for every supported device, pad layout, encoder count, LED protocol, transport buttons, whether the device has aftertouch. The spec was hand-written against the manufacturer’s MIDI implementation chart. It’s the same data the wizard would have asked you to enter, but we entered it once and shipped it.

Third, we bind by role, not by number. The pads on a Maschine become the scene matrix. The encoders become the FX knobs. The transport becomes transport. None of this depends on which MIDI note number the manufacturer chose. It depends on which physical button does what on the device. Swap a Maschine for an APC mini mid-set and the scene matrix moves to the APC’s pad grid without rebinding anything.

That’s it. No wizard, no learn, no setup. Plug in and play.

What we refuse to add

Once every couple of months somebody asks us to add a “MIDI Learn” feature. We always say no, and we always explain why.

MIDI Learn is the wizard, dressed up. It still requires you to wire every parameter manually. It still requires you to teach the app something we should already know. It still scales linearly with the number of parameters: a Push 2 has 64 pads, 8 encoders, 24 buttons, a touch strip, and a pressure-sensitive ribbon, and Learn would have you teach the app every single one. That isn’t a feature; that’s homework.

We also already have MIDI Learn for the rare cases where you need it. Plug in a controller the spec database doesn’t recognise, your friend’s weird boutique fader bank, and the Bind panel lets you map any control to any parameter in three clicks. It’s there, you don’t need it for any commonly-used device, and we don’t put it on the front of the experience.

What “tentative” means

Some controllers are listed as Tentative on our controllers page. That’s not us hedging. It means we have the device’s MIDI implementation chart, the spec parses correctly, and the device should work, but we haven’t physically tested every model in the family. The Maschine Mikro Mk3 is tentative for that reason. The Mk3 is verified because it’s our primary test rig.

When you plug in a tentative device, the Settings panel tells you it’s tentative. The app still binds it. The chip just says “tentative” instead of “verified”. You know what you’re getting.

Why this is the right hill to die on

Live performance is full of small frictions that add up. A Learn wizard at the start of every gig is one. A controller that almost works is another. A mapping that doesn’t survive a project move is a third. Each of them costs a few minutes that should have gone into the music.

We took those minutes back. The controller works the moment USB clicks in, and you spend the time you saved on the set.