New release - 20100613

This week's release improves memory usage further. When bliss runs it builds an 'index' over your music files. This is so it can easily and efficiently work out where, for instance, all music files for a particular album are stored, all the tracks by a particular artist and similar information. Before, this information was all stored in computer memory. Now I have moved it onto your hard disk. For large collections of, say, 100,000 files, this yields a saving of about 70MB. Meanwhile, more memory work has been ongoing to make libraries of theoretically unlimited size to be supported. This work will hopefully be released next week.

In addition I tweaked how the size rule worked. Before, size was 'approximate'. Not only would bliss look for art +/- 10% of the rule size, but also it would resize down art to 10% over your stated maximum size. For the latter, it made little sense to resize to a size larger than you decreed, so instead for matters of compliancy all sizing is now 'strict'. The sizing is still approximate, however, for online searches, just so you can capture good art that is a few pixels too large/small.

The new build can be picked up at
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.