Very Work in progress Traktor S5 mapping for the Mixxx DJ software in TypeScript.

• ✅ Reverse engineered core Traktor S5 HID mapping
• ✅ TypeScript/Vite build and Vitest regression suite
• ✅ Stable component rebinding for deck switching and shift propagation

• Mixer controls (channel faders, EQ, filter, cue, FX assign, crossfader)
• Mixer VU meters
• FX Unit
• Deck switch button with deck-local rebinding
• Shift layer for play, cue, sync, pads, loop encoder and touch strip
• Play button
• Cue button
• Sync button
• Loop encoder
• Hotcue pads
• Browser encoder / back button basics
• Touch strip seek/scratch handling with LED output
• Flux button basic slip/loop interaction
• Display-area transport/browser-related buttons
• LED output for transport, pads, touch strip and mixer

• Freeze mode behavior
• Remix mode behavior
• Display rendering
• Browser/preview behavior that depends on Mixxx GUI focus
• Remaining S5-specific workflow details from the original hardware manual

1. Install the Mixxx software
2. Clone the repository: git clone [email protected]:Serveny/mixxx-traktor-s5-mapping.git
3. Open repository directory and install dev dependencies: npm install
4. Check that the Mixxx type-definition paths referenced in tsconfig.json exist on your machine, or adjust them to your local Mixxx checkout / installation
5. Point attic/mappings/controllers/ at your Mixxx controllers directory, for example: ln -s "/home/[username]/.mixxx/controllers" "attic/mappings/controllers"
6. Run npm run build for a one-off build or npm run dev for watch mode. The generated dist/Traktor-Kontrol-S5.js is copied to attic/mappings/controllers/ after a successful Vite build
7. Start Mixxx in debug mode. On Linux the package script is npm run start, which expands to ../mixxx/build/mixxx --controller-debug --developer

• npm run test:run: Runs the automated Vitest suite.
• npm run test:mixxx-smoke: Starts Mixxx with isolated settings/resources and checks for controller warnings or script errors.
• node tests/scenarios/run-visible-dj-set.mjs: Prints the visible DJ-set validation flow and warns if required audio files are missing.

The automated suite currently focuses on:

• component rebinding and shift propagation
• deck-switch regression coverage
• HID input regressions for deck/shift/touch-strip/play flows
• mixer LED and volume-meter output behavior
• transport, loop, pad and LED behavior
• audio preflight handling for scenario tests
• a manual-derived coverage matrix under tests/spec/

The DJ-set scenario uses tests/assets/tracks-manifest.json as its track list. If required files are missing, the scenario reports a warning and either degrades to control-only checks or blocks execution.

Reverse engineered HID mapping. Some bits/byte in the reports are empty between (or I didn't find out the usage).

• Used for button and knob touch data
• Size: 30 byte (240 bit)

• Used for fader data
• Size: 79 byte (632 bit)
• 38 Values of 16 bit (here 0-4095)
• 1 Number is 2 bytes (1. byte = substep (0-255), 2. byte = step (0-15))

• Used to control the LED's of the left and right fx units, decks, transport buttons and touch bar
• Size: 104 byte (832 bit)
• Report-ID 128 for left side
• Report-ID 129 for right side

Byte 0-23: 8 Pad-Buttons RGB of 3 byte

Brightness/color value from 0 to 127

Pad buttons color: Byte 1 (0-127): red Byte 2 (0-127): green Byte 3 (0-127): blue

Touch strip phase LEDS: 25 bit for blue, then 25 bit for red

• Used to control the LEDS of the mixer
• Size: 73 byte (584 bit)

• prop. Bulk/Isochronous endpoint
• layout with QML