So I finally get around to upgrading 3.2.1, and come up with the following issue regarding XML playlist import via the XML bridge:
Normally on version 3, cue and hot cue points load up no problem from tracks imported, but for some reason version 4 simply ignores them.
Here's a sample of a small test xml file, you can make it with any .mp3 for test purposes. Any tracks loaded via this route come in with out cue points or hot cues, at least for me.
<?xml version="1.0" encoding="UTF-8"?>
<DJ_PLAYLISTS Version="1.0.0">
<PRODUCT Name="rekordbox" Version="4.3.1" Company="Pioneer DJ"/>
<COLLECTION Entries="2">
<TRACK Location="file://localhost/C:/test1.mp3">
<POSITION_MARK Name="cue" Type="0" Start="0.046" Num="-1"/>
<POSITION_MARK Name="HCB" Type="0" Start="0.046" Num="1"/>
<POSITION_MARK Name="HCA" Type="0" Start="416.792" Num="0"/>
</TRACK>
<TRACK Location="file://localhost/C:/test2.mp3">
<POSITION_MARK Name="cue" Type="0" Start="4.287" Num="-1"/>
<POSITION_MARK Name="HCB" Type="0" Start="4.287" Num="1"/>
<POSITION_MARK Name="HCA" Type="0" Start="357.774" Num="0"/>
</TRACK>
</COLLECTION>
<PLAYLISTS>
<NODE Type="0" Name="ROOT" Count="1">
<NODE Type="1" Name="test1.mmp" Entries="2" KeyType="1">
<TRACK Key="file://localhost/C:/test1.mp3"/>
<TRACK Key="file://localhost/C:/test2.mp3"/>
</NODE>
</NODE>
</PLAYLISTS>
</DJ_PLAYLISTS>
Post is closed for comments.
...hold off on looking into this for a moment. Through the upgrade, it looks like RB did not carry over the previous version's configuration file, so let me make sure version 4 is looking in the right places first.
Confirmed: The configuration file in 4.x was apparently incompatible with version 3.x, and many of the settings on 4.x pointed to default folders. In this case, the default folder contains an XML bridge file generated for Rekordbox version 2 (I know, ancient history, but that version still resides on an ancient laptop in the oft-chance this one breaks and I need to move tracks to a USB before fixing it).
What, exactly, is the issue?
I think this can be closed off.
This is just a minor annoyance. When I upgraded from 3.x to 4.x, I expected the 3.x configuration would carry over for all common parameters. Well, not so much as an expectation as I didn't really think much about it.
It might be a bit of a stretch to expect a major release (3.x to 4.x, for example) to carry over the majority of configuration settings. In this particular case, my custom setting for XML bridge file location in 3.x got reset to the default in 4.x.
On my platform, for testing I had an old 2.x version pointing at that location, and that version of rekordbox can't deal with cues at all in the bridge file. 4.x was happily picking up that XML, and here I was wondering were the cues were. Sure enough, version 4 was not looking at the right bridge file, because the location setting got reset to default, pointing to a deprecated version of the playlist file.