There are two primary types of computer DJs: those who use Serato and those who use Traktor. MIDI stands for Musical Instrument Digital Interface and it is a powerful tool that DJs should be acquainted with. By decoding the MIDI data that a DJ controller sends, a DJ can increase the capabilities of his device and personalize his gear to his workflow. This article will be an introduction to understanding MIDI and how to get started with MIDI programming in Traktor. While this article will be tailored to Traktor, the knowledge can be transferred over to Virtual DJ, djay Pro, and other MIDI-compatible DJ programs.

What is MIDI?

Controllers that are used with DJ software send MIDI data which is viewed as notes by the software. These notes range from 1 to 127 channels and contain different musical notes with each channel. A DJ won’t need to know the programming and distinction between each different MIDI note at this stage. What is important to understand is that (in most cases) every button, knob, platter, and other control of a device sends a different MIDI note. In order to understand what each control can do, we will use Traktor to decode the mapping of our controller.

Reading MIDI Mappings

The file that stores all the instructions for Traktor is commonly referred to as a MIDI mapping file. This mapping is what lets Traktor know what to do when each button is pressed and knob is turned. First, let’s take a look at the organization of a MIDI mapping file.

To open a MIDI mapping file in Traktor: click the gear icon > click Controller Manager > select your device from the first drop down menu to open the mapping file. If you haven't attached a separate controller, the default will be your keyboard. Below, each MIDI note will be displayed.

Control: This category lets the DJ know what a button specifically does within Traktor. These usually are self-explanatory however some may need more explanation. All the different types of controls can be found in the Traktor manual.

I/O: In means that the control is activated when the button or knob on the controller is turned on. Out indicates the Traktor is sending data to the controller which is usually the LED color or pattern for a button. (Great for color synchronization.)

Assignment: This section lets the DJ know what portion of the software is being controlled. This will read as Deck A-D, FX Unit 1-4, Remix Deck, Global, and Device Target.

Mode: Mode lets the DJ know how to interact with a button. Toggle means the button works like an on/off switch. Hold means the button has to be held down to be activated. This also indicates whether a button increases or decreases an effect. (Loops, FX, etc.)

Mapped To: This is the distinction of which button the control is mapped to. A DJ doesn’t need to know the exact MIDI note a button is assigned to. Traktor makes it easy to map buttons and we will go over that below.

Condition 1 & 2: Condition 1 & 2 let the DJ know if there are any modifiers attached to the control. Modifiers allow for the DJ to get super crazy with mappings and have one knob or button perform more than one function. Since we are just getting our feet wet, we’ll hold off on modifiers for now.

Comment: This is a great tool that every DJ who MIDI maps should use. Comment is where notes can be stored about each control. After getting a handful of buttons mapped, the comment section will come in handy to distinguish between similarly mapped buttons. (See above how I have different controls with similar names and no comments. This can easily become confusing and convoluted.)

Now, let’s read the first line and figure out what that button does!

Button 2 is controlling the second effect in FX Unit 1. When the button is pressed the effect is turned on and pressing the button again will turn the effect off. (Toggle)

Mapping a Button

Now that we can read a MIDI mapping let’s map our own controller. This is the second step into creating a more personalized controller and mastering the tools of the trade.

Begin by pressing Add In. Then find a control in the drop down menu. Let the imagination run wild! The button that is mapped can be used for an effect, filter, cue, loop, and pretty much anything else inside the software.

Next, press Learn and then a button on the controller so Traktor can determine which MIDI note to map. This makes mapping super easy and a DJ won’t need to worry about knowing each MIDI note. Be sure to click Learn again so Traktor isn’t waiting for another button to be pressed.

Commenting what each button does is a great practice to get into and will help with navigating through a controllers mapping.

Interaction mode is where buttons can be turned into toggle or hold control, and knobs can be turned into direct or relative. Toggles are great for effects and holds are typically used for cue points. Knobs are generally always direct.

Finally, let Traktor know which Deck or FX Unit should be controlled in the Assignment section. A specific location can be specified or the button can be left on Device Target. Device target means that whatever deck is activated will be affected by that button. Personally, I never use this because I want to make sure that I know what the button will affect when I press it.

Map the Uncharted Territories of a DJ Controller

And that’s it! By following the instructions above a DJ can map their own controller to fit the way they play. This guide didn’t touch on every way to map a controller purely because there is so much to learn! However, with the knowledge provided, a DJ can map his own controller using Traktor. If there is anything that seems confusing or mysterious, be sure to utilize the Traktor manual and also reach out to me on Twitter. Mapping controllers can be as difficult as mastering the 1s and 2s but the skill set is priceless.

Dean William will field any questions that you have about Traktor, MIDI mapping, and controller customization. He's on Twitter: @deanithon.