Official comment
Yes, we're aware, but the fix wasn't ready for 5.7.0.
With the release of Rekordbox 5.6.1 a nasty bug was introduced in Rekordbox, this bug remains in a slightly different form in Rekordbox 5.7.0:
If a track is already part of the Rekordbox collection, meaning the file path to the track's media file is already in the Rekordbox collection, Rekordbox 5.6.1 will NOT import any DJ metadata from the XML such as cues, loops, grid, comments, and possibly much more. It's like the track is locked in the collection while it's not.
I've received official acknowledgement about this bug from the Rekordbox engineering team. They were able to replicate the issue and are working on a fix as we speak.
If a track is NOT part of the Rekordbox collection all metadata is imported as before. And Rekordbox 5.6.1 is much faster at importing the tracks than it ever was. Improving the import speed of the XML has been part of my Rekordbox feature request list for a long time. Most likely implementing the speed boast did trigger the bug.
I've made a video that will show the bug using only Rekordbox and a text editor. That video also shows how to implement my preferred solution to avoid the bug. Watch it at: https://youtu.be/Ez8wgVNSXM0
This bug has serious consequences for the users of the Rekordbox Cue and Key Tool - Reck and DJ Conversion Utility - DJCU or for those who rely on other conversion apps.
right now there are 2 options to avoid the XML import bug:
Delete the track from the Rekordbox collection before importing it from the XML.
It works but besides it's a hassle it got user error written allover it.
Use Rekordbox 5.6.0 to import XML data in the Rekordbox database until Pioneer DJ has fixed this bug
How to use 2 versions of Rekordbox on the same computer:
Some words of caution if you want to use this workflow
The ATGR apps that rely on XML import have a warning system in place
These apps will warn you the moment a bugged version of Rekordbox is detected.
The apps will even warn if Rekordbox 5.6.0 is installed alongside the bugged Rekordbox version as a reminder you can only import XML meta data reliable using a certain procedure.

Rekordbox 5.7.0
If using the left click->"Import Playlists" is used in Rekordbox 5.7.0 the bug will still be active (no XML metadata is imported)
however, the Playlists will be imported correctly.

While in the same XML if all tracks contained in the tab "All Tracks" are selected and left click->"Import To Collection" is invoked the XML metadata is imported. But this import does not import any playlist information. The tracks are just imported into the Rekordbox collection without their associated playlists.

These 2 "imports" can be combined in the same XML to get both the Metadata and Playlists over to the Rekordbox collection.
The 5.6.0 import method remains my preferred option to avoid the XML bug because it's proven reliability.
Yes, we're aware, but the fix wasn't ready for 5.7.0.
Post is closed for comments.
Thanks for mentioning those apps never knew they existed! Bookmarked for when I have the need to convert things.
I have run into the same issue and a "reverse" issue related to xml import regarding Beatport streaming tracks.
For some (strange) reason Beatport decided that you cant add Beatport tracks to your Playlists in rekordbox (great decision .... how do we prepare streaming tracks for our sets now) ?
They want you to use Beatport Link playlists I guess.
I figured out that XML import is a way around this (see my other post) ...
But you cant add a "release date" to the XML and when you import the beatport tracks in your collection via this method - the release date field remains empty - even though it is not set in the XML.
ps your post title mentions 5.7.1 but I can only see 5.7.0 in mine. Is that a beta?
Has anyone at Pioneer officially recognized this issue?
the 5.7.1 was my typo ;) thanks @FreshTechno for bringing it up
The Rekordbox XML import method has some flaws. Import dates not being honored is one, cues/loops in the memory banks not having colors is another. And maybe your issue with release date is along that line.
@movingzachb if you read the post you'll find your answer, but it is yes.
@movingzachb, they did: https://forums.pioneerdj.com/hc/en-us/community/posts/360050615212/comments/360007553652
Has this been listed as one of the next priority fixes? Like many other ReCK users, I am also experiencing the same issue and therefore I am forced NOT to upgrade my software to keep the obsolete 5.6.0..
Please can you promise you guys will look into this? It's been over a year already 🙏
@Fabrizio > I see you posted the same thing to several topics; please don't cross-post.
Our engineers are aware of this but we don't have any information on timeline or availability of a fix. Thanks for your patience.