Magic Nodes 4.2 w/ 380 masks & real GUI (2011-07-01)[MM2+]

[Guest]

Figured it out. Didn't realize i needed to put Composer in brackets (<Composer>) when setting up the code.

It works like a charm now.

Thanks

[martialartsguy]

Hi, small (I hope) request here:

I'd like a magic node that finds all artists with less than 3 songs who are rated less than 3 stars in my library. Thanks!

[B.B]

EDIT*

Never mind..

But thanks anyway..

[Guest]

I'd like a magic node that finds all artists with less than 3 songs who are rated less than 3 stars in my library.

Code: Select all

Artists with less than 3 songs which are rated less than 3 stars|Filter:Songs.Artist IN (SELECT Artist FROM Songs WHERE Rating Between 0 And 59 GROUP BY Artist HAVING Count(*) < 3)\<Artist|Statistic:Count(Tracks), Avg(Rating)>

Code: Select all

Songs form artists with less than 3 songs rated less than 3 stars|Filter:<Rating> Between 0 And 59\<Artist|Statistic:Count(Tracks), Avg(Rating)|Max tracks:2>

[martialartsguy]

Thanks guest!

EDIT: Unfortunately, these two masks still show artists with a large # of songs. The first mask even shows ratings higher than 3 stars. The second shows only 3 stars and below (which is great), but the artists associated also have more songs.

[Guest]

Unfortunately, these two masks still show artists with a large # of songs.

I think it depends how you want to handle unrated tracks. Maybe instead of <Rating> Between 0 And 59 you could try <Rating> <= 59.

The first mask even shows ratings higher than 3 stars.

Of course it shows that. With the first mask you should get all tracks from artists which have less than 3 songs rated less than 3 stars. I didn't know exactly what you want, so I posted two different masks.

[martialartsguy]

OK, I see what's going on here. I wasn't clear about what exactly I was looking for in my magic node. My bad.

What I mean to ask for is this:
I have a number of artists with 3 or less songs total in my library.
I would like to find these artists who have < 3 songs (total) in the library, and also ensure that all of those songs have a rating of 3 or less stars.

[Guest]

What I mean to ask for is this:
I have a number of artists with 3 or less songs total in my library.
I would like to find these artists who have < 3 songs (total) in the library, and also ensure that all of those songs have a rating of 3 or less stars.

Well, it is now much understandable. You could try this:

Code: Select all

Artists with less than 3 songs, all of them rated less than 3 stars or unrated|Filter:Songs.Artist IN (SELECT Artist FROM Songs GROUP BY Artist HAVING Count(*) < 3 And Max(Rating) < 60)\<Artist|Statistic:Count(Tracks), Avg(Rating)>

or if you don't want to handle unrated tracks:

Code: Select all

Artists with less than 3 songs, all of them rated less than 3 stars|Filter:Songs.Artist IN (SELECT Artist FROM Songs GROUP BY Artist HAVING Count(*) < 3 And Max(Rating) < 60 And Min(Rating) >= 0)\<Artist|Statistic:Count(Tracks), Avg(Rating)>

[martialartsguy]

Glorious! Thanks Guest - both those scripts gave me exactly what I needed!

[emalvick]

Files that have multiple genres are accomplishing that right now with multiple genre fields (as opposed to using one genre field with each genre separated by a semi-colon).

for example a song from Nine Inch Nails Ghosts Album may have the following:

GENRE = Rock
GENRE = Electronic

With my MagicNode for genres and all my files most of my genres are showing up multiple times in the list... i.e. Rock is shown twice. It seems that for files in which Rock is in the first Genre field (as shown above) are placed in the first Rock node and that files where Rock is in the second genre field (imagine Electronic being first and the Rock) show up in the second node.

Shouldn't Magic Nodes be able to put all the files tagged with Rock into one Genre Node? Can I some how deal with the fact that there are multiple Genre fields? Magic Nodes seems to come close as it does acknowledge that the files have multiple genres (e.g. the track above will show up under a node for Rock and a node for Electronic), it's just that there are multiple nodes for Electronic and Rock.

As an aside when I look at the files in the browser pane, these same files show the Genres as if they were in one Genre field, e.g. GENRE = Rock;Electronic.

Now I could change all the GENRE tags to be essentially one field with semi-colons, but my media-server cannot handle the Genre field that way.

Does anyone have any ideas on how I can make MagicNodes work for such instances? Does anybody use multiple fields for multiple items and have this issue? I know that some people will have multiple ARTISTS fields, but I haven't tried that to see if the same problem might exist there. For some reason when I specify multiple artists in Media-Monkey using a semi-colon, my file server handles the multi-valued artist field without issue, so I haven't had to split that field into multiple ARTIST tags.

[Weatherman]

Zvendan...I don't want to cross post, so just to say that a query I have placed in PlayHistory &Stats thread has an issue that maybe Magicnodes could solve?
Jim

[Champ19]

Wow - awesome plugin! Just installed it and loving it so far. I read through some of the documentation but it's a little above my head. I'd like to make a new node under Artist that shows tracks where Artist name = Album name. Hopefully this is pretty simple (I browsed through the presets but couldn't find one like this).

Thanks!

[Guest]

I'd like to make a new node under Artist that shows tracks where Artist name = Album name.

Code: Select all

Artist name same as Album name|Child of:Artist|Filter:Songs.Artist = Songs.Album\<Artist>

[Champ19]

Thanks that worked great. Only thing is I expected it to show up under the Artists... Magic Node but instead it shows up under the Library area in the tree view. Not a big deal, just curious as to why it showed up there if it should have been a child of the Artists... Magic Node.

[Guest]

Only thing is I expected it to show up under the Artists... Magic Node but instead it shows up under the Library area in the tree view. Not a big deal, just curious as to why it showed up there if it should have been a child of the Artists... Magic Node.

Well, you first said Artist, not Artists. How could I know that you want the Artists sub-node of Magic Nodes folder and not the Artist sub-node of the Library folder? Here is another mask:
<Group|Name:Artists...>\Artist name same as Album name|Filter:Songs.Artist = Songs.Album\<Artist>