Traktor hanging on start after sync from Lexicon

Lexicon Bug Reports
1

Apologies if this is being discussed elsewhere. Couldn’t find anything.

I sync from Serato into Lexicon, all works fine. Pulls from internal and an external drive. Tracks play in Lexicon so files are linked OK.

I open Traktor, all works fine.

I close Traktor, sync from Lexicon to Traktor, then re-open Traktor, and it just hangs with the “Loading collection” modal. (I have tried leaving it for a couple hours.)

I have tried ticking to convert smartlists to playlists, and unticking ‘add album art’, thinking it was them, but no change. I have also tried deleting the Traktor folder, recreating by opening Traktor, then (closing Traktor and) syncing from Lexicon - still just hangs.

I’ve a fairly large collection but not crazy, 60K tracks. I have Serato smartlists, happy to delete them. Could happily just sync the track metadata and a handful of playlists if simpler (although appreciate Lexicon usually works flawlessly).

Any recommendations for workarounds or diagnosis? Traktor 4.0.2. Considering install Traktor 3, sync to that, then open Traktor 4 to copy across?

Edit: I installed Traktor 3.11.1, opened it to create the Documents/Native Instruments/Traktor 3.11.1 directory, closed Traktor 3, deleted the Traktor 4 directory in Docs/NI, sync’ed from Lexicon. Lexicon reported progress like usual, asked for a backup filename, but the Traktor 3.11 directory was not touched. How can I point Lexicon to Traktor 3.11.1? How does Lexicon decide which version? I assumed it would check the NI directory, but should I uninstall Traktor 4?

Tried upgrading to Traktor 4.1 and getting the same issue. collection.nml is written to, but Traktor just hangs with “Loading collection”.

I would be happy just to sync the tracks and recreate the playlists if it gets me up and running and is possible. Never had an issue with Lexicon before (last used it when it was called something else).

Thanks

2

Can you upload your collection.nml? Maybe there is something wrong with it. I’ll test it here.
You can upload with this link: http://upload.lexicondj.com

1 Like
3

Thanks very much Christiaan, package 01JCG10FSDWVKA5FZGA127D3AN

Traktor does seem to be thrashing a single core, so might be stuck in a loop.

Very happy to provide whatever to help diagnose. Unfortunately it is 70MB which can’t be ideal for diagnosis!

How does Lexicon decide which version to export to? Can I rename Traktor 4 to try via Traktor 3? Might eliminate quite a few possible explanations? Ignore me if not useful, no reply needed. (Tried removing Traktor 4 and its metadata and Lexicon still didn’t touch the Traktor 3 collection.nml)

4

Lexicon always uses the highest version of Traktor, it gets that info somewhere from the registry so only uninstalling Traktor 4 would work for Lexicon to use Traktor 3.

You can also just delete the collection.nml and Lexicon will ask which other NML you want to use, then you can point it to Traktor 3

1 Like
5

There is something wrong with the NML, it’s a track entry that is causing it. You have to open the NML with a text editor and figure out which of the <ENTRY> tags is doing it. Not sure if you know how XML works but basically delete half the ENTRY’s and start Traktor, see if it works. If Traktor works, you know you’ve deleted the bad ENTRY. Keep doing that until you narrow it down to one ENTRY.

6

Thanks very much. I saw you advise this or making read-only on another thread and tried read-only and deleting the whole directory, but don’t get asked for a new location.

However you gave me an idea. I was assuming a v3 collection would be a slightly different format but realized I can copy collection.nml from the v4 Docs/NI/Traktor folder to v3 manually.

Traktor 3 loads fine with the collection.nml that is making Traktor 4 hang, and from a very brief looks all lines up fine, file locations and smart playlists. So it looks like Traktor 4 has an additional rigidity parsing.

7

I know XML. What sort of thing do you think I should look for? A weird character? The XML, eg, invalid property? Invalid tag nesting? Or something with the tune metadata, eg, out of range bpm value? Or references, eg, membership of a playlist that doesn’t exist?

8

I’ve addressed my issue, thanks to your comments.

As explained, I exported to Traktor 4
I replaced collection.nml in the Traktor 3 directory with the one Lexicon wrote to Traktor 4
I loaded Traktor 3, it opened fine. I closed again, rewriting the collection.nml
I deleted the Traktor 4 collection directory.
I opened Traktor 4 and agreed to it importing from Traktor 3.
Traktor 4 now works fine.

Shall I upload the working collection.nml? I’m thinking you might be able to sort then diff it with the one I uploaded above.

9

Yeah if it is the (almost) same size, then I can diff it.

If the problem happens again, maybe Lexicon is writing some kind of character in the XML that Traktor doesn’t like. Just have to figure that out by process of elimination

10

Gosh just checked, it is 12MB smaller.

Uploaded ID 01JCGC4HN0FKE736FEAS6FSKJH in case it is useful

Enormous thanks for helping me with this within minutes. Really, really appreciate it.

1 Like
11

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.