Traktor Pro 4 MIDI mapping, explained

Every MIDI controller that drives Traktor Pro 4 — hardware or an iPad — does it through one system: the Controller Manager and its .tsi mapping files. This guide explains how that system actually works: In and Out mappings, importing and exporting, modifiers, and the pitfalls that catch people. It's written by the team behind Interaktiv Tap, whose mapping toolchain reads and writes the .tsi format byte-for-byte.

How Controller Manager is organised

Open Preferences → Controller Manager and you'll find three ideas doing all the work:

• A device — one entry per controller, with an In-Port and an Out-Port. This is how Traktor knows which physical (or virtual) MIDI device a mapping belongs to.
• The assignment table — the rows of the mapping. Each row binds one MIDI message (a note or CC on a channel) to one Traktor command, in one direction.
• The command — the thing in Traktor being driven: Play, a loop size, an FX knob, a hot cue. Traktor exposes around 550 of them; the full command list is a page of its own.

Everything else — interaction modes, device targets, modifiers — is detail on those rows. A finished mapping is just a large, carefully consistent assignment table. Interaktiv Tap's, for example, is the set of commands it plays from the iPad, each with its direction.

In mappings, Out mappings, and two-way control

In mappings carry your gesture into Traktor: press a pad, move a fader, and the bound command fires. Buttons choose an interaction mode — Hold (active while pressed), Toggle, Direct (set a specific value), Inc/Dec (step through values), Reset. Faders and knobs are Direct (absolute position) or Relative (nudge from where Traktor is).

Out mappings go the other way: Traktor reports state back to the surface — a hot cue lights up, a loop size readout changes, a level meter moves. A control that should both send and reflect state needs both rows for the same command: an In and an Out.

That two-way loop is what separates a surface that feels alive from one that's guessing. When a mapping covers Out properly, the controller always shows Traktor's real state — what's playing, what's looped, what the FX are doing — instead of what it hopes the state is. It's the difference you feel immediately on a screen-based surface like an iPad, where the display is the controller.

The .tsi file: import, export, back up first

A .tsi is Traktor's settings container. For mappings, it carries the device setup and the entire assignment table, so a mapping that took days to build imports in one step.

• Back up before importing. Export your current settings to a .tsi first — an import can overwrite the categories you tick, and this is the undo button.
• Import via Preferences → Import, then tick what the mapping needs — for a controller mapping, that's Controller Mappings (some mappings also ship an effects selection).
• After importing, select the device in Controller Manager and point its In-Port and Out-Port at your controller. A mapping with no ports assigned looks broken but isn't — nothing is arriving.

One honest note on scale: hand-building a serious mapping in the assignment table is slow — every row is added and configured by hand, and a two-way surface needs In and Out rows kept consistent. That's why complete mappings are shared as .tsi files, and why Interaktiv Tap generates its .tsi from the same source of truth as the app itself, so the two never drift apart.

Modifiers: layers without more hardware

Modifiers (M1–M8) are eight variables, each holding a value from 0–7, that rows can read as conditions. Map a shift button to set M1=1 while held, then give other rows the condition M1=1, and the same pads do different things with shift down. Two rules keep this sane: use as few modifier states as you can, and write down what each one means — a mapping with five undocumented modifiers is unmaintainable, including by you in three months.

The pitfalls that catch people

• No ports set. The most common "my mapping doesn't work": the device's In-Port/Out-Port were never pointed at the controller after an import.
• Two rows fighting. Two In rows bound to the same channel + CC — or two devices both listening to the same hardware — make controls fire twice or fight each other. Keep one device per controller and scan for duplicates when editing.
• Parameter jumps. An absolute fader that's out of sync with Traktor snaps the parameter the moment it moves. Soft Takeover (per In row) or Relative mode avoids the jump — the classic mid-set mistake this prevents is a volume or filter leap.
• Resolution expectations. A standard CC has 128 steps. Plenty for FX and EQ; coarse for something like a long-throw pitch move. Design the mapping around where fine control actually matters.
• Echo loops. When a command is mapped both In and Out, a surface that blindly re-sends whatever it receives can loop Traktor's echo straight back. Well-built surfaces deduplicate — they only send on a real change.

Build one, or import a finished one

If you enjoy the craft, building your own mapping teaches you Traktor's insides like nothing else — start small, back up often, and keep the command list open. If you'd rather play than wire, import a finished mapping and spend the evening on music instead.

Interaktiv Tap is the second path taken seriously: a multi-touch instrument for iPad that plays Traktor Pro 4 over one USB cable. The mapping — every command it plays, fully two-way — is already designed, and the app exports its matching .tsi for the one-step import above. If you're weighing the options, here's how playing Traktor from an iPad works and how the iPad Traktor controller options compare.

FAQ

What is a .tsi file?

Traktor's settings container. For mappings it carries a device's full Controller Manager setup — every In and Out row — so a complete mapping imports in one step.

How do I import a mapping into Traktor Pro 4?

Back up first (export your own .tsi), then Preferences → Import, tick the categories the mapping needs, and set the device's ports to your controller.

Can I use an iPad as a MIDI controller for Traktor?

Yes — over USB an iPad is a standard MIDI device, so Traktor maps it like any controller. Interaktiv Tap ships that as a finished instrument rather than a blank surface.

Where's the full list of mappable commands?

On the Traktor Pro 4 command list — every Controller Manager command, by category.