Traktor Export with Gold Import have to analyze bug
I bought the Gold version because I wanted to test if I could clean up my Traktor library and mp3 folders with 38,000 tracks. The deduplication finds 400 tracks. I deduplicated them with mixo and did the export in Mixo. With lock and under lock but both don't work well in traktor when I import them because......I have to have everything reanalyzed by Traktor and that takes a lot of time.
Why? If I export from Mixo and then re-import in Traktor pro it should work.
Other question is when I scan my mp3 folder with Dupeguru it does find 1800 duplicate files when I scan by filename or tag, so how is that possible? So Mixo doesn't look at the file but what it sees in the NML ffile, but so that's not useful.
What is handy is that you can now choose that the deduplicated tracks go to the recycle bin!
I use traktor pro 3.11.17
The same question 
Hi Alex,
MIXO’s Duplicate Finder Tool compared title, artist and duration to determine duplicates, not just the file name. It’s actually better than a straight comparison of file names. You can run it a few times and sometimes it might find a few more because of the a/b matching logic.
Regarding Traktor analysis, you shouldn’t have to reanalyse the tracks, especially if they already exist and you’re reimporting them. I’ll have to check that.
When importing the NML do you select Collection as opposed to File?
Remko
MIXO DJ team
Hi Alex,
MIXO’s Duplicate Finder Tool compared title, artist and duration to determine duplicates, not just the file name. It’s actually better than a straight comparison of file names. You can run it a few times and sometimes it might find a few more because of the a/b matching logic.
Regarding Traktor analysis, you shouldn’t have to reanalyse the tracks, especially if they already exist and you’re reimporting them. I’ll have to check that.
When importing the NML do you select Collection as opposed to File?
Remko
MIXO DJ team
Yes, i have to choose track or Collection, i choose collection. The duplicate tool is awesome because it merges the playlists. But if i can not export it to traktor with a correct import then its for me not working. 40k scanning tracks is not recommered.
off topic. I did my collection scan with the tool One Scanner so allmost all my tracks are with the right tags in it. I did not change the file name.
Please let us make this awesome together, ask me what u want to make this happen.
Greets fom the NEtherlands. I speak dutch.
Yes, i have to choose track or Collection, i choose collection. The duplicate tool is awesome because it merges the playlists. But if i can not export it to traktor with a correct import then its for me not working. 40k scanning tracks is not recommered.
off topic. I did my collection scan with the tool One Scanner so allmost all my tracks are with the right tags in it. I did not change the file name.
Please let us make this awesome together, ask me what u want to make this happen.
Greets fom the NEtherlands. I speak dutch.
Just double checked and I'm not seeing analysis happening when importing another collection into Traktor.
The only time analysis occurs is when you load a track into the deck, which is normal since the NML does not contain waveform data.
Remko
MIXO DJ team
Just double checked and I'm not seeing analysis happening when importing another collection into Traktor.
The only time analysis occurs is when you load a track into the deck, which is normal since the NML does not contain waveform data.
Remko
MIXO DJ team
Hi Remko,
I think you didn’t fully understand my issue. I have a complete collection in Traktor, and everything has already been analyzed. When I import that collection into MIXO, run the deduplication, and then export it again as a new .nml file, I expect that only the duplicates are removed, while the rest of the collection remains intact.
However, when I re-import this exported .nml file into Traktor, the tracks are indeed all present — but all the analysis is gone. Traktor forces me to reanalyze everything, which takes a lot of time.
This tells me that MIXO is not retaining the analysis data when exporting the .nml. But shouldn't the analysis be preserved in the NML file itself?
It would make sense that if a track was already analyzed and has not changed, Traktor wouldn't need to analyze it again. But that’s not what’s happening.
Can you confirm whether MIXO strips this analysis data from the export, or is this a bug?
Best regards,
Alex De Neus
Hi Remko,
I think you didn’t fully understand my issue. I have a complete collection in Traktor, and everything has already been analyzed. When I import that collection into MIXO, run the deduplication, and then export it again as a new .nml file, I expect that only the duplicates are removed, while the rest of the collection remains intact.
However, when I re-import this exported .nml file into Traktor, the tracks are indeed all present — but all the analysis is gone. Traktor forces me to reanalyze everything, which takes a lot of time.
This tells me that MIXO is not retaining the analysis data when exporting the .nml. But shouldn't the analysis be preserved in the NML file itself?
It would make sense that if a track was already analyzed and has not changed, Traktor wouldn't need to analyze it again. But that’s not what’s happening.
Can you confirm whether MIXO strips this analysis data from the export, or is this a bug?
Best regards,
Alex De Neus
Replies have been locked on this page!