For instance, some of my albums have extra info in the album name such as (2009 Remaster). When bliss searches for album art, it includes this extra info in the search and (most of the time) doesn't find the album art. It would be nice if I could edit the search string that is being used (basically just to remove this extra info) so that I could get the proper art. A step further might be to have this happen automatically if no art is found, but that is probably asking too much.

Currently bliss always performs case sensitive comparisons of music tags to file/folder names. It should be optional to force bliss to consider what a file/folder name should be in light of a preferred case.

For instance, when using <fileextension> to organise music files by their file type, it would be useful to be able to enforce capitals, otherwise on case sensitive file systems we may end with folders like mp3/, MP3/ and so on.

Provide the ability to have a different folder for compilations.

Currently, the artist seems to default to 'Various'. The directory name could begin 'Compilations' for example.

Here's a similar idea to vary rules according to genre: http://ideas.blisshq.com/forums/21939-bliss/suggestions/36753685-individual-rulesets-for-different-genres

The ability to produce, print and export a "catalogue" of the music library which could be sorted by album, artist, quality etc.

bliss should allow textual tags to contain "derived" data; that is, to provide consistent manipulations of canonical data to a defined scheme.

An example of this may be to append the bitrate to an album name. Using a template engine, the album could be defined as so:

Album name: <album name> [<format>]

Tags could potentially be combined with others:

Track name: <track name> (<artist name>)

Set out in more detail here: https://www.blisshq.com/music-library-management-blog/2017/10/03/derived-tags/

When choosing the album art manually nowhere you can know the directory name of the current "album" and that can help alot for choosing the good cover matching good album version

There are a couple sites to review.
http://www.chartlyrics.com
http://www.lololyrics.com
http://lyrics.wikia.com

have a button to open an album's folder in the os on the album detail page to let the user manually examine/fix files/folder.

Add a capability to add the correct linked release if it is not found by Bliss.
Often (especially for more obscure albums) the album is marked non-compliant as the list of linked releases does no find the actual matching release. If I unlink all releases and rescan, it will clear the errors, but it would be good, after unlinking all the incorrect releases, to be able to add the correct release so bliss was able to verify the tags against the correct release (rather than just marking it all as compliant becuase it has no linked releases to check against).

I have a main folder called "Full Albums" which contains the folder structures defines in my rules. I also have a number of folders like "Various - 00s", "Various - 90s" etc. Each of this folders contains lots of individual mp3 singles, each mp3 has it's own genre, year and file naming convention (without track numbers).

The only way I could think of doing this is allowing multiple music folders, and allowing us to setup rulesets for a each folder (or group of folders).

It would be very useful if you can save your view/display settings for you tags.
Now, Every time I go back to the tags page it displays the default columns, and I have to select again the Year and Genre columns.
I know files may have different field tags applied, but this would be useful for Common Tags only

When enforcing a title case rule, it should be possible to make an exception for abreviations so that an album can still be compliant.

It would be nice to be able to delete albums easily

Create a new album artist token to order artist names as Last, First. Also order groups as "The Beatles" to "Beatles, The"

As discussed previously...

Dan Gravell (Founder and programmer, bliss) commented · August 21, 2015 10:37 ·

Adding every artist name would not scale, so I want to solve this alongside the canonical artist rule. I think I could add a checkbox to the rule saying "if the artist is canonically correct, ignore the case rule".

That said, OST are an interesting one! http://musicbrainz.org/search?query=OST&type=artist&method=indexed

Could you add this as a new idea? The same fix can also be applied to album and track names.

Being able to tag songs with multiple tags through the UI or automatically.