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

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.

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

Yes I think that's by design. I tried importing a collection.nml exported from Traktor and each time I played a track it reanalysed it.



Remko

MIXO DJ team

When I export a .nml file from MIXO (playlists only) and import it into Traktor, all tracks are re-analyzed, even though those files already exist in my Traktor collection with full metadata.

After analyzing the exported file, I found two key issues:

1. Missing Traktor analysis data
The export only includes <PLAYLISTS>, but Traktor requires <COLLECTION> entries with fields like:
AUDIO_IDTEMPO (BPM, BPM_QUALITY)LOUDNESS (PEAK_DB, PERCEIVED_DB)MUSICAL_KEYCUE_V2 (hotcues)Without this, Traktor will always re-analyze the track from scratch.

2. Incorrect PRIMARYKEY path format
MIXO exports paths like:
D:/Music/Artist - Track.mp3
But Traktor expects:
D:/ :Music/:Artist - Track.mp3 (note the /: for each folder)

* * *


Request:
Please consider adding an option to:

* Export playlists with paths in Traktor's /:folder/:file format
* Optionally include <COLLECTION> entries to retain analysis info
* Or even better: auto-link playlist entries to existing collection tracks via AUDIO_ID or filepath

This would prevent unnecessary re-analysis in Traktor and make MIXO even more powerful for Traktor users.

Let me know if I can help test this!

Ah I see, so when exporting specific playlists, as opposed to the whole library, the bug occurs.



MIXO should export the tracks to the collection tag as well, similar to how it works with Rekordbox XML.



I’ll investigate!



Remko

MIXO DJ team

Well, I couldn't see any issues exporting Traktor NML and selecting specific playlists only (or with Export Everything checked).

Tested on Windows and mac.

The NML contains the <COLLECTION> entries and <PLAYLISTS> entries, all with correct paths, like C:/:Users/:remko/:Desktop/:MIXO-app/:01 17 (Extended Mix).m4a".

Could you please restart MIXO, export again and send me your NML?



Remko

MIXO DJ team

Yes, what email adres i can send, its a large file. Maybe with a cloud or something i can email you.

Just to anon@mixo.dj I would upload the file to your cloud storage and send shared link, or use wesendit.com and use the link option.



Remko

MIXO DJ team

Done, i have send the file and a step by step what i have done. I hope u can fix it.

Good news, I have a fix for missing artwork and waveforms, ready for the next release!

There might be some additional steps involved regarding artwork, but as long as your waveforms exist when you quit TRAKTOR (quitting refreshes the default collection.nml), MIXO will find them and include the AUDIO_ID in the exported NML, so when you 'Import Another Collection' in the next release they should be retained.

The work around for missing artwork will be to delete all your tracks in TRAKTOR, then drag/drop them from your computer/drive which will import the artwork, then 'Import Another Collection' and choose Collection. You can do this in the next release.



Remko

MIXO DJ team

Awesome, i dont need the artwork, its fun i never used it, i delte them mostly.

When is the next release?

@remko When is the next release so i can test if everyting works fine. U can mail me if u want me to test it first.

Emailed you a beta!



Remko

MIXO DJ team

Hi remko, i did not receive anything? Did u send with email?

sorry, i get it. I have the test beta now. My faulth

OMG it was an other wetransfer form a client. I did not receuve anything.

It was in the spam folder pffffffffffff Sorry man for all the fuss but I got it in now. We are going to test it.

Great! Please let me know your feedback.



Remko

MIXO DJ team

Hi, i have done it, but strange. When i scan it says Tracks Missing stripe and totaltracks to analyze is 33174 of the 36338 tracks.

I did restart traktor etc etc.

Now i do this with my whole collction.

I think i gonna build a new (test) plylists and mp3 tracks in a clean envoirement en do it agaian.

I take 100 tracks. make 5 playlists in traktor en then will import and export and see what happen.

I come back to you soon.

If your tracks are analysed in Traktor and you've quit Traktor, MIXO should be able to export the required info to the NML.

However, it's possible the matching logic needs some more work so let me know how it goes!



Remko

MIXO DJ team

Hi there, i test a clean traktor pro 3.11.17
Did a import and a export many times but i have to reanalye everything.
I make a new mp3 folder with 50 tracks for testing, but also i have to reanalyze everything.

@Remko, is there any progress? Still not working.

Are you definitely on the latest beta version I sent you?



Please email me your exported NML from MIXO and also the default collection.nml from the TRAKTOR folder.



You can find this quickly by clicking the folder icon on the Import TRAKTOR page in MIXO.



Remko

MIXO DJ team

Hi here are 3 files.

1 original

1 i have imported and exported

1 i have imported, unduplicate and exported.

Also MICO says it will tag MIXO but i can not see it.

I use Traktpr PRO 3, i know that there is a Traktor Pro 4 and will install if i first re-duplicate my libarary.

I have uploaded to my CHATGPT Traktor Project to analyze and here u will see the reults.

PROMPT: wil je deze eens vergelijken, de exports als ik die inlaad in traktor dan moet hij alle tracks weer opnieuw analyseren

Ik heb de drie NML-bestanden (originele collection.nml, de standaard export en de deduplicatie-export) vergeleken op welke XML-elementen én attributen per track­entry bewaard blijven. Kort samengevat:

* Originele collection.nml bevat naast de basis­velden (LOCATION, ALBUM, TEMPO, MUSICAL_KEY, CUE_V2 enz.) ook:
een LOUDNESS-element met attributen PEAK_DB, PERCEIVED_DB en ANALYZED_DB (de uitkomst van Traktor’s analyse)

* in de <INFO>-tag extra attributen zoals LABEL, COMMENT, FLAGS en REPLAYGAIN_TRACK_GAIN


* Export (zonder deduplicatie) bevat wél LOCATION, ALBUM, INFO, TEMPO, MUSICAL_KEY, CUE_V2 maar geen LOUDNESS en mist velden als LABEL en COMMENT.

* Export_ontdubbel (na dedupliceren) is hetzelfde als de standaard export, met alleen een extra COLOR-attribuut in <INFO>, maar nog steeds zonder LOUDNESS.


Omdat Traktor bij het inlezen van een NML ziet dat de analysegraad (LOUDNESS) ontbreekt, wordt de track opnieuw door de analyzer gehaald. De oplossing is daarom om bij het exporteren ook de <LOUDNESS>-tags (en eventueel andere analyse­velden) mee te nemen. Je kunt je export-script dus aanpassen zodat het deze sectie in de XML behoudt, bijvoorbeeld door bij het kopiëren van <ENTRY>-elementen niet alleen de velden in conf._entries te zetten, maar ook de gehele set kinderen inclusief <LOUDNESS>. Hierdoor ziet Traktor bij import dat de analyse al gedaan is en hoeft hij niet opnieuw te analyseren.

By the way, i have als experimented with https://www.flowrl.com/librarian/ en https://github.com/r0x0r/traktorlibrarian and maybe the Pyton script u can learn from it. Its an ols script but maybe it helps you.

Can we speak ducth in the mail, tht will be better for me :)

Greetings>

@Remko?

Sorry, still investigating.



Remko

MIXO DJ team

I've tested using your data and everything works.

The problem is your exported NML does not contain any AUDIO_ID references.

Either you did not export using the latest beta I sent you, or there's a permission issue where MIXO can't read the collection.nml from the TRAKTOR folder.

Please try installing the beta again, then give MIXO full access to the collection.nml file, or the complete TRAKTOR folder.

Maybe that will solve it!



Remko

MIXO DJ team

Hi Remko, i think i found it.
What i did.
I make a Virtaul clean windows 11
Installed Traktor Pro 4
Tested withe the latest build 1.85.4
I think its working now.

On my other laptop with win dows 10 and traktor pro 3 it wont wrk.

This week i installed Traktor Pro 4 on that ols laptop and see if it works with my total catalogs.

To be contined

Awesome, nice work!! Do you think it was a permissions issue?



Remko

MIXO DJ team

Hi Remko, i have installen version 3 and 4 on a virtual windows 11 machine. 4 is working, but 3 is not good, it wont work.

Ahh I see so it’s a Traktor version compatibility issue. I’ll have to check what’s available in version 3.



Although if the collection.nml you sent me was from version 3, it all worked absolutely fine for me. In which case it’s a permissions issue.



Remko

MIXO DJ team

MIXO v1.86 is now live with a heap of improvements!

https://www.mixo.dj/versions?v1.86

Thanks for the epic ideas and feedback :)



Remko

MIXO DJ team

Still the same problem. Import TRaktor, Export NML file. Then import into Traktor again and boom not working.

Do you first clear the original collection in Traktor?
Do you select import the original collection.nml or an copy of that in an other folder?

Maybe make a video with the whol proces, so we can learn from it.

Hi Alex,

Remember, it worked fine for me using your collection.nml, which means it's not a MIXO issue, it will be a permission issue probably.

Here's a video again showing that it works, this time using my own data: https://take.ms/BoSg1

The problem is probably still that MIXO cannot read the collection.nml that is automatically generated by Traktor.

Did you check the permissions?

You cloud try right-clicking MIXO.exe and run as administrator.

Additionally, give MIXO access to the Traktor folder:

1. Right-click the folder Native Instruments folder:

2. Go to Properties > Security > Edit.

3. Click Add and enter the app’s user account (or Everyone, though this is insecure).

4. Grant Full control permissions.

Also, Windows Defender or other antivirus software might still restrict access regardless of app permissions so please check that MIXO is whitelisted.



Remko

MIXO DJ team

No the problem is that my tracks are on my external ssd G: its a copy of my dj laptop where my tracks are stored on d: so when i import xml it says the tracks are not imported.

No the problem is that my tracks are on my external ssd G: its a copy of my dj laptop where my tracks are stored on d: so when i import xml it says the tracks are not imported.

o in the nml and mr3 and xml it reference to d: but the tracks are on G:

i only enat my playlists not more from Traktor to Rekordbox.

In that case, once you've imported into MIXO, you could use the Find & Replace Tool to fix your paths, or use Relocate Tracks.

If you use the Find & Replace tool, make sure you uncheck everything except "FilePath", then use partial match, match "D:" replace "G:".

yes i think that works.

i will let u know.