Release 20160304
March 05, 2016 in bliss by Dan Gravell
Something of an emergency release today; we've had reports of a problem when restarting the latest version of bliss (20160217). In many cases, the restart fails. We've fixed it, and a few other items too!
bliss uses some third party code called OSGi to help manage its codebase. This allows us to track versions of all aspects of the code, calculate the dependencies within the code, and therefore provide reliable means by which the code can be updated from version to version.
Unfortunately, it appears a bug in the way we use OSGi meant that restarting bliss v20160217 after an apparently successful first-start would not work in many cases.
In this new version that's fixed.
More improvements
- In OS X we now store settings in
/Users/[username]/Library/Preferences/bliss
and runtime working files in/Users/[username]/Library/Application Support/bliss
- Reduce the number of times we try to load files when tags are missing.
- Stop using JNotify for file system events. Use Java's own
FileWatcher
instead. - When caching tags, calculate the size of WAV tags more accurately.
- Add opt-out of Google Analytics into the app.
- Log when settings are changed (not what the settings are), the version of bliss and the server OS in Google Analytics
- Fix a race condition when clearing-and-rescanning.
Downloading and installing
You can download from the downloads page. After you click through, installation instructions are available on the page following download.
If you are using Windows and you don't know whether your version of Java is version 7 or later, in app update is not recommended when updating from version 20151013 or earlier, because bliss now requires Java 7 or later. The Windows installer now bundles Java 8, and so download of the full installer is recommended.
Thanks to JoeRuscoe95 for the image above.