What Interaktiv Tap plays in Traktor
Interaktiv Tap plays Traktor Pro 3 or 4 over USB MIDI. This page is the audit of that: exactly which of Traktor's Controller Manager commands the iPad plays, which stay in Traktor, and why — stamped with the app and mapping version it is true for, and generated from the mapping itself so it cannot drift. The rows, all of them with ours marked, are on the Traktor command list; how mapping works at all is the Traktor MIDI mapping guide.
As of Interaktiv Tap 1.3, mapping 15.12.0: 215 of Traktor's 524 Controller Manager commands are played from the iPad — 41%, in 9 of Controller Manager's 14 sections.
#Played from the iPad, by section
Played is what the iPad drives; the total is every command Controller Manager offers in that section. Every played command is named here — a chip opens that command on the reference, where its direction, kind and values are. A chip with a number stands for a numbered family, like the 64 Remix cell triggers.
#Untouched from the iPad
5 sections have no row on the iPad at all — 94 commands: Browser (59) · Pattern Player (21) · Layout (5) · Preview Player (5) · Audio Recorder (4). Why each stays in Traktor is below.
#Why those stay in Traktor
Browser is the one we call unfinished rather than deliberate. Browsing is the last thing that still forces a hand onto the laptop mid-set, and it is the next family we intend to map. MIDI can only navigate the browser — Traktor has no channel that sends track names back to a controller — so the design will be hands on the iPad, eyes on the laptop screen, the way hardware browse encoders work. The Preview Player goes with it: it is the browser's pre-listen.
Layout stays in Traktor by choice: switching layouts is work you do with the track stopped, and an instrument you play is the wrong place for it. The Audio Recorder is one action at the top of the night — arm it and forget it — so it has simply not been done, and probably will not be. Pattern Player is a different case: it is built for playing live, but only one sample sounds at a time, and putting sixteen steps and a kit selector on the surface would cost a lot of room for that. A Remix deck does the same job with four slots instead of one, and the iPad plays those in full.
Modifier is not a function at all: the eight modifiers are variables a mapping keeps for its own conditions. The iPad's mapping needs none — its conditions are Traktor's own state.
Inside the sections the iPad does play, the gap between played and total is what the surface has no control for today. Every row is on the command list; the ones marked iPad are the ones you can touch.
#FAQ
#Is the mapping two-way?
Yes. Most commands are mapped In and Out, so the iPad reflects Traktor's state — move a fader or trigger a cue in Traktor and the iPad follows. The command list marks each row's direction.
#Do I have to build this mapping myself?
No. Interaktiv Tap exports its finished .tsi from Settings; import it once into Traktor's Controller Manager and every command counted here is wired. The steps are in how Traktor MIDI mapping works.
#Does it work with Traktor Pro 3?
Yes — Interaktiv Tap plays Traktor Pro 3 and Traktor Pro 4. This list is maintained against Traktor Pro 4.
#What stays in Traktor?
Browsing and loading tracks, the Preview Player, layouts, the Pattern Player, the Audio Recorder and the mapping modifiers — the untouched sections above count them, and the section beneath says why. The iPad plays what is loaded; the library stays on the laptop.
New here? Read our manual, or see what Interaktiv Tap does. Traktor's own commands are described in Native Instruments' Controller Manager manual.
Every figure here is generated from the shipping mapping on each app build, and published as JSON — the counts, every played and unplayed command by section, and the live-row figures behind Send Monitor State. An assistant can read it through our MCP server.
Scan with your iPad
See what Interaktiv Tap does →