Ooops! Native dun goofed! Those of you signed up to the Traktor mailing list will have seen the urgent email sent out advising everyone to upgrade from the last version of the DJ software, v2.6.6, to a critical hotfix, v2.6.7. For many of us, we’ve spent years refining and designing our playlists, but it seems that there’s a critical flaw in Traktor Pro 2.6.6 which can corrupt your collection.
The short but vital changelog is to the point…
What’s new:
- Fixed an issue in version 2.6.6 that corrupts playlists containing Remix Sets or tracks when these are relocated
- Fixed a bug in the search function that returns additional results not matching the query
- Fix required the full deactivation of Metadata Sync with TRAKTOR DJ for this version
Please note:
- We strongly recommend 2.6.6 users to update to this version to avoid potential data loss.
- Version 2.6.6 has been withdrawn from Service Center and the Update Manager.
- If you had 2.6.6 installed and update to 2.6.7, Traktor will copy & import the last Traktor folder (i.e. 2.6.6), so after installation please ensure you import your last working collection file manually (the procedure for which is outlined in the manual).
You can read more in the NI Knowledgebase, including how to rescue your collection should you have fallen victim to the bug. The take-away from this is if you’re running 2.6.6, you need to UPDATE… RIGHT NOW!
Yeh, when I updated it forgot the root path for all the files, had to import previous collection. Luckily I did lose anything
I had the same thing last time I upgraded over xmas. Its forgotten them all again now. I don’t use Traktor often enough to know how to fix anything lol. Doing my head in. I’ve hundreds of songs I swear I had all with que points that I did years ago that have gone too *sighs*
Nothing wrong with syncing. The art of mixing died with dvs! Not that I use it..well, only for remix decks
“Nothing wrong with syncing”
Guess you no dj then, just a guy with alot of mp3z
I stopped updating since 2.6 which is stable and plenty enough for me! Avoided this bug and more to come lol
it’s only really affecting those with iPads …(big smiles :) )
I find it amazing that the Traktor community isn’t freaking out about an approved version of Traktor causing data loss. Has this happened before?