Not really sure where this problem lies. MyTags are sent to RB and they work there but for some reason they don’t work on the XDJ. I don’t think that is caused by Lexicon.
You can try re-arranging the tag categories in Lexicon just to see if Genre is the problem or just the 4th category. I suspect it is the latter.
No updates from me. I’m still experiencing the issue. I tried reformatting my USB and resyncing it from Rekordbox, but it didn’t help anything. I also tried editing tag names and category names, but saw no changes. don’t think it’s a Rekordbox issue because it never popped up until I synced from lexicon recently.
Really a bummer because I use tabs heavily when I dj & my workflow is pretty reliant on them. Frustrating to spend a bunch of time editing tags and then not being able to make use of them in the way I need. Definitely hoping @Christiaan can figure out what’s going on here.
@quantreau have you tried creating a new category in Lexicon (with a new unique name not used before just to be sure), moving all of the Genre tags to that new category, and deleting the old category? Tedious but it may clear out whatever issue there is with the category data itself…
Is there a way to un-do the lexicon sync and fix this issue ? This is a huge problem for anyone trying to dj and use the full function of the cdj/Xdj as intended.
Or is it at all possible to select which three tag groups will show up ? I can get by with three for the time being while a solution is created. Thanks.
You can try putting all your tags into 3 categories in Lexicon and delete the other categories. Then Sync and Lexicon should create an empty unused category in RB. But I don’t know what causes the XDJ to ignore one of them or which one. Might be the last category
Update: I manually dragged my 4th tag group to the top of the tag lists on rekordbox, synced my USB, and now the tags are showing up on my cdj/Xdj. The order is not the same as in rekordbox but all 4 category’s now appear and all my tags are there. Hopefully this helps as the dev team finds a solution to avoid this issue again. Have not tried syncing back to lexicon yet.
