0.6.2

Fixed

• The interpretation of colors for memory points and loops (as opposed to hot cues) has been fixed, thanks to a contribution by @ehendrikd.
• It turns out that nxs2 cue list entries are not always complete, they are sometimes missing color information or even the comment information that precedes it. We no longer crash when we encounter
  such partial cues.
• Fixes to the Beat Link and Crate Digger libraries allow them to work properly with new formats for data that rekordbox 6 sends. We may find more problems in the future, because testing with this new version has been limited, but it is already working much better than it did at first.
• An update to Crate Digger avoids crashes when trying to parse track analysis files created with mal-formed vestigial waveform preview tags.
• The interpretation of byte 0x37 in the CDJ status packet has been updated, which forced fixes of the isDiscSlotEmpty() and getDiscTrackCount() methods in CdjStatus.
• Links in the JavaDoc now directly take you to the relevant sections of the new Antora documentation site that replaced the old PDF protocol analysis document.
• Track Load packets now need to have an extra value to tell the recipient on which deck the track should be loaded, because the XDJ-XZ has two decks but only one network address on which to receive these commands. (Sadly for us, it refuses to load tracks from other players even when this byte is sent correctly, it only loads tracks from a rekordbox collection when rekordbox tells it to.)

Added

• Another bit has been explained in the main CdjStatus flags byte: we can now tell when a DJ has forced a player into degraded BPM-only sync mode (by nudging the jog wheel of a synced player).
• We now know that beat grid entries also report the tempo of the track at that beat, so this is properly exposed in the API.
• We now fully support the device number assignment phase of the Pro DJ Link protocol, so when Beat Link is connected to an ethernet port on a mixer that is assigned a dedicated channel number, it will use that device number, and we defend our device number once we have successully claimed it.

Deprecated

• The classes and methods relating to creating and using metadata caches are no longer needed because we can reliably obtain metadata no matter how many CDJs are on the network.
• The getName and getNumber methods in DeviceAnnouncement were inconsistent with the getDeviceName and getDeviceNumber naming convention used in the entire device update packet hierarchy.