Another release, more automation!

We've added automation to the tag accuracy rules. We've also made the <tag field> file organisation token even more powerful, and fixed a bunch of other things.

Astell & Kern are an electronics company that manufacture a range of hi-fi equipment, but in recent times it has been its small portable hi-fi units that have garnered most attention.

These players combine hi-fi quality DACs with large displays to browse your music library; so while you get great sounding music, in theory you should be able to easily choose what music to play.

In theory...

This release includes the first tranche of rules automated using the new automation framework we've built into bliss. The maximum image data size rule (which shrinks artwork consuming too many of those precious bytes) and the capitalisation rule both get the automation treatment in this release.

Importantly, there's also a bunch of stability fixes and some added power to the <tag field> file organisation token.

This release completes the porting of all rules to the automation framework. From this point on, converting rules to be automated will be a lot easier.

You can write a generic "find and replace" rule in bliss using custom rules.

In this example I'll take this idea to remove HTML encoding from tags and implement it as a custom rule. HTML encoding is a way of writing certain characters such as < or & in a way that does not affect the rendering of Web pages. The respective special characters for those two examples are < and &.

Unfortunately this text can sometimes be copied outside of an HTML context which leads to gibberish that makes little sense. In our case, it can sometimes make its way into our music tags (maybe caused by copy-and-paste gone bad, or software using data which has been HTML encoded). This then might mean the same gibberish showing up in your music player!