MIDI Mapping Templates Library — Free Downloads for Every Major DAW

Building a MIDI mapping from scratch is the most tedious part of using a new controller. You sit there with the manual, you click MIDI Learn, you wiggle a stick, you click Save, you wonder if CC 24 was supposed to be channel volume or filter cutoff, you forget which face button you've already assigned. Forty minutes later you have something that almost works. We did this forty times so you don't have to. Behold: the mapping library.

What's in the library

Every template is built around a common philosophy: face buttons are notes (so they trigger clips and pads), shoulders and triggers are continuous CCs (so they sweep filters and macros), sticks are paired CCs (so they drive XY effects), and the touchpad is two CCs plus a click-to-arm note. From there each preset specialises for its target host.

Template	Target	Tier	Highlights
Ableton Live (default)	Ableton 11/12	Free	Session nav on d-pad, scene launch on L1/R1
Logic Pro 11	Logic	Free	Smart Controls macros, transport on options/share
FL Studio 21	Image-Line FL	Free	Channel rack pads, mixer fader on triggers
Bitwig Studio 5	Bitwig	Free	Per-note modulation, grid macros
Reaper	Reaper	Free	Action ID binding via OSC bridge, transport hotkeys
Resolume Arena 7	Resolume	Free	Clip launch, deck crossfade, touchpad XY effects
Cubase 14 (Quick Controls)	Cubase	Pro	Generic Remote XML included
TouchDesigner	Derivative	Pro	CHOP-ready, full gyro support, 250 Hz polling
MadMapper 5	MadMapper	Pro	Surface masks, beat-sync triggers
Notch Builder	Notch	Pro	Modifier nodes pre-bound to sticks
VCV Rack 2	VCV Rack	Pro	MIDI-CC mapping, polyphonic-stick mode
Drum Performance	Any DAW	Free	16-pad layout, velocity from trigger pressure
DJ Crossfade	Mixxx, Traktor	Pro	Sticks as jog wheels, triggers as filter
Camera Operator	OBS, vMix	Pro	Scene switching, source visibility, audio mute

How the templates are built

Each template is a plain JSON document. You can open one in any text editor, version-control it, diff between revisions, and bulk-edit. The schema is documented and stable.

{`{
  "$schema": "https://midi.aidxn.com/schemas/mapping-v2.json",
  "name": "Ableton Live (default)",
  "version": "2.1.0",
  "controller": "any",
  "lanes": [
    { "input": "button.cross",   "type": "note", "value": 60, "channel": 1 },
    { "input": "button.circle",  "type": "note", "value": 62, "channel": 1 },
    { "input": "button.square",  "type": "note", "value": 64, "channel": 1 },
    { "input": "button.triangle","type": "note", "value": 65, "channel": 1 },
    { "input": "trigger.l2",     "type": "cc",   "value": 1,  "channel": 1, "curve": "cubic" },
    { "input": "trigger.r2",     "type": "cc",   "value": 2,  "channel": 1, "curve": "cubic" },
    { "input": "stick.left.x",   "type": "cc",   "value": 3,  "channel": 1, "deadzone": 0.06 },
    { "input": "stick.left.y",   "type": "cc",   "value": 4,  "channel": 1, "deadzone": 0.06 },
    { "input": "touchpad.x",     "type": "cc",   "value": 16, "channel": 1 },
    { "input": "touchpad.y",     "type": "cc",   "value": 17, "channel": 1 },
    { "input": "touchpad.click", "type": "note", "value": 84, "channel": 1 }
  ]
}`}

Why JSON, not a binary format

We considered a binary format. We talked ourselves out of it in twenty minutes. Plain JSON is diffable in git, editable in any text editor, parseable by any scripting language, and human-readable. The performance cost (a few microseconds at startup) is trivial. Community contributors can edit templates without writing a single line of code, and you can `cat` your mapping in a terminal when debugging.

Get Universal Controller MIDI Pro — $89 →

Importing and exporting

# Export the active mapping
$ ucmidi mapping export ./my-live-set.json

# Import a friend's mapping
$ ucmidi mapping import ./friend-vj-rig.json

# Diff two mappings to see what changed
$ ucmidi mapping diff ./preset-a.json ./preset-b.json

# Validate against the schema
$ ucmidi mapping validate ./custom.json --schema v2

The CLI ships with the desktop app. If you live in a terminal, you can manage mappings without ever opening the GUI.

Contributing a template

Pro users get an in-app "Submit to library" button. Hit it, fill in the metadata (target app, version, description), and the mapping is uploaded to our submissions queue. We sanity-check, test on real hardware, and ship the accepted ones in the next release with attribution. Templates currently in review include rigs for Vital, Serum, Diva, and a 16-step sequencer built entirely on the d-pad and face buttons.

Limitations

• Templates are starting points. Every producer's session is different — expect to tweak a handful of lanes.
• Per-DAW behaviour varies. A note-on in Ableton triggers a clip; in Logic it plays the highlighted instrument. Templates pick sensible defaults but cannot fully abstract DAW differences.
• Older versions of host apps may not understand newer CC numbers. The shipped templates target current major versions only.
• Community contributions are reviewed for quality. We do not ship random uploads.

Quit clicking MIDI Learn one parameter at a time. Grab Universal Controller MIDI, pick a template, and have a fully-mapped controller in under 60 seconds.