Emergency! Release 20131108

ERP! After releasing the first build for some time on Tuesday I began getting reports of problems when starting bliss. It was only today that I was able to properly identify the problem.

I mentioned in the previous release's notes that:

The <tracknumber> token used in the default file organisation patterns has been changed. Now, we use <tracknumber:auto> rather than the "raw" value, to make it more widely applicable and to provide an ordered track list in all players by default. Existing use of the default patterns will remain the same, although your pattern will now be counted as a "custom" pattern in the settings user interface.

Well, that was the intention. In reality the code that attempted this conversion had a bug which meant new users couldn't start bliss! So, a frantic few hours of fixing, building and regression testing today have led to this new build.

The good news is that as well as this fix, there are a few more useful fixes in this release...

  • Use the new version of OneMusicAPI
  • Better error reporting in popups when fixes don't work
  • Fixed multiple identical entries appearing in genre dropdowns
  • We now support Stripe for payments, so you can just supply your credit card details in the app

Downloading and installing the latest release

You can download the release from the downloads page. After you click through, installation instructions are available on the page following download.

Existing users can use the in-app updater. You can also download the latest installer and install it, replacing the current installation. Any fixes licences already purchased will be retained!

tags: release
blog comments powered by Disqus

The Music Library Management blog

Dan Gravell

I'm Dan, the founder and programmer of bliss. I write bliss to solve my own problems with my digital music collection.