XML bridge playlist import issues

Platform: Win7sp1, RekordBox v3.2.1 rev.3231-4360

So, I'm importing a simple playlist, and version 3 does not seem to take the POSITION_MARK (cue points) defined in the XML bridge file. I tried extending the file by specifying TEMPO information and that seems to have the effect of the tracks importing with no beatgrid.

Analysis seems to go fine, I get waveforms and key, etc. I've attached two versions of my bridge file, it does not seem to matter what tracks I pick for them, the behavior seems to be consistent. I also exported my library and the XML file formatting is consistent with 3.2.1's (only more verbose in terms of the fields exported...I always reload tags when I do an import)

I seem to remember version 2.x having issues with importing TEMPO data, but the cues come in just fine.

pope June 18, 2015 03:19 Answered

Post is closed for comments.

Date Votes

8 comments

Will pass upstairs!

Pulse June 21, 2015 00:03 0 votes

Thanks, Pulse.

pope June 21, 2015 02:34 0 votes

@pope > Engineers have responded:

This user seems to write the xml file manually from the scratch. We investigated it and found the cause.

Currently, if TotalTime is not included in the xml file, PositionMark (Cue) will not be able to be imported.

Pulse June 25, 2015 18:58 1 vote

Awesome, just added those tags to the XML, and now the beatgrid and cues and hotcues import just fine. When I wrote this script to export and import playlists from backups, V2.x did not use the PositionMark information. This obviously changed to a requirement in V3.x. Please thank the crew for the speedy response!

pope June 26, 2015 05:25 0 votes

Cool - glad it's working for you now.

Pulse June 26, 2015 06:08 0 votes

Me too. However, I did find that Rekordbox 3.2.1 does not export the RX Hotcue "D", nor does it import it. If I set a cue and all four hotcues for a track in rekordbox then export the XML, I see POSITION_MARK tags with num values of -1 (a cue), 0 (hot cue A) , 1 (hot cue B), and 2 (hot cue C). I would assume that hot cue D is 3, but there is no tag exported with that value. If I manually generate an XML with what I'd assume to be the value for hot cue D, it doesn't set D on import.

The XML import/export code likely has not caught up with the other changes to support the RX. Progress in steps, as it were...

pope June 26, 2015 06:27 0 votes

Yeah, that's known (and noted elsewhere, can't find it atm), and will be addressed in a future update.

Pulse June 26, 2015 06:28 0 votes

Great, thanks...
Also confirmed that if I set the D hotcue in rekordbox, then import that track, it clobbers the D hotcue (even with the D tag in the bridge) so at least the behavior is consistent.

pope June 26, 2015 08:05 0 votes