I have tried to export my library from Serato and onto Rekordbox 7. I used the unofficial method in Lexicon to do so. I can see that when I look at my library, the waveforms and hot cues are visible in the preview, so I assume that went correctly.
However, I keep getting a ‘load error the file could not be found’ each time I try to load a track. I have tried to update the following settings and none have worked so far
- Updated xml file location to USB
- Changed the auto relocate the auto search files to include the USB
- Moved the master database to the USB
I’m still getting the same error and have run out of suggestions of what to do next on Google, does anyone have any advice on how to resolve? Thanks!
You don’t need to change any of those settings normally.
Is your Rekordbox database on the E:
drive? If not, best to put it back to the original there. You don’t want it on the USB.
After that, try a Full Sync to Rekordbox again and see if the tracks load. If not, check what the location on a track is in Rekordbox and compare that to the same track in Lexicon. If the track does play in Lexicon, there must be a difference in location.
Hi Christiaan, I just tried the full sync again and it has found the files and can be played in Rekordbox 
However it now hasn’t analysed the tracks, and I have huge library so it takes about 24 hours to do that from the beginning. Is there a way to avoid having to reanalyse all the tracks? I can do it again, but it’s not ideal (have to use someone else’s PC, as it crashes my laptop)
Lastly, do you mind confirming the default location for the rekordbox.xml file, I changed the other settings except for that one and can’t find it on Google.
Thanks for your support, the support and forum are a great part of the Lexicon product!
Lexicon changes the xml path automatically so you don’t need to worry about it. You don’t use it anyway unless you are using RB XML files.
Normally re-analyse is not needed but maybe the first time it is. You can try by analysing a few tracks and then full sync again.
If analyse crashes your laptop, try changing the setting to Power Saving: