Release 20200903

Progress A few more bug fixes in this week’s release, with a special concentration on the progress indicator (the Scanned n of m albums text).

The progress indicator should now update when settings are changed and a rescan occurs. Before, the progress indicator would show on rescans from the Albums page, but not after rules change.

To improve memory efficiency, we’ve consolidated the number of threads used by several places in the codebase that were capable of dropping hung HTTP calls for metadata. Reducing the number of threads in this way saves some memory which is important for more constrained NAS devices.

Around rules, we found a bug where if the missing information rule was enabled for album-level tags like genre or year, and an album had inconsistent values for those fields, we’d report the inconsistent values as “incorrect”. Now, we’ve changed that to only mark the missing values as… well… missing. The suggested value is the most common value in the other files.

We got a report that when using the top level Tags page, changing album or artist names would mean the album wasn’t rescanned after the change. We’ve fixed that.

Finally, we found that in certain rare circumstances data would not be committed to our database when some of the information about an album changed - we fixed that. This only became apparent if bliss was stopped immediately after the update.

Downloading and installing

You can download from the downloads page.

After you click through, installation instructions are available on the page following download.

Photo by Jungwoo Hong on Unsplash

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.