NGS: We're fixing bugs

As soon as we let people lose on the final test server with live data, people started finding lots more bugs. Which means that the final switchover will be delayed for a while longer.

But, the NGS data is live and replication packets for the NGS data are flowing. I’ll post instructions on how to tap into this feed later today.

UPDATE: Please be careful with your edits — we plan to keep this data!. Unless some data corruption bug is discovered, we’re going to do our best to keep this data. Please keep this in mind as you edit on this server.

Picard 0.14 released

NGS is obviously the release of this week, but Lukáš has today announced the release of Picard 0.14 on the mailing list.

Picard 0.14 should be the last release that doesn’t support the NGS web service. It brings some improvements in handling of network errors, changes the default ID3 version, finally adds support for sorting, prioritizing matches based on release types and fixes a couple of bugs. It is also the first release that has a Mac package available at the release time, many thanks to bitmap for that.

You can download the packages as usually at


  • Fixed a problem with network operations hanging after a network error (#5794, #5884)
  • ID3v2.3 with UTF-16 is now the default ID3 version
  • Option to set preferred release types for improved album matching
  • Added support for sorting the album/file lists (#75)
  • Fixed OptimFROG tag reading (#5859)
  • Fixed colors for a white-on-black color scheme (#5846)
  • Added an option to replace non-ASCII punctuation (#5834)
  • Support for writing release group and work IDs, currently unused (#5805)
  • Fixed saving of the release event format tag (#5250)
  • Added support for the language and script tags (#943)
  • Plugins can now use track-track relationships (#5849)
  • Allowed external drives to be visible in the file browser panel on OS X (#5308)

New Web Service policy for NGS

Once we move to NGS on May 16th, we’re going to require each application that makes requests to our web service to have a proper User-Agent header string. The User-Agent string needs to identify the application and the version of the application that is making the request; having a generic User-Agent string like “Java/1.6.0_24” or “PHP/5.3.4” does not allow us to properly identify the application making the requests.

IMPORTANT: 6 Months after we release NGS (Nov 16th) we’re going to start blocking common generic User-Agents strings, so please make sure that you send us a proper User-Agent header as part of your request.

New NGS dataset, new VM and replication started

We have a new NGS dataset available. This data set contains no known bugs (at this point in time) and is the basis for our restarted replication stream.

If you’re interesting in testing the NGS replication stream, please download and install this data set and then run admin/replication/LoadReplicationChanges to pull in the latest changes.

I’ve also uploaded a new NGS Virtual Machine — for details on how to use this virtual machine, please see the wiki page for the virtual machine. This VM is also setup to start replicating off this NGS data stream. Invoke the replication mechanism as mentioned above.

At this point we’re not certain if this is the last time we’re going to start the replication or if we’re going to do it one more time before we release NGS. Stay tuned!