> If you try to fix a track name or meta after fixing the path, then the queue won’t be able to process as the track is not to be found anymore before a new scan is made and location is re assessed.

Actually - that should work just fine. It's a bug if it doesn't - please email support@blisshq.com

Had that feeling indeed : the fixes are queued, in the order they were selected. If you try to fix a track name or meta after fixing the path, then the queue won't be able to process as the track is not to be found anymore before a new scan is made and location is re assessed.

One things that could be interesting to remedy somehow would be to filter by action type the inbox so that one can first fix album names before any change is done to rest of the meta. since this would be the key to anything that comes later.
I would prioritize :
1.Album name
- rescan
2.All meta details
3.Track name
4.Path fixing.
- rescan for compliancy validation.
final comliancy checking

> Some drastic measures like deleting may be only available when track names and album etc… things that allows to make sure the track what it pretends to be are actually finalized. I felt like there is a right order to do things.

Interesting - currently all rules run at the same level and don't really know about each others' existence. So the integrity rule wouldn't know whether the track names are "finalised" and, even if the correctness rule was enabled and the album marked as compliant, it can't differentiate between that and the correctness rule being disabled.

Absolutly : one may be able to rank the quality / codec / bit-rate combo and state that this format is the one you want to keep when duplicates are found.

The duplicate process is not clear enough on the format found.
I would prefere to keep Flac over MP3,
However, when i have 5.1 flac and MP3, i'd like to keep booth.

The automate enging may not be able to curate the whole library, but could allow a group fix when the dups meet the ranking list.
As of today, it is not very clear what is being deleted, and most of all, when 2 mp3 are dups, you don't know which one is 128k and which one is 320.
I would also add these details in the list of tracks (put dups next to each other), make a multiple check mark and get rid of the selection - if the auto selection is not able to choose by it self.

- note maybe worth in a different topic. Some drastic measures like deleting may be only available when track names and album etc... things that allows to make sure the track what it pretends to be are actually finalized. I felt like there is a right order to do things.

We would have to define which file would "win" when a group of duplicates is found.

A manual option to do this would be the first stage before http://ideas.blisshq.com/forums/21939-bliss/suggestions/6985890-automatic-removal-of-duplicate-artwork .