0.3.4

This is a small release to help address some requests generated as the audience for Beat Link Trigger has expanded greatly in response to a DJ TechTools article.

Added

• Exposed the function which opens and returns a metadata cache file,
  so that other projects can explore their contents, for example to
  offer a view of what they contain.

0.3.2

This is a small release to help address some issues found as the audience for Beat Link trigger has expanded greatly in response to the DJ TechTools article.

Added

• More logging about the detection of media being mounted and removed
  from players, to help track down problems creating metadata caches.

Fixed

• There was a potential for the thread that reports media being
  mounted or removed to terminate if any exceptions occurred while
  handling player updates. It now logs these and continues.

0.3.1

This is primarily a release of recent changes so that a release of Beat Link Trigger can be made, to make it easier for everyone who heard about it via the DJ TechTools article to download the version that includes on-air indicators and SMPTE hooks.

Added

• The TimeFinder now keeps a list of listeners that want help tightly following track position changes, for example to generate SMPTE time code that is tied to the current playback position.

0.3.0

Changed

• The entire metadata retrieval approach has been fundamentally
  rewritten, based on a much deeper understanding of the message and
  field format, thanks to tips and sample code from @awwright.
• This led to a deep refactoring of the library, and a split into
  several packages, now that there are many more classes to support
  all of these new features. API compatibility was not maintained with
  previous releases.

Added

• Many more kinds of information can be retrieved from players, and
  the classes and API documentation have been enriched to reflect our
  deepening understanding of the protocol.
• Metadata cache files can be created by downloading either entire
  collections or individual playlists from players on the network, and
  then attached for use in environments (such as busy shows with four
  physical players) where metadata queries are not reliable.
• Metadata cache files can be monitored for automatic attachment to
  player ports when media that matches the cache is mounted by the
  player.
• New listener interfaces to provide information about changes to the
  available metadata caches, as well as changes to metadata about
  tracks loaded in players on the network.

Fixed

• The approach to concurrency was examined carefully, and almost all
  synchronized methods were eliminated in favor of newer concurrent
  classes for improved performance and safety.
• When the last device disappears from the Pro DJ Link network, we
  clear the DeviceFinder's notion of when we first saw one, so that
  the VirtualCDJ's device-number conflict-avoidance code can work
  properly when we later encounter a new network.

0.2.1

This release includes the ability to tell the Virtual CDJ to use a standard player number when starting (important for when retrieving metadata), includes an important fix to the process of self-assigning a player number to avoid conflicting with and knocking an actual player off the network, supports new (and slightly larger) CDJ status packets from more recent firmware, and allows you to request all metadata from a given media slot.

See the change log for details.

Release 0.2.0

This release adds the ability to retrieve track metadata, including artwork images, thanks to discoveries made by @evanpurkhiser. See the change log for details.

Release 0.1.9

This release makes a small change to the nature of timestamp values for compatibility with Ableton Link. See the change log for details.

Release 0.1.8

This release adds initial support for NXS2 devices, some new features related to identifying tracks and starting to experiment with requesting their metadata. It also uses slf4j to integrate with whatever logging framework its host project wants to use. See the change log for details.

Release 0.1.7

This release chooses the device number to use for the VirtualCdj by watching for an unused device number between 5 and 15 when starting, unless you explicitly set one to use by calling setDeviceNumber(). See the change log for details.

Release 0.1.6

This release fixes an issue with Beat packets found while developing beat-link-trigger. See the change log for details.