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

[tooone7]

Your description is not precise. What if you have just two songs: 'Pirates' and 'Pirates (No Vox)', should 'Pirates' be displayed in that case or not?

I appreciate your help. In your example Pirates should not be displayed because there is no actual double other than the acoustic one. And imo it doesn't count as a double.

Your mask doesn't work when i enter it in magicNodes it says 'invalid mask'.

My advice is to use "[ ]" only for the version information and "( )" for the actual part of Title. In that case you will be sure that any manipulation with "[ ]" would include only the version information, not the part of Title. You could use RegExp Find & Replace add-on and its "Replace (... remix/version/edit ...) with [ ... ] at the end of <Into Field>..." preset for that.

Good idea i will do that


Edit: i have this now

Code: Select all

Songs.Custom1 IN (SELECT Custom1 FROM Songs WHERE Length(Custom1) > 0 GROUP BY Custom1 HAVING Count(DISTINCT Artist) > 1) AND (<Title> Not Like '%(%' OR <Title> Not Like '%[%')

Taken from the node Tracks>Tracks with same Title from same Artists. Just replaced 'SongTitle' with 'Custom1'.

It still shows tracks with '(' and ')' though...

[ZvezdanD]

Your mask doesn't work when i enter it in magicNodes it says 'invalid mask'.

It works fine. Most probably you used Select All command from this forum which is buggy since it adds several space characters in the front of copied code (I already reported that so long ago, but it seems that none administrator care about it). Just remove spaces or copy code without that command and all will be fine.

[1007]

Hallo
I just tried MediaMonkey 4 Beta with MagicNodes 4.0.4.
When i start MM this error comes :
Error #-2147418113 - SongsDB.SDBStringList
[SafeCall Exception]: List index out of bounds (-1)
File: "C:\Programme\MediaMonkey\Scripts\Auto\MagicNodes.vbs",Line:13846,Column:12

I can quit this message amd MM starts and MagicNodes is working.
The only thing is that i cannot delete a song in a MagicNode.
Nothing happens.

I known its Beta but maybe you will Known this problem.

[ZvezdanD]

I just tried MediaMonkey 4 Beta with MagicNodes 4.0.4.
When i start MM this error comes :

Thanks for the report. MediaMonkey is currently in Alpha stage and it has many bugs related to the script engine. You could try to fix this bug if you open the c:\Documents and Settings\your_name\Application Data\MediaMonkey\MediaMonkey.ini file in Notepad, find [MagicNodes] section and remove LastNode key from it. Note that .ini file has different location then MM3.x (c:\Documents and Settings\your_name\Local Settings\Application Data\MediaMonkey\). After the program starts, open the Options dialog box, go to Magic Nodes tab and turn on the "Skip expanding of the Magic Nodes branch during start-up" option. However, even when you resolve the reported bug, there is another one because of which the Filter edit box in its Settings dialog box is not visible, but it could be resolved only within the program itself.

[1007]

You could try to fix this bug if you open the c:\Documents and Settings\your_name\Application Data\MediaMonkey\MediaMonkey.ini file in Notepad, find [MagicNodes] section and remove LastNode key from it. Note that .ini file has different location then MM3.x (c:\Documents and Settings\your_name\Local Settings\Application Data\MediaMonkey\).

That worked
Many thanks.

btw : location of the .ini is in my version ( WIN7 German ):
C:\Users\xxxxx\AppData\Roaming\MediaMonkey

[SimonORorke]

When expanding any Role node within the Involved People by Role node within the Split Examples node, I get the following error message:

• There was a problem querying the database:
  Error executing SQL "SELECT UpperW('; Guitar: Jim O'Rourke; ') GLOB UpperW('*; Bass:*; *')
  " : near "Rourke": syntax error (1, 1)
  File: "C:\Program Files\MediaMonkey\Scripts\Auto\MagicNodes.vbs", Line:6276, Column: 24

I'm a database programmer myself, so I can see the problem. As I expect you will know well, apostrophes (single-quotes) embedded in SQL literals need to be doubled up, like this:

Code: Select all

SELECT UpperW('; Guitar: Jim O''Rourke; ') GLOB UpperW('*; Bass:*; *')

To replicate the problem, I think it should only be necessary to include an apostrophe in a person's name within any Involved People tag. But, in case it helps, here is the exact contents of the problematic Involved People tag that was being accessed in my case:

• Alto Saxophone, Baritone Saxophone: Mats Gustafsson; Bass: Ingebrigt Haaker Flaten; Drums: Paal Nilssen-Love; Guitar: Jim O'Rourke

I'm using Magic Nodes 4.0.4 with MediaMonkey 3.2.4.

[SimonORorke]

When selecting any Person node within the Involved People by Person node within the Split Examples node, an empty list is shown.

I'm using Magic Nodes 4.0.4 with MediaMonkey 3.2.4.

[ZvezdanD]

To replicate the problem, I think it should only be necessary to include an apostrophe in a person's name within any Involved People tag.

Thanks for the report. This bug will be resolved with the next version of this add-on.

When selecting any Person node within the Involved People by Person node within the Split Examples node, an empty list is shown.

Actually, this is not a bug. You are using one space character after ":" in your tag, so instead of ":" you should use ": " with the Exclusive left/right of qualifiers in that mask, like this:

Code: Select all

<Group|Name:Split examples|Show tracks:No>\Involved People by Person|Icon:Top level\<Involved people|Split by:; |Split Mode:Categories|Exclusive right of:: >\<Involved people|Split by:; |Split Mode:Categories|Exclusive left of:: >\<Album with album artist>

Maybe I could do something about it using Trim function, but such solution could have unwanted effect to those users who use " " as a separator character.

[SimonORorke]

Maybe I could do something about it using Trim function, but such solution could have unwanted effect to those users who use " " as a separator character.

I wonder if perhaps it comes down to what does or does not constitute a well-formed Involved People tag. I would have expected this to be rigorously defined somewhere, but what looks like the official definition at http://www.id3.org/id3v2.3.0 is vague. If space may optionally be used instead of colon as a delimiter, then I can see the problem.

I got the Involved People tag example I quoted above from the http://www.discogs.com/ web site via the Discogs Tagger add-on http://www.mediamonkey.com/forum/viewto ... =2&t=43924. I don't know what validation or formatting there is of Involved People tags on Discogs, but the Involved People Node add-on http://www.mediamonkey.com/forum/viewto ... =2&t=42303 copes with it fine. But then the documentation for that add-on insists that colons, not spaces, be used as delimiters and therefore explicitly states that spaces can optionally be used as padding.

[ZvezdanD]

If space may optionally be used instead of colon as a delimiter, then I can see the problem.

Keep in mind that Magic Nodes is not exclusively written for the Involved People tag/field. Split/Left of/Right of qualifiers that are used for parsing of the Involved People could be also used with any other textual field. For example, Big_Isch is using the space character as a separator for something like this: Custom 1 = "src.cd pkg.cd.2 tracks.12+9 kind.soundtrack albumvolume.92" (http://www.mediamonkey.com/forum/viewto ... 89#p125689).

As I said, this is not a bug/problem of this add-on. Magic Nodes is written to be universal as much as possible and it allows you to use any character or string of characters for the mentioned qualifiers. There would be a real problem if Magic Nodes has hard-coded some separators like ";" and ":", without a possibility to specify your own ones, if some user wants to use some another string as separator. If you are using "; " as separator in your fields instead of ";", it is your responsibility to specify the same string for these qualifiers. I cannot call that "the problem" since you have a possibility to modify the predefined masks or to create your own ones which would have specified proper strings for separator and then you would get the wanted result. The mask which I posted in the previous message would work in your case just fine.

You also have a responsibility to use consistently the same character/string as separator in all your tracks. If you have somehow mixed "; " and ";" in your tags, there are the "Add space character after "";"" separator in multi-item <Into field> if missing" and "Remove space character after "";"" separator in multi-item <Into field>" predefined presets for the RegExp Find & Replace add-on which allow adding/removing the space character after ";". You could modify these presets to do the same thing with ":" instead of ";" very easily.

[Mizery_Made]

I'm having some trouble with the Involved People nodes as well. I'm assuming they're all "default/example" nodes as I can't remember adding them myself (though I have modified them to use "; " and ": " after seeing the last several posts in here). They are:

Code: Select all

<Group|Name:Split examples|Show tracks:No>\Involved People by Role|Icon:Top level\<Involved people|Split by:; |Split part:-1|Exclusive left of:: >\<Involved people|Exclusive right of:: |Split by:; |Split part:-1>\<Album>

<Group|Name:Split examples|Show tracks:No>\Involved People by Person|Icon:Top level\<Involved people|Exclusive right of:: |Split by:; |Split part:-1>\<Involved people|Split by:; |Exclusive left of:: |Split part:-1>\<Album>

<Group|Name:Split examples|Show tracks:No>\Involved People by Involvement and Role|Icon:Top level\<Involved people|Split by:; |Split part:-1|Exclusive left of:->\<Involved people|Split by:; |Split part:-1|Exclusive right of:-|Exclusive right until:: >\<Involved people|Exclusive right of:: |Split by:; |Split part:-1>\<Album>

<Group|Name:Split examples|Show tracks:No>\Involved People by Involvement and Person|Icon:Top level\<Involved people|Split by:; |Split part:-1|Exclusive left of:->\<Involved people|Exclusive right of:: |Split by:; |Split part:-1>\<Involved people|Split by:; |Split part:-1|Exclusive right of:-|Exclusive right until:: >\<Album>

I've just began to "test" these nodes to see if it'll provide me what I'm looking for. Thus, I have tagged a test file with this in the Involved People tag: "Production-Producer: YoungFyre; Production-Additional Production: Karbon"

This is what I'm seeing in the tree however:

Code: Select all

Involved People by Role
\__ Production-Producer
   \__ Production-Additional Production
      \__ <Empty>
   \__ YoungFyre
      \_ Sickology 101

Involved People by Person
\__ <Empty>

Involved People by Involvement and Role
\__ <Empty>

Involved People by Involvement and Person
\__ <Empty>

What I was expecting to see was:

Code: Select all

Involved People by Role
\__ Production-Additional Production
   \__ Karbon
      \__ Sickology 101
\__ Production-Producer
   \__ YoungFyre
      \_ Sickology 101

Involved People by Person
\__ Karbon
   \__ Production-Additional Production
      \__ Sickology 101
\__ YoungFyre
   \__ Production-Producer
      \__ Sickology 101

Involved People by Involvement and Role
\__ Production
   \__ Additional Production
      \__ Karbon
         \__ Sickology 101
   \__ Producer
      \__ YoungFyre
         \__ Sickology 101


Involved People by Involvement and Person
\__ Production
   \__ Karbon
      \__ Additional Production
         \__ Sickology 101
   \__ YoungFyre
      \__ Producer
         \__ Sickology 101

So what could be causing these nodes not to work? Is there something wrong in the way I've wrote the Involved People tag, or is it something to do with the Mask markup? I'm left scratching my head, so I'm hoping you have some insight.

[ZvezdanD]

So what could be causing these nodes not to work?

It seems to me that you are using masks from 3.x version of the add-on. The v4.x version has changed format for the Split qualifiers which is noted in the Important section of the first post in this thread. It is also recommended that you read the Information about 4.0 version section of the same post which explains usage of the related qualifiers in more depth. In your case, you should replace Split part:-1 with Split Mode:Categories.

By the way, if you are upgrading this add-on from some old version, especially if there is updated syntax of masks, it is strongly recommended to follow these steps:
1. make a backup of your own created masks using the Edit / Magic Nodes Export/Import dialog box;
2. uninstall old version of add-on and choose Yes when you are asked if you want to remove add-on settings;
3. install the new version of add-on;
4. import your own created masks using the Edit / Magic Nodes Export/Import dialog box.

In that way you would always have the latest and updated masks. If you don't remove old settings (together with masks), during the installation this add-on would check the mask's names and if they are same as old ones it would skip their installation, even if they are improved/updated.

[Mizery_Made]

Well that's a simple enough fix, changing it to Category has them all working as expected. I've definitely got some old outdated masks then, as I've always just "updated" the script when the Extensions manager found a new update. I'll try to remember to go the uninstall/reinstall route the next time there is an update available.I'm guilty in regards to not reading the information too, as I honestly don't mess with this script much anymore (not having a need for too many custom nodes these days) and I guess I always figured the update would "correct" masks in the process or something.

I... really like what your script can do for the Involved People field, allowing someone to categorize and then sub-categorize the listings (I'm one of those individuals that hates to lose the distinction between roles... hence why I use "Artist 1; ft.; Artist 2" for multiple artists instead of just "Artist 1; Artist 2"). Thus, I was looking for a way of distinguishing between individuals credited for Production, Additional Production, Co-Production, etc instead of throwing them all into one field as "Producer" (which I've been using Conductor for) or having listings like "Producer 1; Producer 2 (add)" which would cause multiple entries in the tree as "Producer 2", "Producer 2 (co)", "Producer 2 (add)" and such.

However I've come to the realization that moving over to the Involved People node and using MagicNodes to present this information... I would lose a the ability of right clicking a track and "Find More From Same -> Conductor"... hm, now I got to figure out what I want to do...

[ZvezdanD]

However I've come to the realization that moving over to the Involved People node and using MagicNodes to present this information... I would lose a the ability of right clicking a track and "Find More From Same -> Conductor"... hm, now I got to figure out what I want to do...

It is not exactly what you want, but maybe you could try Conductor field (or some other multi-item field) with names specified first, then role-sub-role. For your mentioned example ("YoungFyre: Production-Producer; Karbon: Production-Additional Production"):

Code: Select all

<Group|Name:Split examples|Show tracks:No>\Role, Person (using Conductor field)|Icon:Top level\<Conductor|Exclusive right of:: |Unknown:No>\<Conductor|Exclusive left of:: >\<Album with album artist>

Code: Select all

<Group|Name:Split examples|Show tracks:No>\Person, Role (using Conductor field)|Icon:Top level\<Conductor|Exclusive left of:: |Unknown:No>\<Conductor|Exclusive right of:: >\<Album with album artist>

Code: Select all

<Group|Name:Split examples|Show tracks:No>\Role, Sub-role, Person (using Conductor field)|Icon:Top level\<Conductor|Exclusive right of:: |Right until:-|Unknown:No>\<Conductor|Exclusive right of:->\<Conductor|Exclusive left of:: >\<Album with album artist>

Code: Select all

<Group|Name:Split examples|Show tracks:No>\Person, Role, Sub-role (using Conductor field)|Icon:Top level\<Conductor|Exclusive left of:: |Unknown:No>\<Conductor|Exclusive right of:: |Right until:->\<Conductor|Exclusive right of:->\<Album with album artist>

[Mizery_Made]

Hm, that does kind of give a compromise in that it would allow the sub-classifications while also leaving the ability to "Find More from Same." However, it would still leaves the FMFS feature kind of crippled as you could have multiple entries ("Young Fyre: Production-Producer", "Young Fyre: Production-Additional Production", etc) so FMFS would only bring up some of their work.

One thing is for certain though, using Involved People is out of the question. In playing with it a little more, I was reminded why I've given up on attempts to do so before. The way MM uses/writes the field either makes it incompatible with other programs (MP3Tag for instance) or makes it incompatible with the format used for the MagicNodes. Boo. I really wish they would put some TLC into that field. :\

If I do decided to trade in FMFS for these nodes, I may end up using a Custom Field (well, I guess if I give up FMFS, there's no reason I couldn't use Conductor still and just not use FMFS or the built in node.) Anyway, I appreciate your suggestion in using the Conductor field though, Zvez.