MiniHub

Setups

Plug in. Be recognised. Download.

A setup says what a controller sends and where its controls sit on it. MiniHub reads one and draws your keyboard from it. Mapping a device is paid once per model — by whoever gets there first, and never again by anyone who owns the same hardware.

This page can listen for the controller you have plugged in and tell you whether anyone has mapped it. Nothing is recorded and nothing is sent: the matching happens here, in your browser.

Needs Web MIDI · Chrome, Edge and other Chromium browsers · one permission prompt, no sysex

Published

What has been mapped so far.

Each card is a file, drawn from its own contents: the schematic below is generated from the coordinates in the setup, not illustrated by hand. A setup names the hardware, never the person — two people mapping one keyboard produce two files that MiniHub can swap without cutting a single cable.

Arturia BeatStep

arturia-beatstep · revision 1 · no nickname given

Controls
4117 knobs, 16 pads, 8 buttons
Answered
329 declared silent
Written
2026-09-05format version 1

Recognised by the port it announces

  • BeatStep performance

Download arturia-beatstep.json

Arturia MiniLab 3

minilab-3 · revision 1 · no nickname given

Controls
298 knobs, 4 faders, 1 main encoder, 1 encoder click, 2 touch strips, 4 utility keys, 8 pads, 1 display
Answered
25every one observed
Written
2026-09-04format version 1

Recognised by the port it announces

  • Minilab3 MIDI performance
  • Minilab3 ALV performance
  • Minilab3 MCU/HUI control-surface
  • Minilab3 DIN THRU ignore

Download minilab-3.json

Once downloaded

Three steps, and the window reloads.

1 · Open your controller's page
In MiniHub's sidebar, under System. That is where a keyboard is loaded and unloaded — not in Settings, which is about where files are written.
2 · Import a profile…
That is the button, word for word. The file you downloaded is called a setup here and a profile in the format MiniHub reads; they are the same thing.
3 · Load it
The window reloads, because the controller's identity is fixed before the first line of the interface runs. Your project, its cables and its nodes come back as they were.

Yours

Mapped a keyboard nobody has?

The Builder writes the file in your browser, from your own gestures and a photo of your own device. Sending it here is what turns one evening of calibration into something every other owner skips.

For now a setup arrives by hand, through the issues of this site's repository · no account, no queue and no moderation are planned: that is what the rest of this design owes