Loading Incorrect Serato Cue Points

Lexicon version: 1.7.5
Operating system (remove one): MacOS 14.1

Bug description:
I’m having a weird issue syncing my Serato to Rekordbox that seems to occur on a small # of the mp3s. For the most part, my cue points are coming over from Serato to Rekordbox no problem. However, I have a few that seem to have different sets of cue points in them.

For example, I open the file in Serato and I get this:

However, when I view it in Lexicon, it looks like this:

and it also looks like this in Rekordbox:

and this in Mixed in Key (which is where I think they came from originally, just looking at where it put them):

(Note that the cue point names are not the same as in Serato, and the locations are more based on energy)

I’ve tried to clear them out in Mixed in Key, Rekordbox, etc., but the incorrect one keeps coming over, which leads me to think that the mp3 meta data itself has two forms of the cue points (?).
I’ve seen this on other files randomly as well (it’s a minor subset of files, but enough to be worrisome), so not sure how to even identify these.

How do I go about resolving this? Ideally it’d be nice if Lexicon prioritized the Serato cue point info instead of this other kind when doing the “Import tracks & playlists” from Serato into Lexicon.

I can send over the actual file directly to you if needed.

Thank you,

-Eric

I suspect this is the problem that MIK sometimes creates where it breaks the ID3 tags and sets a second set of cues on your tracks. Lexicon doesn’t know which set of cues to read and sometimes picks the wrong ones.

You can check with kid3, it will probably show the track as red which means it is technically broken (though often that does not matter). It might have double ID3 entries.

Thanks for the quick reply, this is VERY helpful. I did download the Kid3 Tag Editor and you are correct - I do have duplicate tags on some of the files:

I’ve deleted some as a test and reimported, as it is now picking up the proper points so I’ll go through the whole library - this is a huge sigh of relief!

One possible suggestion, at least in how it is listing the properties, it looks like Serato always uses the first set of marker tags, whereas Lexicon uses the secondary/duplicate set? If that’s the case, may be possible on your end to read that first set to help bulletproof this for users who aren’t as savvy?

Either way, I have a fix for my stuff – MUCH appreciated for the quick response as this was really driving my nuts yesterday trying to figure out what the deal was.

Keep up the great work, love the product – really helps DJs like myself who plays on both Serato and CDJ3000s.

1 Like

Nice! :slight_smile:
I will look into taking the first set of cues, hopefully that will work, if Serato always uses the first set too then I suppose even when broken, no one will notice

@airbalz Can you send me that track in your screenshot? With double ID3 tags, if you still have it? Will help with my testing

You can upload with this link: http://upload.lexicondj.com

Christiann,

I had a backup of everything, so went through and found 3 different types of duplicate markers and uploaded them to your link (package ID 01JC190ATPQH7AZDVT3SS711TN).

Please let me know if I can help in any other way!

-Eric

Perfect thanks!

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