WinShow.

Installing the Traktor probe on the DJ’s machine

A small installer, run once, removed the same way. It touches neither the audio, nor the library, nor the mappings.

  1. 01Note the WinShow machine’s addressOn the booth machine, note its IP address on the network joining the two machines. That is what the probe will aim at.
  2. 02Declare a Kontrol D2 controller in TraktorOn the DJ’s machine: Preferences → Controller Manager → Add… → Traktor → Kontrol D2. No hardware is needed — the controller is virtual, and it is what makes the screen the probe uses exist.
  3. 03Run the patcherIt detects the Traktor installation and its version, backs up the original files into a timestamped archive, then installs the probe. The operation is idempotent: a machine already patched is not patched twice.
  4. 04Accept the Windows elevation promptTraktor installs into Program Files, which cannot be modified without elevation. Unlike the booth machine — installed per user precisely to avoid this — this patcher cannot do without it.
  5. 05Enter the booth addressIt is stored in a separate file, so that re-patching after a Traktor update does not lose it.
  6. 06Check the reportThe patcher says what it did: "Traktor 4.5.1 patched — pushing to 192.168.1.50". Without that report, nobody knows whether it worked before the first track.
  7. 07Open the firewall on the booth sideThe WinShow machine must accept the probe’s inbound connection. The installer adds the rule; if the network is on the Public profile, check that it is active there.

What the probe does not change for the DJ: their interface, their mappings, their audio, their library. It runs on Traktor’s interface thread, never on the audio thread.

What to tell them anyway:

  • A Kontrol D2 appears in their controller list. Harmless, but visible — and they will find it again if they export their TSI.
  • If they own a real D2, we touch the file that drives its screen. Plan for it.
  • A Traktor update erases the probe. Nothing breaks on their side; it is we who stop receiving, and it is on us to notice.

To remove the probe, the same binary carries a Remove mode: it restores the backup and says so.

The patcher, report after installing