Traktor Pro: installation, audio setup, deck types and routing.

Traktor Pro almost never fails for lack of functions: it fails because something between the computer, audio interface and mixer has been declared incorrectly. Your first hour with the program decides whether everything works later or whether you spend the rest of your gigs hearing tracks through the wrong headphones. This guide covers Installation, Audio setup, Deck types, Advanced routing and Troubleshooting, in that order, because that is the order in which you need to handle them.

Markers, loops and mapping come later; here we just want clean signal, correct outputs and a program that starts the same way today as it does six months from now.

Installation

Traktor Pro is installed and updated through Native Access: sign in, find Traktor Pro in the product list and press Update or Install. Every update leaves a copy of the previous version in the application’s Backup folder, so you can open the old version if the new one causes problems. On first launch, Traktor asks whether you want to import data from an earlier installation: copying is the convenient answer, because it preserves your collection, preferences and mappings without touching the original files.

It is worth knowing where everything lives. The collection is in collection.nml, inside the user’s root directory (Documents, then Native Instruments with the version number), alongside Traktor Settings.tsi, which stores layout and preferences. The same root contains the Backup folder with automatic collection and settings copies, and the Logs folder with the operations record, the first useful thing when something misbehaves. Recordings and samples go in their own folder inside Music. Touch those files only to copy them, never to edit them by hand.

If you come from Traktor 2, the setup wizard decides what to import; if you start from zero, the first run asks for your music path and the folders you want analysed. That is where the next section begins.

Audio setup

In Preferences, the Audio setup page concentrates the three decisions that determine everything else: Audio Device (the external interface or integrated sound card), Sample Rate (44.1 kHz is the standard) and Buffer Size. The official recommendation is to work between 256 and 512 samples and watch calculated latency: about 15 ms to start and between 5 and 10 ms when the computer can handle it. Too low a buffer produces dropouts and artefacts; too high a buffer makes playing feel spongy.

On Windows, change the buffer in the driver’s control panel through the Settings button on the Audio setup page; on macOS, use Traktor’s own latency control. This is also where you decide what happens if the interface disappears: the integrated-sound-card backup option lets the system keep producing sound, and the multiprocessing support box should be disabled if you run another real-time application, such as a second DAW.

If the interface is certified or belongs to Traktor Kontrol, the rest of the route usually configures itself. If it is generic, follow this guide through to the end and declare every output pair manually.

Deck types

Traktor offers four virtual decks, each of which can have a different type. The Track Deck is the equivalent of a turntable or CD player: it plays a conventional track and is where normal mixing happens. The Stem Deck loads stems files and adds volume, filter and FX-send controls for each part while still behaving like a Track Deck. The Remix Deck triggers samples in cells arranged in columns, synchronised to the master clock. And Live Input lets an external signal enter without coming from the collection, useful for microphones or connecting another program.

In practice, all four coexist: you can have two Track Decks mixing, a Remix Deck with the percussion hook and a Live Input waiting for the voice. Loading a stems file automatically switches the deck to Stem Deck, so you do not need to declare anything first. Details of each type, including Remix Decks and the master clock, are in the guide Decks, Remix Decks, FX Units and Sync.

Advanced routing

Routing declares how sound leaves and enters. On the Output Routing page, Mixing Mode defines everything else. With Internal, Traktor mixes in software and you must assign Output Master (what goes to the venue), Output Monitor (what you hear in headphones, which also feeds the preview player) and, if you want a clean track for recording or broadcasting, Output Record. With External, the physical mixer does the mixing: each deck goes through its own output pair (Output Deck A, B, C and D), plus Output Preview and Output FX Return if you use sends.

The Input Routing page completes the picture: Input Deck A/B/C/D for external signals, Input FX Send for return effects and Input Aux, which exists only in Internal mode. There is also a quiet but powerful setting: Swap Channels, which reverses channel pairs in software so you do not need to recable. If you can only connect two outputs at a venue, recabling takes thirty seconds; reassignment takes two clicks.

The correct mixing mode depends on the equipment: an external mixer, an interface with two outputs for master and headphones, or DVS with inputs and outputs per deck. The table above summarises mapping by scenario; for DVS, the complete configuration is in the guide to timecode and synchronisation.

Preparing outputs for the gig

Before the first event, do the full test with the hardware connected. Raise the crossfader and channel faders, check that the master sounds through the correct output, that the monitor responds when you press Cue and that browser preview comes through headphones rather than the venue. Then lower everything and raise it again: it is the only way to discover crossed output pairs calmly rather than in front of the audience.

Remember that configuration as the venue’s profile: the same cabling, channels and mixing mode. If you always use the same interface, spend two minutes checking that audio preferences did not change after an update; Native Access updates the program rather than your output route, and a major update may create a new root directory without migrating something you expected.

Troubleshooting

When there is no sound, follow the chain from top to bottom: does the interface appear in Audio Device? Is Mixing Mode appropriate? Is an output pair assigned in Output Routing? Are the channel fader and crossfader in position? Does the master meter move? That path solves most cases without leaving Preferences.

If sound crackles or cuts out, the usual culprit is the buffer: raise it from 256 to 512 samples and test again. If the controller does not respond, check Controller Manager, that In-Port and Out-Port point to the specific device rather than All, and that no other program has it open. If something behaves strangely after an update, the log in Logs and the previous version’s copy in Backup are your two diagnostic tools. And if a track cannot be found or the browser appears empty, the guide to USB, format and crash errors covers file and disk cases.

Next step

With audio declared and outputs checked, it is time to prepare the music: beatgrids, Flux mode, Loop Recorder, Pattern Player and timecode control in the guide to beatgrids, Flux, Loop Recorder, Pattern Player and DVS.