Release - 20170502 - 'pipelines'
May 09, 2017 in bliss by Dan Gravell
The main breakthrough in this release is the introduction of data pipelines.
Before, the tag correction and all other tag rules worked independently. This caused an issue when the rules disagreed on what the tag should be for a given field.
For example, consider the album It Takes a Nation of Millions to Hold Us Back. Imagine this was stored as the truncated title It Takes A Nation Of Millions in your music collection. You have the tag correction rule enabled and also a title case rule enabled for the album name.
The tag correction rule suggests changing the album name to It Takes a Nation of Millions to Hold Us Back. If you do this, the title case rule would then resolve as non-compliant, and ask to change it to It Takes A Nation Of Millions To Hold Us Back.
If you accepted that, then the tag correction rule would complain again, this time about the capitalisation!
So now, suggestions from online data sources are run through a "pipeline" of transformations, supplied by your other rules. In this case, the suggestion will be to change the album name to It Takes A Nation Of Millions To Hold Us Back, and subsequent rescans will assess this album as compliant.
As an aside, if you don't have the case rules enabled, support for ignoring capitalisation and punctuation when assessing tag correctness are coming in the next release.
More improvements
- Disable high performance GPU switching on OS X.
- Make the album detail page prettier when rescanning.
- Fix change art page rescanning/refreshing state model.
- Ensure album data is re-queried when settings are changed.
- When there's a
YEARandDATEin a FLAC, set both. - Show actual album name or artist name when either is non-compliant instead of placeholder text.
Downloading and installing
You can download from the downloads page. After you click through, installation instructions are available on the page following download.
In app update will only work for release 20170307 and later. That's because of a fix in 20170307 following the changes introduced in 20170209 which I wrote about in my call for beta testers. Users on older versions should download the latest and install manually, and from then on in-app update should work again.
Thanks to rawpixel.com for the image above.
