Traktor MIDI mapping, explained — Pro 3 or 4
Every MIDI controller that drives Traktor Pro 3 or 4 does it through one place in Traktor's settings: the Controller Manager, which keeps each mapping in a .tsi file. This guide explains how it works — In and Out mappings, importing and exporting, modifiers — and the pitfalls that catch people, as of Traktor Pro 4.5.1, the version its screenshots and command list come from. It's written by the team behind Interaktiv Tap, an iPad app that plays Traktor through this same system.
Start here
- Is your controller already supported? Traktor has a ready mapping for every controller it supports. Find the list in Preferences → Controller Manager → Add… → Pre-mapped. If your controller is there (see the list), add it and you're done.
- Buying a controller? Before you buy, check that it is in that same Traktor list. If it is not (for example, it was made for another DJ app), it needs a mapping file to work with Traktor. Make sure one exists for Traktor Pro 3 or 4 before you buy: where to find Traktor mappings.
- Installing a mapping file? Back up first: Preferences → Export, with every box ticked. Then use Controller Manager → Add… → Import from disk…: it adds the mapping and keeps your other ones. Don't use Preferences → Import for this — it replaces all your controllers. To undo a bad import, open your backup with Preferences → Import.
- Your controller is not in Traktor's list? Look for a mapping from the controller's maker or from other DJs: where to find Traktor mappings.
- Some controls do nothing? In Controller Manager, set the device's In-Port and Out-Port to your controller. These are the ports Traktor listens and answers on. Then check the pitfalls.
- Building your own mapping? Start at how Controller Manager is organised. The sections after it explain every setting, in order.
- Using an iPad? See the iPad question below.
#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 more than 500 of them; the full command reference 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, Trigger (fire once), Direct (set a specific value), Inc/Dec (step through values), Reset. Faders, knobs and encoders are each offered Direct (absolute position) or Relative (nudge from where Traktor is); an endless encoder is normally mapped Relative. Every field of a row, in order, is below.
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 follows Traktor's real state as it changes — what's playing, what's looped, what the FX are doing — instead of what it hopes the state is. The moment it connects is the exception: Out rows send on change, so a freshly connected controller has to ask for the rest (the FAQ below says how). It's the difference you feel immediately on a screen-based surface like an iPad, where the display is the controller.
Two-way mappings have a ceiling most builders meet by accident: Traktor sends a device's whole state on request, and with Send MIDI Clock on that dump stops at about 500 messages. We measured it and wrote up how Send Monitor State behaves and how to stay under the line.
#Every field in Controller Manager, in order
Select any row in the assignment table and the panel beneath it shows the row's fields. This is the whole vocabulary — the same dozen fields, top to bottom, for a hot cue, a filter knob or a level meter. Read them once in order and a mapping stops looking like a spreadsheet of settings and starts reading as sentences: this message, on this control type, does this to this command, on this deck, when this condition holds.
#The row: Control, I/O, Assignment, Mapped to
- Control — the Traktor command the row drives or reports. Commands are grouped the way Traktor's own menus are (Deck Common, Mixer, FX Unit, Loop Recorder, Master Clock, Remix Deck…); the full command list is a page of its own.
- I/O — In (your controller drives Traktor) or Out (Traktor reports to your controller). One command, two directions, two rows.
- Assignment — which thing the command acts on: Deck A, B, C or D; Global; FX Unit 1–4; a Remix Deck slot; the Loop Recorder; the Master Clock. Device Target is the special one: the row follows whichever deck the device is currently focused on, so a two-deck controller can serve four decks with a deck-switch button instead of a second set of rows. The same command means different things per target — Play on Deck A and Play on the Loop Recorder are two rows with two lives.
- Mapped to — the MIDI message on the wire: a Note or a CC (Control Change) on a channel 1–16, or Pitch Bend. Learn fills it from the next message the controller sends, which is the honest way to find out what a button actually emits. Several In rows on the same message all fire together: on purpose, that is how a macro is built; by accident, it is the duplicate pitfall below.
- Modifier conditions — up to two M1–M8 = value tests; the row is live only while they hold. That is how one button gets a second life under a shift key — Modifiers and conditions beyond them have their own sections.
- Comment — free text. Use it: a hundred rows later it is the only thing that says why.
#Type of Controller, and the interaction modes each one offers
Traktor asks what kind of physical control sends the message, because that decides which interaction modes make sense. There are three types on the In side.
- Button — sends a press and a release. Modes: Hold (the Traktor button stays pressed as long as yours is — the default), Toggle (each press flips it), Trigger (fires once per press, no state), Direct (sets a specific value — see Set to value), Inc / Dec (one step up or down through a command with more than two values), Reset (back to the default, like a double-click with the mouse). Not every command offers every mode: Play/Pause offers Toggle, Hold and Direct; a tempo offers Direct, Inc, Dec and Reset. The menu tells you.
- Fader / Knob — sends an absolute position, 0–127. Modes: Direct (Traktor's control follows the position) or Relative (each movement nudges Traktor's value from where it is).
- Encoder — an endless knob that sends ticks, not positions. Traktor offers it Direct and Relative, like a fader; it is normally mapped Relative, so each tick moves the value a step from where it is. Its Enc.-Mode names the tick format the hardware uses: 7Fh/01h (127 means one step down, 1 means one step up) or 3Fh/41h (63 down, 65 up). Wrong format, and the knob turns one way only.
On the Out side the type is LED and the mode is Output: Traktor sends the command's state, and the range fields below say how.
Which mode to pick is the main design decision in a mapping, and it depends on what the button sends. A hardware button springs back when you let go, so on a controller Play/Pause is a Toggle — each press flips it — with an Out row that lights the button from Traktor's own state; that is how Native Instruments' tutorials map it, and the light cannot drift, because Traktor drives it. Mapped as Hold, the same button would play the deck only while your finger is down. Hold suits a surface that sends a level instead of a press — on for as long as it wants the deck playing, off when it wants it stopped — such as a touchscreen that keeps its own button state: the value on the wire is the request itself, so a repeated message changes nothing. Direct suits one-shots: Delete Hotcue with Set to value = Hotcue 3 deletes that one cue, and one Direct row per loop size on the single Loop Size Selector command gives every size its own button.
#The options under a row
- Set to value — appears with Direct: the value the press sets. For Hotcue Select it is the cue number; for Loop Size Selector one of its sizes; for Deck Flavor one of the four flavors. It is how a single command becomes eight hot-cue buttons.
- Invert — flips the sense: a Hold that is pressed when the button is up, a fader that runs the other way. Useful when the hardware's idea of "on" is Traktor's "off".
- Soft Takeover — faders and knobs in Direct mode: after a change Traktor made on its own (a snapshot, another controller, the mouse), the control does nothing until it crosses the value Traktor holds, then takes over. It prevents the parameter jump that catches people mid-set.
- Auto Repeat — buttons in Inc/Dec: keep firing while held, so a size or a tempo walks instead of stepping once per press.
- Resolution — how far one step or one tick moves the value, from Fine to Coarse. Coarse gets a filter across its range in a quarter turn; Fine is for key and tempo, where a step should be inaudible.
- Rotary Sensitivity and Rotary Acceleration — for an Encoder in both its modes, and for a Fader/Knob in Relative: how far one tick moves, and whether a fast turn moves further than a slow one. Invert sits with them.
#The Out side: Controller Range, MIDI Range, Invert, Blend
An Out row turns a Traktor value into a MIDI value for an LED, a ring or a meter, and four fields shape that translation. Controller Range (min and max) is the window of the Traktor value the row reports — for a button state that is simply 0 to 1; for a meter it is the span you want to see. MIDI Range is what goes on the wire at the two ends, 0–127. Invert swaps the ends. Blend decides whether the output moves smoothly between the ends or switches at a threshold — off for an LED that should be lit or dark, on for a meter or a ring that should breathe.
A real row, from Interaktiv Tap's mapping: Deck Common › Phase is an Out-only row with a Controller Range of −0.5 to 0.5, so the phase meter on the iPad centres when the deck is in phase and swings either way from there. Set that range to 0…1 by mistake and the negative half clips — the meter sits hard left while Traktor's own is centred. That one field is the difference.
#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. Preferences → Export, every box ticked, saves your current settings to a
.tsi— an import can overwrite the categories you tick, and this is the undo button: import that file again through Preferences → Import to get back to where you were. - Import a whole settings file via Preferences → Import, then tick what it needs — for a controller mapping, that's Controller Mappings (some mappings also ship an effects selection). That replaces your whole controller list; to add one mapping and keep the rest, use Controller Manager → Add… → Import from disk… (below).
- 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.
#Conditions beyond modifiers
The condition menu on every row holds more than M1–M8. Below the modifiers sit 25 conditions that read Traktor's own state — Deck Play, Deck Flavor, Slot State, Sample Page Selector, Hotcue State and the rest — so a row can exist only while a deck is a Remix deck, or only while a page is showing. That does two things a modifier cannot. It keeps the set of live rows small enough for Traktor's state dump to arrive whole. And when the condition turns true, Traktor sends the newly live rows by itself — a modifier flip sends nothing, so the lights under a shift layer keep what they showed until a value changes. The full list, with targets and values, is on the Send Monitor State page.
#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.
- Duplicates by accident. Two In rows on the same channel + CC both fire — which is exactly how a macro works when you mean it. When you don't (a row left behind after editing, or two devices both listening to the same hardware), a control fires twice or fights itself. Keep one device per controller, and when a control misbehaves, look for a second row on its message.
- 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.
#Where to find Traktor mappings, and how to install one
Looking for a mapping for a specific controller — an Akai MIDIMIX, a Behringer CMD, an M-Audio X-Session, even a plain MIDI keyboard? Start with what Traktor already has, then look further out.
- Built into Traktor. Controller Manager → Add… → Pre-mapped lists a ready mapping for every device this version of Traktor supports natively (the list is at the end of this section). If yours is there, you're done.
- From the controller's maker. Look on the product's support or downloads page: a maker's own
.tsiexpects the controller's own MIDI mode. - The community collections. DJ TechTools' mapping database is the largest public one: search by software and controller, and read the votes and comments from people who used each mapping (downloading needs a free account). Traktor Mappings is Stevan Djumic's site, with the free mappings he has built for many controllers over the years. For a Maschine, TraktorMapping.com offers free and premium Traktor mappings.
- Forums. For older or rarer hardware, the controller's name plus "Traktor mapping" on the DJ TechTools forum or Native Instruments' community usually turns up a shared file.
Before you trust a mapping, check four things: that it was made for Traktor Pro 3 or 4; that it names your exact controller and the mode it expects (many controllers can run in more than one mode — one made for a particular DJ app, another that sends plain MIDI — and a mapping works only in the mode it was made for; the controller's manual says how to switch); whether it includes Out rows, without which the controller's lights stay dark; and when it was last updated.
To install one without losing what you have:
- Back up first. Preferences → Export, every box ticked, saves your current settings to a
.tsi; importing it again the same way puts them back. - Add it as a new device. Controller Manager → Add… → Import from disk…, then choose the file. Your other mappings stay as they are. Preferences → Import with Controller Mappings ticked replaces the whole controller list instead.
- Point it at your controller. Set the device's In-Port and Out-Port, then move a control and watch Traktor answer.
If no finished mapping exists for yours, the Controller Manager sections above are exactly how you build 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.
Have an iPad? Interaktiv Tap, our own app, is a multi-touch instrument that plays Traktor Pro 3 or 4 over one USB cable, with its mapping — every command it plays, fully two-way — already built: the app exports its matching .tsi, and the mapping is also in DJ TechTools' database. If you're weighing the options, here's how playing Traktor from an iPad works and how the iPad Traktor controller options compare.
#The controllers Traktor maps out of the box
This is what Traktor Pro 4.5.1 lists under Controller Manager → Add… → Pre-mapped, maker by maker. If your controller is here, you don't need a file from anywhere else. Other versions of Traktor may list a few more or fewer.
- Traktor Kontrol: D2, F1, MX2, S2, S2MK2, S2MK3, S3, S4, S4MK2, S4MK3, S5, S8, X1, X1MK2, X1MK3, Z1, Z1MK2, Z2
- Native Instruments: Audio Kontrol 1, Kore 2, F1 Pattern Player, F1 Step Sequencer (Deck A, B, C and D), and Maschine, Maschine MK2, Maschine Mikro and Maschine Mikro MK2, each as Track Decks or Remix Decks
- Pioneer DJ: CDJ-400, CDJ-900, CDJ-900NXS, CDJ-2000, CDJ-2000NXS, CDJ-2000NXS2, CDJ-3000, CDJ-TOUR1, XDJ-700, XDJ-1000, XDJ-1000MK2, DDJ-ERGO, DDJ-T1, DJM-T1
- AlphaTheta: DDJ-FLX2, DDJ-FLX4
- Numark: DJ2GO2 Touch, Party Mix II, Party Mix Live
- Rane: Twelve MK2
- Reloop: Buddy, Ready
- Volta XR: MIDI Outputs
Anything not on the list needs a mapping file, from its maker or from the community collections above. And with no controller at all, Add… → New → Generic Keyboard maps your computer keyboard in the same Controller Manager.
#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?
Back up first (Preferences → Export), then Controller Manager → Add… → Import from disk…, which adds the mapping as a new device and keeps your others, and set its ports to your controller. Preferences → Import replaces the whole controller list.
#Where can I download Traktor mappings?
First check Traktor's own list (Controller Manager → Add… → Pre-mapped), then the controller maker's support page, then DJ TechTools' mapping database and Stevan Djumic's Traktor Mappings site. Pick one made for Traktor Pro 3 or 4 and your controller's mode, and back up before importing.
#Which controllers does Traktor map out of the box?
The ones under Controller Manager → Add… → Pre-mapped: Native Instruments' Traktor Kontrol controllers and several Maschine models, Pioneer DJ CDJs and controllers, AlphaTheta's DDJ-FLX2 and DDJ-FLX4, Numark's DJ2GO2 Touch and Party Mix models, Rane's Twelve MK2 and Reloop's Buddy and Ready. The full list, as Traktor Pro 4.5.1 shows it, is above.
#Can I use an iPad as a MIDI controller for Traktor?
Yes. On a Mac, an iPad on a USB cable becomes a standard MIDI device once you enable it in Audio MIDI Setup, so Traktor maps it like any controller; on Windows it needs a small bridge app, the free Interaktiv Bridge. Interaktiv Tap ships that as a finished instrument rather than a blank surface: the app exports its matching .tsi, and the mapping is also in DJ TechTools' database.
#Where's the full list of mappable commands?
On the Traktor command list — every Controller Manager command, by category.
#Why does my controller show stale state after connecting?
Out rows send on change, not on connect. Map Send Monitor State to request Traktor's whole state — and keep the rows that can be live at once under 500, or with Send MIDI Clock on the dump arrives cut. Measured here.
Source: Native Instruments' own Controller Manager documentation is the reference for what each field is called. This guide is how the system behaves once you use it.