Great update Bex, caught a few tracks that had slipped through the net The folder node is a cool addition but it threw up a SQL error when I tried to use a filter with it. Also, bit of a noob question, but how do you update a node to be the same as the tracks in it? I've had a bunch of songs with Node Vs Track Case Inconsistencies for ages and no idea how to get them out.
Thanks!
Yes, a stupid typo made one Folder Node to throw an SQL error. It's fixed now, and a new version will be released soon with additional bug fixed plus a new node.
To fix the Case Inconsistencies, either correct it in MM's ordinary node by pressing F2 and type the correct case or select all tracks which has the incorrect case and mass edit the offending field.
Script is updated
Ver 3.7 (2008-05-13) [MM3 only]
- Added new Album Node:
- - DB Inconsistencies
- Fixed SQL Bug with Filters in a Folder Node
- Fixed SQL Bug in some Album Nodes
- Corrected some bad SQL statements in a few Album Nodes (unicode issues)
The new Album Node: DB Inconsistencies. Finds albums which have exactly same Name and AlbumArtist but different ID's. That shouldn't be possible. To fix them select all tracks in an Album and mass edit the Name and AlbumArtist.
Regarding the new "Album Node: - DB Inconsistencies"
Do anyone have any albums in this node?
If so when were the tracks modified?
And how were the tracks modified?
That look strange indeed. The node is supposed to do this:
- Remove all "signs" from the person name e.g. AC/DC -> ACDC
- Then find all duplicates e.g. Finds AC/DC and ACDC if both exist in your collection.
But something is clearly wrong in your case. I wonder if yo have a persontype named <space>?
What happens if you fix your DB-Inconsistencies?
Also try a Remove Unused Artists.
Please see after each action if the problem did go away so we know what caused it.
Well, I duno. I had already fixed the artist db inconsistencies before opening the non-letter node..
Then after I fixed +; - (multi-artist) to +/- (single artist) and came back from lunch it was fixed (or at least does not display that particular node).
The +/- was originally like this, then whatever version of MM changed it to +; - and just earlier I changed it back to +/- like it supposed to be and appears to stay now.
On the "Persons With... Non-Letter Inconsistencies" node, if you have a case of two files matching because for instance, one has a composer of "D Roc" and the other has an artist of "D-Roc" (two different people, so changing them to match isn't ideal), then if you go in and do a filter to exclude one, the other will still show up with a single entry.
Only solution is excluding them both, however I find it strange that it takes this since if you exclude one, the other has nothing to match. Is this a bug, or how it's intended to work?
The folder node is a cool addition but it threw up a SQL error when I tried to use a filter with it. Also, bit of a noob question, but how do you update a node to be the same as the tracks in it? I've had a bunch of songs with Node Vs Track Case Inconsistencies for ages and no idea how to get them out. 
Last.FM Node
