Magic Nodes 1.3b (IS OUTDATED SEE NOTE IN FIRST POST)

jonisaksson · Post by **jonisaksson** » Mon Apr 23, 2007 2:25 am

hi just save the txt file and change the file extension after you have downloaded it to be a vbs file

So from MagicNodes.1.3b.txt to MagicNodes.1.3b.vbs

Pablo (not logged in) · Wed Apr 25, 2007 6:08 am

Anonymous wrote:Hi Pablo:

The Download link only takes me to a script page. How do I actually download it?

You have to right-click on "here" and select "download as". This will download the file. Then you have to change the extension from .txt to .vbs. To do this you may need to configure the explorer to show extensions.

El Cabrito · Post by **El Cabrito** » Mon Apr 30, 2007 10:55 am

hey,

LOVE the magicnodes!

though i can't figure out something, when using magic nodes to create an alphabetically order list of artists or album artists, is there a way to get it to ignore "the" for the sorting criteria. For ex. I want to create a MN for album artist that lists them in alphabetical subnodes. i.e.

Album Artist (alphabetical)|child of:artist\<album artist|trim:1>\<album artist>\<album>

but, it sticks those artists w/ "the" at the beginning under the "T"s. i.e "The Afghan Whigs" is under "T" and not "A".

Any suggestions?

thanx

Bex · Post by **Bex** » Mon Apr 30, 2007 11:03 am

Yes, there's a modified version some pages back which takes care of that problem.

El Cabrito · Post by **El Cabrito** » Tue May 01, 2007 8:23 am

found the new MagicNodes 1.3c script. Works even better!

Son of Spam · Post by **Son of Spam** » Thu May 03, 2007 11:12 pm

Pablo wrote:I've posted a new version of the script. It's basically a bug fix release. The only new functionality is the left of: and right of: qualifiers, which implement the idea of Sadao:

If one organizes genres as

Super genre-Sub genre
Then <genre|left of:-> would pick the Super genre, and <genre|right of:-> the Sub genre. So one could have the following Super Genres node:

Super genres|child of:genre|icon:top level\<genre|left of:->\<genre|right of:->\<album artist>\<album|sort by:max(year)>
Download the new version from the website,

http://students.washington.edu/~shmerkin/magic_nodes/

As always, questions, comments, bug reports and etc are appreciated .

Unfortunately, that link no longer works.

scarecrow · Post by **scarecrow** » Mon May 07, 2007 9:12 am

Anyway, Magic Nodes do not seem to work with 3.0 A4... I just get scripting errors when trying to run it.

Bex · Post by **Bex** » Mon May 07, 2007 11:14 am

Link that works: (From the first post.)
http://magicnodes.110mb.com/

Very few scripts works in MM3 due to its database structure is changed but not finalized. I don't think anyone will update their script, which contains SQL, until the final structure is set...

latinmusiclover · Post by **latinmusiclover** » Wed May 09, 2007 10:05 pm

I came across a typo on the page -- after I spent ages trying to figure out what I was doing wrong!

Example 11
Comments|icon:top level\<comments|trim:25>

Should read:
Comments|icon:top level\<comment|trim:25> (the field is "comment")

ZvezdanD · Post by **ZvezdanD** » Tue Jul 10, 2007 8:58 pm

scarecrow wrote:Anyway, Magic Nodes do not seem to work with 3.0 A4... I just get scripting errors when trying to run it.

Hi folks!

I just finished modifications of Magic Nodes script, mainly to enable its work with MediaMonkey 3.0. I am not original author, so this 1.4.0 modification is unofficial. Unfortunately, its author Pablo is very busy and temporarily abandoned work on it. I got a permission from him for sharing modified script in this forum, so you can take it.

Keep in mind that this modified version is only a provisional solution. It works with current 3.0.0.1045 alpha version of MediaMonkey, but there is a possibility that it would not work with future versions of MM, if developers decide to change MM database structure. It is fairly tested, but there is also a possibility that some combination of input parameters will not work.

Currently not working:
- percent argument of top qualifier (e.g. top: 5 percent)
- first and last arguments of sort by qualifier (could be replaced with min and max)

Should be tested:
- left of and right of qualifiers
- drag & drop
- ...

Please, use it only on your own risk:

http://solair.eunet.yu/~zvezdand/MagicNodes.htm

Maybe it is not clear from previous sentences (English is not my mother language), so I need to mention that this modified script works also with previous version of MM >= 2.2.

nojac · Post by **nojac** » Wed Jul 11, 2007 8:03 am

Thank you very much for your work on modifying MagicNodes to MM3, ZvezdanD It seems to work perfectly for me.

My first question is: Can I add the number of tracks after each album, like it works on another favourite script: Bex’s Tagging Inconsistencies (which unfortunately is only for MM2, the main reason why I still need MM2….)

A minor second question: My node is: Album Artist MN|child of:Library\<album artist>\<album|sort by:max(year)|sort order:asc> I thought this would make it a subnode of Library (beside Artist and Album...) but it came up as a main node, beside Library. OK for me, but ...

And finally: 3. Is there a way to expand this node, so I can see all artists with their album subnodes in the left panel?

(May be you should make a new thread for the MM3 version?)

ZvezdanD · Post by **ZvezdanD** » Thu Jul 12, 2007 3:48 am

nojac wrote:Thank you very much for your work on modifying MagicNodes to MM3, ZvezdanD It seems to work perfectly for me.

Thanks, I am really glad that you like it.

My first question is: Can I add the number of tracks after each album, like it works on another favourite script: Bex’s Tagging Inconsistencies (which unfortunately is only for MM2, the main reason why I still need MM2….)

As I know, it is not possible with some custom user mask, but it needs modifications of script source code. I thought about similar possibilities before, and I think that it shouldn't be very hard to implement something similar. I am thinking about more general approach where you can enter custom defined display of fields, not only those hard-coded in script, but I cannot give you any promise about this.

BTW, Bex is a great programmer and I think that he only waits for final MM 3 to make modifications on mentioned script.

A minor second question: My node is: Album Artist MN|child of:Library\<album artist>\<album|sort by:max(year)|sort order:asc> I thought this would make it a subnode of Library (beside Artist and Album...) but it came up as a main node, beside Library. OK for me, but ...

I am not sure that understand you. I think that you should replace Library with Artist, if you want your node to be sub-node of Library.

And finally: 3. Is there a way to expand this node, so I can see all artists with their album subnodes in the left panel?

Off course. I don't understand where is a problem?

(May be you should make a new thread for the MM3 version?)

I am not sure this would be correctly to Pablo. I'll ask him if he don't mind about this.

nojac · Post by **nojac** » Thu Jul 12, 2007 11:35 am

ZvezdanD wrote:
A minor second question: My node is: Album Artist MN|child of:Library\<album artist>\<album|sort by:max(year)|sort order:asc> I thought this would make it a subnode of Library (beside Artist and Album...) but it came up as a main node, beside Library. OK for me, but ...
I am not sure that understand you. I think that you should replace Library with Artist, if you want your node to be sub-node of Library.

You are right. I assumed that "child of" ment "subnode of", but that was not the case

ZvezdanD wrote:
And finally: 3. Is there a way to expand this node, so I can see all artists with their album subnodes in the left panel?
Off course. I don't understand where is a problem?

I guess the answer is too obvious for an experienced user to understand that anyone could have such a simple problem... When I open the AlbumArtist subnode I want to see all the albums of all the artists without having to "open" each artist individually.

ZvezdanD · Post by **ZvezdanD** » Thu Jul 12, 2007 2:15 pm

nojac wrote:You are right. I assumed that "child of" ment "subnode of", but that was not the case :oops:

Yeah, I agree with you that this name is somewhat confusing. But, if "child of" works as "subnode of" we couldn't have a possibility to put a node to the same level as Library, Playlists and other nodes on first level.

I guess the answer is too obvious for an experienced user to understand that anyone could have such a simple problem... When I open the AlbumArtist subnode I want to see all the albums of all the artists without having to "open" each artist individually.

Sorry, problem is not in connection with some experience, but with my lack of English language. I thought that you want:
- AlbumArtists MN
--- AlbumArtist1
----- Album1
----- Album2
----- ...
--- AlbumArtist2
----- Album1
----- ...

This was obvious, but now, I am not sure. Do you want to get something like this:
- AlbumArtists MN
--- AlbumArtist1 - Album1
--- AlbumArtist1 - Album2
--- ...
--- AlbumAstist2 - Album1
--- ...

Currently, this is not possible. But, you could try something like this:

Code: Select all

Album Artist MN\<album and artist>

In that case, you will get somewhat different layout: Album (Artist)

Please, could you send your MN mask?

emalvick · Post by **emalvick** » Thu Jul 12, 2007 2:27 pm

nojac wrote: I guess the answer is too obvious for an experienced user to understand that anyone could have such a simple problem... When I open the AlbumArtist subnode I want to see all the albums of all the artists without having to "open" each artist individually.

Why don't you try a Magic Node like this:

Artist Album\<album|sort by:album artist>\<title>

I believe this will essentially create an album node but sort the albums by the artist.

Now on first look, you might think it will only show you the album names, but I've found that when using something similar the node will actually show as: album artist - album or maybe (album artist) album...

In my case I had used a node like the following:

Artists and Albums by Year\<artist>\<album|sort by: year>

When I did this, I would see the list like this:

U2
|
|-(1980) Boy
|-(1983) War
|-(1985) The Unforgettable Fire

for each artist. I didn't like it much for me as I really didn't need to see the year, but MN seemed to by default include that sort criteria in the node. It seems then that for your album node you'd get something similar with the artist name being at the front; you just eliminate the <artist> node so that it is only an album node.

Erik

Magic Nodes 1.3b (IS OUTDATED SEE NOTE IN FIRST POST)

ignore "the" for alphabetical sort in <album ar

Thanx Bex

Passing It Along: Typo in Examples in Help