Tagging Inconsistencies 4.0.1 (2014-02-27)

steelydan · Post by **steelydan** » Sun Aug 12, 2007 6:08 pm

As I stated earlier, i love this script. Most useful script I ever used. However, I can think of one fix that may or may not be possible.

When I used this script to find all of my incomplete albums, I used the:

+Tagging Inconsistencies
+Albums with..
+ Missing Tracks

This quickly alerted me of all of my incomplete albums. However, I realized that I still had a few incomplete albums that the script didn't notice.

It turns out that many of my incomplete albums had only the first track. Since I only had the first track and lit was abeled as track number 1, the node assumed it was a complete album. Is there any possible way to add another node that would take note of all albums with only 1 track?

Perhaps this would only be helpful in my situation. I have already fixed these incomplete albums, so there is no glaring need for it. Just thought I'd bring something to the table.

Again, thanks for the great script.

Bex · Post by **Bex** » Sun Aug 12, 2007 6:16 pm

Thanks!
I see what you mean and I can implement such node. I don't know when though.

Bex · Post by **Bex** » Sun Aug 12, 2007 6:24 pm

latinmusiclover wrote:I have a question about the "Initial Invalid Character" node. I have some tracks that begin with valid characters that are marked as invalid -- "(" and "¿" for example. Is there a way to add these characters to the script so that they don't get flagged as invalid? Thanks.

This node only display titles that doesn't start with a letter or a number but it doesn't mean that they are in fact mistagged. I only used this node for browsing through the songs to see if I find any that are mistagged.
But I'll see if I can add some smart settings in the option sheet. It could be a bit tricky.

latinmusiclover · Post by **latinmusiclover** » Mon Aug 13, 2007 11:53 am

Is it possible to add a section that can be updated with an "ignore" list of personal valid characters? Something like a section, "Add Initial Characters to Ignore" and the existing script to check the Initial Invalid Character would filter results through this list before adding them to the node. So, in my vase, I would add "(" and "¿" to this list and they wouldn't appear on the node.

Bex wrote:
latinmusiclover wrote:I have a question about the "Initial Invalid Character" node. I have some tracks that begin with valid characters that are marked as invalid -- "(" and "¿" for example. Is there a way to add these characters to the script so that they don't get flagged as invalid? Thanks.
This node only display titles that doesn't start with a letter or a number but it doesn't mean that they are in fact mistagged. I only used this node for browsing through the songs to see if I find any that are mistagged.
But I'll see if I can add some smart settings in the option sheet. It could be a bit tricky.

nojac · Post by **nojac** » Mon Aug 13, 2007 11:57 am

steelydan wrote: Is there any possible way to add another node that would take note of all albums with only 1 track?

Until Bex has included a "One Track Album"-node (or the MM3 database has stabilized so he can make a new version of his great script

), here is a Magic Node I used for this purpose:

One Track Albums|SQL filter: Songs.IDAlbum IN (SELECT IDAlbum FROM Songs GROUP BY IDAlbum HAVING Count(SongOrder) < 2)|show tracks:yes\<album artist|statistic:count(all)>\<album|sort by:max(year)|sort order:asc|statistic:count(all)>

It is probably more complex than necessary, but I have used several versions of it to show Max 4 tracks, Min 5 Tracks etc... (SLOW in MM2, FAST in MM3!)

PS: An Incomplete Albums Magic Node suggested by Teknojnky:
Incomplete Albums|SQL filter: Songs.IDAlbum IN (SELECT IDAlbum FROM Songs GROUP BY IDAlbum HAVING Count(SongOrder) <> (Max(SongOrder+1)) AND Count(SongOrder) > 1)|show tracks:yes\<Album Artist>\<Album|statistic:count(all)>

steelydan · Post by **steelydan** » Mon Aug 13, 2007 1:20 pm

nojac wrote:
steelydan wrote: Is there any possible way to add another node that would take note of all albums with only 1 track?
Until Bex has included a "One Track Album"-node (or the MM3 database has stabilized so he can make a new version of his great script ), here is a Magic Node I used for this purpose:

One Track Albums|SQL filter: Songs.IDAlbum IN (SELECT IDAlbum FROM Songs GROUP BY IDAlbum HAVING Count(SongOrder) < 2)|show tracks:yes\<album artist|statistic:count(all)>\<album|sort by:max(year)|sort order:asc|statistic:count(all)>

It is probably more complex than necessary, but I have used several versions of it to show Max 4 tracks, Min 5 Tracks etc... (SLOW in MM2, FAST in MM3!)

PS: An Incomplete Albums Magic Node suggested by Teknojnky:
Incomplete Albums|SQL filter: Songs.IDAlbum IN (SELECT IDAlbum FROM Songs GROUP BY IDAlbum HAVING Count(SongOrder) <> (Max(SongOrder+1)) AND Count(SongOrder) > 1)|show tracks:yes\<Album Artist>\<Album|statistic:count(all)>

Thanks for the helpful post. Always appreciative to see others offer solutions. I'll be looking into these ideas. Thanks

latinmusiclover · Post by **latinmusiclover** » Thu Aug 16, 2007 7:19 am

I tried to add both these Magic Nodes, but each one produces an error: "The mask you entered is not valid. Please try again." I looked at the format, but can't find anything wrong with it. Does anyoen know why they dont' work?

nojac wrote:One Track Albums|SQL filter: Songs.IDAlbum IN (SELECT IDAlbum FROM Songs GROUP BY IDAlbum HAVING Count(SongOrder) < 2)|show tracks:yes\<album artist|statistic:count(all)>\<album|sort by:max(year)|sort order:asc|statistic:count(all)>

It is probably more complex than necessary, but I have used several versions of it to show Max 4 tracks, Min 5 Tracks etc... (SLOW in MM2, FAST in MM3!)

PS: An Incomplete Albums Magic Node suggested by Teknojnky:
Incomplete Albums|SQL filter: Songs.IDAlbum IN (SELECT IDAlbum FROM Songs GROUP BY IDAlbum HAVING Count(SongOrder) <> (Max(SongOrder+1)) AND Count(SongOrder) > 1)|show tracks:yes\<Album Artist>\<Album|statistic:count(all)>

Mizery_Made · Post by **Mizery_Made** » Tue Aug 21, 2007 12:54 am

A, just opened up this thread for another reason, but before I went to go into all that, I thought I'd check to make sure I had the most up-to-date version. Noticed that the current version is 2.5 while in my script file I see 2.6, sure there's an explanation (real quick and dirty bug-fix version that you released and I knew about at the time but have since forgotten, and don't wanna go back and read, Lol.) Anyway...

B, I'm back, with Exclusion/OK-List stuff. Lol. Still not that big of a deal, but I had an idea and thought I'd toss it out there. Currently, you offer a simple Folder Exclusion method which serves it's purpose. But, the downside is that if you don't want something to show up under "No Cover," you add it to this list and it no longer shows up under "No Year" either. How can we fix that? Well, I came up with an idea. As usual, have no clue if it's even possible to pull off, and if it is it could possibly slow the script down to a snails pace, you know? Lol. Anyway, here's the concept I came up with:

Kind of similar to that of an Auto Playlist, you add specific rules. In the example shown, I wouldn't want the album "La Primera [Mixtape]" to show up under the No Cover (No Album Art is the actual node I think, but *Shrugs*) so I've added a rule specifying that this rule won't show up under "No Cover" (Exclude From), I'm wanting to exclude by Album Title so I select "Album" as the Exclude Type/Filter Type, then enter the corresponding data, thus "La Primera [Mixtape]" no longer shows up under that node, yet will still show up under No Year, No Track#, etc.

Then you have Plus & Minus's to add/delete a rule. You could exclude based on several fields, such as Artist, Album, Path, and such. Ideas still rather rough around the edges, namely because not much need in putting tooo much thought into it if your not even sure if it's scriptable.

Anyway, the ideas there, if it'd work and doesn't compromise performance or anything then go ahead and use it, otherwise just toss it aside and move along. Whatever the case may be, I still love this script.

I now return you to your regularly scheduled programming, I believe it's a nice long documentary on birds, or was it that new horror movie, don't remember.

Bex · Post by **Bex** » Tue Aug 21, 2007 2:02 am

A. I don't know why I've put 2.6 in the latest version. It's a mistake.

B. Thanks for your idea and detailed explanation. Unfortunately it can't be done in that smart manner but I have a look and implement something that does what you want, when I get the time. I don't think it'll be before MM3 is out.

Thanks
/Bex

Mizery_Made · Post by **Mizery_Made** » Fri Aug 24, 2007 8:05 pm

It may be by design, but I just noticed that the "Album Node: Only Consider Albums With _ Tracks or _" option has no effect on "Albums With... Multiple Bitrates." I have the option set to 5 Tracks or More, yet an album that I have only 2 tracks for shows up under said node.

Again, could be by design, but given the option specifies "Album Node," and this resides within that node... *shrugs*

Bex · Post by **Bex** » Sat Aug 25, 2007 5:06 pm

You're right Mizery_Made. In fact that option doesn't apply to any of the "Albums with... Multiple ***"-nodes. I don't remember exactly why I left them out but I think it was performance reasons in conjunction with the need of having that limit in those nodes.

Let me know if it's important and I can include that limit in all nodes.

Diabolic-Destiny · Post by **Diabolic-Destiny** » Mon Aug 27, 2007 5:33 pm

sorry is this compatbile with MM3?

Bex · Post by **Bex** » Mon Aug 27, 2007 5:57 pm

Not yet. I'm waiting for MM3's database structure to be set.

Superfrodo · Post by **Superfrodo** » Tue Sep 04, 2007 6:23 am

Could you please add 2 nodes to the Album node:
* No Album Art in Tag, only Linked
* No Linked, only Album Art in Tag

This would really help me with adjusting Album Art from Linked to Tagged, and the other way around.

By the way: superb script. I use it all the time

Grtz SuperFrodo

Bex · Post by **Bex** » Tue Sep 04, 2007 12:32 pm

Thanks!

That would be possible. I'll see when I get the time to implement it! But I have to convert the script to MM3 first.