Controller-Mapping in Traktor 1.2

Logical and Physical Controllers

With Traktor 1.2 the architecture of the controller mappings has completely been reworked. This tutorial describes the new architecture, it explains the differences between a logical controller and a physical controller and it shows which device classes are available when you create a new logical controller.


In Traktor 1.2 a mapping is no longer created for a particular physical device, but for a logical device/a logical controller instead.

A logical controller has several specific characteristics and properties:

The following figure illustrates the new architecture of the Controller-Manager by using some examples. The box on the left side symbolises the controller manager that currently manages five logical controllers and their mappings.


The two top most logical controllers are of type Keyboard. For example, one controller could hold the keyboard mapping Perform and the other one the mapping Preparation. The In-Port Keyboard been assigned to the controller that holds the mapping Perform, i.e. only this key-board mapping is active. To switch from keyboard mapping Perform to mapping Preparation, the only thing you need to do is deactivate the In-Port Keyboard for mapping Perform and to activate the In-Port for mapping Preparation.

The logical controller in the middle contains a MIDI mapping for a Korg nanoPAD. Here no MIDI In-Port is assigned; i.e. this mapping is currently inactive.

The two logical controllers at the bottom each contain one HID mapping for a Pioneer CDJ-400. The commands used in both mappings are identical. Each of the two logical controllers is via the In-/Out-Port assignment connected to a different physical CDJ. The first CDJ-400 controls Traktor deck A and the second controls Traktor deck B.