Subject: Traktor Pro feature request — timestamped History and Mix Recorder performance logs
Hi Native Instruments / Traktor team,
I posted on X today requesting that the Last Played column display the complete time in hours, minutes and seconds.
I’d like to expand that into a broader feature proposal: a timestamped Performance History linked to each Mix Recorder session.
The use case
As a Traktor user producing long DJ mixes and radio shows, I want to know exactly which tracks were audible, when they entered the mix and when they left.
This would allow DJs to:
- Produce accurate timestamped playlists
- Create podcast, YouTube and radio-show chapters
- Prepare royalty and performance reports
- Archive and search previous sets
- Review transitions and programming decisions
- Use external analysis tools, including AI-assisted mix analysis
- Identify level, EQ, pacing and transition problems without manually reconstructing the complete set
Priority 1: Accurate History timestamps
Please add the following columns to History and Archive playlists:
- Played At: full date and time, including
HH:MM:SS - Session Time: elapsed time from the beginning of the recording
- First Audible: when the track first reached the master output
- Last Audible: when it left the master output
- Audible Duration
- Deck: A, B, C or D
- Source Start Position: where playback began inside the track
- Source End Position: where playback ended
- Overlap Duration: time shared with the outgoing or incoming track
Repeated plays of the same track should be stored as separate chronological events rather than overwriting one “Last Played” value.
For external mixing, audible times could be marked as estimated when Traktor cannot observe the external mixer’s faders.
Priority 2: One-click session export
Please provide a Performance Log Export command with these formats:
- CSV
- JSON
- Plain-text timestamped playlist
- CUE sheet
- HTML
- M3U/M3U8
The minimum useful entry would contain:
- Session-relative start and end time
- Artist
- Track title and remix
- Release and label
- Deck
- Source-track positions
- Play duration
- Original BPM and key
- Actual deck BPM and pitch adjustment
- Stable track ID or file fingerprint
JSON would be particularly valuable because it would allow developers and analysis tools to read the history reliably without scraping Traktor’s interface or reverse-engineering NML files.
Priority 3: Link the history to Mix Recorder
When recording begins, Traktor could create:
- The audio recording
- A matching performance-log file
- A shared session identifier
- Recording start date, time and time zone
- Audio sample rate and format
- Traktor version and mixing mode
For example:
DJ-Cyclic-Show-491.wav
DJ-Cyclic-Show-491.json
DJ-Cyclic-Show-491.cue
DJ-Cyclic-Show-491.txt
All timestamps would then line up exactly with the recorded audio.
The log should be written continuously so that it survives a crash rather than only being finalized when Traktor closes.
Priority 4: Optional transition telemetry
For DJs who enable an advanced logging option, Traktor could record changes to:
- Channel faders and crossfader
- Gain and Auto Gain
- EQ controls
- Filters
- Effects and effect parameters
- Tempo, pitch and Sync state
- Cue points and loops
- Stem volumes and mute states
- Remix Deck and Pattern Player activity
- Master-output levels and clipping warnings
This could be event-based—only recording when a control changes—so the files would remain small.
It would allow post-set tools to identify bass clashes, sudden gain changes, overly long blends, aggressive EQ moves, beat drift and other transition characteristics.
Additional ideas
- A mappable Session Marker command so the DJ can flag a great transition, mistake, crowd reaction or announcement while playing
- A “Copy Timestamped Tracklist” button
- Automatic chapter generation
- Tracklist templates for radio shows and publishing platforms
- A documented, versioned local Performance Log schema
- An optional read-only local API for live track-title displays and broadcast systems
- Privacy controls, with all detailed logging local and opt-in
- An option to hide local file paths while retaining anonymous track identifiers
Minimum viable version
Even the following four additions would solve most of the immediate problem:
- Session-relative
HH:MM:SS start time - End time or audible duration
- Deck identifier
- One-click CSV or JSON export linked to the recording
I would be very happy to provide an example output file, test a beta implementation or explain the mix-analysis workflow in more detail.
Thank you for continuing to develop Traktor.
Best regards,
Russell / DJ Cyclic
