Traffic Light / Matching column not working in browser after migration (but works on tracks loaded to decks)
Hi,
I’ve migrated my library to a new laptop using the official Rekordbox migration tool, and I’m seeing an issue with the traffic light system in the browser view.
When I load a track into a deck, the Traffic Light feature works correctly — harmonically compatible tracks are highlighted as expected. So key analysis is clearly present and functioning.
However, in the library/browser view, the Matching/Traffic Light column does not show any harmonic matches at all. It’s essentially inactive outside of the decks.
All tracks have analysed key values and phrasing, Key Display Information is set to alphanumeric (also doesn't work when set to classic), Traffic light is set to Related Key 3, and this behaviour is consistent across both RB6 and RB7.
Because deck-based matching works, it seems like the harmonic data is intact, but the browser-level matching (traffic light column) isn’t querying it properly after migration.
Has anyone else experienced this? Is there a way to force Rekordbox to rebuild whatever index the browser Matching column relies on?
Thanks.
Can't find help? Search our Support Site or alternatively, reach out to our Support agents
Can you please file an inquiry ticket here and our support team will gather some additional information to assist you in resolving this issue.
1 comment