Traktor Global MIDI Control: Control Multiple MIDI Devices With One Controller

Traktor Pro 2.8 brought support for the Kontrol D2, as well as several other features. Quietly included in that update were mapping options for “MIDI Controls”, which allows Traktor to read MIDI signals from one device and parse this input as a MIDI signal for another device. Essentially, this feature allows you to control not only Traktor, but also external VSTs, DAWs, and MIDI hardware with one device, and also allows you to integrate those controls with Traktor’s built-in modifiers and environment states. Read more to see how this powerful mapping feature can seamlessly extend your live performance outside the bounds of Traktor.

What do the Global MIDI Controls do?

The core functionality of the ‘MIDI Controls’ is to read the button, fader, or knob states from one MIDI device and pass those states to another MIDI device. Although the feature was designed for the customization of the S8 and D2 “Performance Area” knobs, buttons, and faders, this feature works with any MIDI device.

The MIDI Controls, like many other inputs in Traktor, can be interpreted as special modifiers taken from the state (values) of the controls assigned by the user on the In-Port.

Matching MIDI Control outputs send the corresponding values of the assigned inputs as MIDI signals on the Out-Port. As of Traktor Pro 2.9.0, there are 8 knobs, 8 faders, and 8 buttons which may be assigned per mapping scheme. Like most other Traktor key/MIDI mapping functions, the MIDI Controls can be programmed to interact with modifiers; this allows you to fit these mappings with Traktor-mapped shift buttons or mapping page functionality.

What can Global MIDI Controls be used for?

Unlike most Traktor features which can manipulate audio from a deck or change the basic operation of the software, this addition does not directly affect anything within Traktor. Instead, this feature can be used to extend the functionality of your MIDI controller outside of Traktor’s functionality.

This essentially allows you to control any MIDI-compatible device, software or plugin from a MIDI control surface already connected to Traktor and integrated with the powerful mapping assignment features Traktor offers.

Map your MIDI controller to the TR-8’s effects section – why not?

Many synths, drum machines, sequencers, and other hardware include not only the ability to send MIDI output, but also the ability to be controlled with MIDI input. For example, the Roland TR-8’s internal effects can be controlled with external MIDI control signals.

One long-requested feature for Traktor that has yet to be implemented is the ability to natively use VST plugins. However, in combination with a virtual MIDI port (such as the built in IAC Driver on Mac OS X, or loopmidi for Windows), it is possible to control a VST with the MIDI signals passed by Traktor. This would allow you to use the same controller to control Traktor and your VST plug-ins.

One reason to use Traktor to repeat the signal, rather than duplicating the MIDI input signals with a utility, is to take advantage of Traktor’s modifiers so you can, for example, create a page of VST controls on a MIDI Fighter, create an instant-gratification mapping, or change a control’s functionality with a shift button.

Here’s an example of a “dual mapping” with Traktor and a Maschine Micro with the Maschine VST. The blue Maschine pads are mapped to Traktor cue points, while the orange Maschine pads are mapped using the Global MIDI Controls to the Maschine plugin.

Here is another example, where some previously unused knobs and buttons of a Numark 4TRAK have been assigned to Massive, configured to generate and apply effects to white noise, which can be very useful in your sets. The leftmost button has been assigned to turning the white noise generator on and off, while the four knobs (from left to right) control the white noise amplitude, color, reverb, and master volume.

Another use for the Global MIDI Controls is to control a DAW such as Ableton Live. Using a tool such as Soundflower for Mac or Virtual Audio Cable for Windows, you could route audio to and from Traktor and your preferred DAW, and use the Global MIDI Controls to trigger MIDI loops, VST Effects, and launch samples in a DAW using the same device connected to Traktor. Again, this is powerful as you can use Traktor’s mapping modifier variables alongside the Global MIDI Controls, allowing you to, for example, create a page of Ableton sample triggers for a MIDI Fighter which could also control loop rolls and instant gratification effects in Traktor.

How to map the Global MIDI Controls

In order to use this feature, you will require the following software:

  • Traktor 2.8.0 or newer – The Global MIDI Controls feature was added with 2.8.0 with the launch of the Kontrol D2.
  • Virtual MIDI Ports – If you are passing MIDI signals from Traktor to a DAW or a VST, instead of to an external MIDI device, you may need to create virtual MIDI ports. On Mac OS X, the IAC Driver, already included as part of the operating system, is able to create virtual MIDI buses. On Windows, you’ll need a third-party utility such as loopMIDI to create virtual MIDI buses.

Due to the wide range of possible software and hardware you’ll be able to control, it is very likely you will need to experiment with the note and CC signals Traktor outputs. Here’s a general guide to assigning the Global MIDI Controls:

  1. Create the Virtual MIDI ports. This step is necessary for sending signals to a DAW or a VST. It may not be necessary if you are sending signals to an external MIDI device which already has a MIDI input port that Traktor can send the MIDI signals directly to. Make sure your MIDI port shows up under the devices list in Traktor.
  2. Create a new mapping, or modify your controller’s current mapping. If you are planning to use modifiers to send MIDI signals to another device or software, you will need to modify your controller’s base mapping instead. Set the In-Port to the device you wish to use as the control device, and the Out-Port to ‘All Ports’. It is necessary to send signals to all ports to retain any MIDI-Output functionality of the controller (Such as lighting) but still send the MIDI signals through the virtual MIDI port.
  3. Assign the knob, fader, and button inputs in Traktor. This part is pretty straight forward. Create a new “MIDI Control” assignment for every knob, button, and fader you wish to control another device with. The assignment is found in the “Global” section of the “Add In…” drop-down menu. If you are new to Traktor mapping, it would be handy to refer to this DJ TechTools guide on building a basic MIDI mapping with Traktor.Note that Traktor does not yet have toggle functionality enabled for the button mapping.If you wish to create a toggle, instead of using a Global MIDI Control assignment, you may need to assign toggle buttons to a modifier. The output you send would also need to be based on a modifier output rather than a Global MIDI Control.
  4. Assign the knob, fader, and button outputs in Traktor. You may assign the outputs to any note or CC output. It may be easier to simply assign the output to the same CC or note as the input (by using the mapping “Learn”) Since Traktor is broadcasting the MIDI output on all ports, it is important to make sure the outputs you have assigned do not interfere with any other device. You can test this out by connecting all of your gear to Traktor and checking if using any knobs, faders, or buttons causes peculiar output or behavior on any of your gear.After you have assigned the outputs, you should test the signals with your virtual MIDI port utility. IAC and loopMIDI allow you to see if data is being passed through the virtual MIDI port.
  5. Configure the MIDI-input device and assign the input control in your VST/DAW/MIDI-device. You’ll want whatever device or software you are controlling to read only from your virtual MIDI port, as well as any additional devices that may control it. Most software allows you to map various parameters to any MIDI control specified. Refer to your software’s user guide to figure out how to assign controls. If you have configured the mapping assignments and virtual MIDI ports properly, the MIDI signals should seamlessly pass through the Traktor and MIDI-learning the controls should work the same as natively assigning parameters to any control surface.

Endless Possibilities

Despite being a very unannounced feature, the Traktor Global MIDI Control mapping assignments are potentially one of the most powerful mapping features Traktor has to offer. With the right combination of MIDI mappings and audio routing, the possibilities for integrating Traktor with performance software and devices are endless. This feature could be a game-changer for live Traktor performance.

Experimented with the Global MIDI abilities of Traktor yet? Let us know how it went in the comments – we’re excited to hear what your experiences are. 

global midimidi devicesmidi routingTraktor Tips
Comments (20)
Add Comment
  • Shaun Bruyninckx

    I just discovered this article (how on earth I managed to miss it in the first place is beyond me), and I really like the possibilities.
    Does anybody know how it is possible to use the 4 faders on my D2 (normally reserved for Stem decks) to receive 4 audio tracks, coming from my Maschine Mikro? And If I manage to get this working, I presume I won’t be able to use the Stem decks anymore with these faders? Any help would be greatly appreciated!

  • blacKat

    I just started using the maschine one map with traktor and i really like it. I was wondering if anyone could tell me if i would potentially be able to map mixemergency to run a limited amount of video with traktor. I love traktor, but unfortunately i am required to run video at a majority of my gigs right now.

  • Patrick Wolf

    I did notice this feature and agree that it does offer some potential. However, ignoring the modifiers and multi-function controls, it has always been possible to map individual midi controls to multiple midi sw/hw.

  • calkutta

    word Travis…I would just love the Maschine software integration to run inside traktor…I mean,is that that hard to do?..i understand Maschine made their stuff proprietary..but N.I still owns it.?..If i can use Acid Pro 10 with Maschine and Kontact and Massive at the same time.yes,i know,as VST’s..then its not that complex…I think there is just an error in the code so it wont run in in the early 2000’s sega did so u couldnt copy their games…so what happened?..a 9 yr old in Amsterdam onna Linux machine saw the error,fixed it,and now we can copy all games and DVD’s..maybe a Linux machine is all we need..seriously?…has anyone tried this yet?.if i can get Traktor opened up guts sure i could make this work..Ean did it with the remix decks,and those were “Impossible’ without an F1’…so if Ean can do,it can be Money is onna 11 yr old in Denmark that will crack this…Watch…

  • Travis Baker

    This post is one of those posts that makes you so excited its hard to finish reading the article completely before blindly trying it out without getting through the tutorial. This is why djtechtools is my muse.

    • Travis Baker

      My run on sentence as proof.

  • DJ Sean J

    I’ve been planning to use this for a few months and was hoping nobody else would figure it out quite yet 😉

  • hrmmm

    on the first video, what is that mapping for the F1?

  • Mert

    Already use the S8 Midi Controls for special Ableton effects, but since the Stems are out the way of performance is not so good. The Faders just control the Stems and where is no option to switch between Stem control and Midi Control. Really like the Small Faders, but this is no option for me.

    Btw. I tried Soundflower on my MacBook and get everytime Dropouts!!! I choose Jack OS and created a Automator-Programm-Start-Routine, so its much faster on Live situation to set it all up.

    • Rico Balakit

      Are the Stem controls within the standard mapping implementation like other controls? It could be possible to use modifiers to create a shift button to switch between Stem and MIDI control.

      • Mert

        The Stem controls are a standart implementation. Same thing is happening if u got a RemixSet loaded. The Faders are only in “Midi Mode” if u have a track deck loaded.

    • Arnold

      use the remix decks mapping for sending midi at all your daw ! it’s the better way i found

    • calkutta

      please share…step by step…thats why the djtech community rocks

  • EveryDay

    Hell yeah! Thanks so much for this post, I am very excited to use this feature and must have missed the sneaky update on 2.8.
    makes me think that we’re one big step closer to finally seeing
    Maschine Integration – my guess is that Traktor 3 is only one or two
    more incremental updates away woohoo!

  • orge

    I did notice this feature and agree that it does offer some potential. However, ignoring the modifiers and multi-function controls, it has always been possible to map individual midi controls to multiple midi sw/hw. That means this feature is only relevant for more complex routings/logic.

    Unfortunately, I would anticipate these uses might hit the wall very quickly with only 3 x 8 controls available – in the examples you’ve given, you can’t even map all 16 pads on maschine or a midi fighter. So this would require splitting into further modules and I could see the programming becoming very frustrating/time consuming.

    I think we should be very careful heaping too much praise on native instruments for the “progress” they are currently making with traktors midi mapping. The reality is that the constraints and interface make programming pretty painful beyond the basics. This is yet another kludge, which has only really been added to support their own hardware.

    Consequently, it’s a bit difficult to get excited by this… J

    • orge

      I would add that I do appreciate the constraints from previous decisions/development. However, it just seems like they are building on sand now and should really refactor the main base.

    • Rico Balakit

      Agreed, it seems the 8-fader, 8-knob, and 8-button limit is based directly off it being a feature intended for the D2 and S8. I’d love to see it expanded past this limit. As you said, you could bypass the limit using additional mapping sets, but unless there is a way to ‘transfer’ modifier values across mapping schemes, it would be not much different (if not clunkier, even) than using a utility for sending a single MIDI device’s signals to multiple devices/programs. If you are able to work within these limitations, however, using this method to control other devices or software taking advange Traktor’s mapping logic functions like modifiers and environment states is definitely a cool luxury.

      Halfway into writing this comment, I realize there could be a workaround to the 8-control-limit using modifiers that I’d like to experiment with soon.