rrfpacker wrote:It seems some knowledge of SQL is needed and I just haven't had the time.
And yet you had the time to manually tag all those tracks

You don't need to know SQL, all you need is to ask for help and I could write mask for you.
By the way, the suggested masks could be used not only for editing tags, but also to get tracks useful for playlists. For example, the predefined "Tracks without duplicates and only one track which has duplicates" mask returns all tracks from the Library without duplicated ones, which is useful for playback when you don't want to listen the same tracks two or more times. If its purpose is still not clear, here is some example. Let say that I have 3 tracks in the Library:
ID = 1, Artist = A1, Title = T1
ID = 2, Artist = A1, Title = T1
ID = 3, Artist = A1, Title = T2
With the mentioned mask I could get the list with tracks: ID = 1 and ID = 3. The main difference between that predefined mask and the new ones which I have posted is in that if some track has duplicates the predefined mask returns the first track added to the Library, and the new masks returns the one with the maximal bitrate/rating. For the same example:
ID = 1, Artist = A1, Title = T1, Bitrate = 128
ID = 2, Artist = A1, Title = T1, Bitrate = 192
ID = 3, Artist = A1, Title = T2
and with the mask "Duplicates with maximal bitrate and tracks without duplicates" I would get the list with ID = 2 and ID = 3.
Magic Nodes from v3.x has a possibility to create static playlists instead of the regular nodes, if you add |Child of:Playlists|Position:Child to the global node of mask, i.e. if you choose Position: Child of, Playlists from the GUI. Such static playlist could be used in some auto-playlist if you specify Playlist is playlist_name condition. Keep in mind that Magic Nodes v4.x creates sub-nodes of playlist as well when you have mask with sub-nodes - if this is not what you want, you need to remove sub-nodes from such mask.
[quote="rrfpacker"]It seems some knowledge of SQL is needed and I just haven't had the time.[/quote]
And yet you had the time to manually tag all those tracks ;) You don't need to know SQL, all you need is to ask for help and I could write mask for you.
By the way, the suggested masks could be used not only for editing tags, but also to get tracks useful for playlists. For example, the predefined "Tracks without duplicates and only one track which has duplicates" mask returns all tracks from the Library without duplicated ones, which is useful for playback when you don't want to listen the same tracks two or more times. If its purpose is still not clear, here is some example. Let say that I have 3 tracks in the Library:
ID = 1, Artist = A1, Title = T1
ID = 2, Artist = A1, Title = T1
ID = 3, Artist = A1, Title = T2
With the mentioned mask I could get the list with tracks: ID = 1 and ID = 3. The main difference between that predefined mask and the new ones which I have posted is in that if some track has duplicates the predefined mask returns the first track added to the Library, and the new masks returns the one with the maximal bitrate/rating. For the same example:
ID = 1, Artist = A1, Title = T1, Bitrate = 128
ID = 2, Artist = A1, Title = T1, Bitrate = 192
ID = 3, Artist = A1, Title = T2
and with the mask "Duplicates with maximal bitrate and tracks without duplicates" I would get the list with ID = 2 and ID = 3.
Magic Nodes from v3.x has a possibility to create static playlists instead of the regular nodes, if you add |Child of:Playlists|Position:Child to the global node of mask, i.e. if you choose Position: Child of, Playlists from the GUI. Such static playlist could be used in some auto-playlist if you specify Playlist is playlist_name condition. Keep in mind that Magic Nodes v4.x creates sub-nodes of playlist as well when you have mask with sub-nodes - if this is not what you want, you need to remove sub-nodes from such mask.