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

Download and get help for different MediaMonkey Addons.

Moderators: Peke, Gurus


Jinx
Posts: 2
Joined: Wed Dec 12, 2007 5:39 am

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

Post by Jinx » Fri Jun 29, 2012 2:31 am

@keiju

I just saw your post. If you still haven't found a solution try this one:

Code: Select all

Pais\<[b]Pais[/b]|Split by:[b];[/b]>\<Artist>\<Album>\<Title>
If I understood your problem correctly then this should solve it.
Please note that the first "Pais" is just the name of the node while the second one is the actually name of your custom field.

Regards
Jinx

Macarena
Posts: 618
Joined: Mon Oct 15, 2007 5:39 am
Location: Prague, Czech republic

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

Post by Macarena » Sat Jun 30, 2012 12:24 pm

Hi Jinx,

it does not work for me. I used my own CustomField name, and I also deleted some fo the BBCode:

Code: Select all

Pais\<Pais|Split by:;>\<Artist>\<Album>\<Title>
Additionally, I found out, that there is no "Split examples" group among my Magic Nodes, please. Do you think I can do anything about it?

I am using MM 4.0.6.1500 and MN 4.2.

Cheers,
M
Jinx wrote:I just saw your post. If you still haven't found a solution try this one:

Code: Select all

Pais\<[b]Pais[/b]|Split by:[b];[/b]>\<Artist>\<Album>\<Title>
Last edited by Macarena on Sun Jul 01, 2012 2:32 am, edited 1 time in total.

Macarena
Posts: 618
Joined: Mon Oct 15, 2007 5:39 am
Location: Prague, Czech republic

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

Post by Macarena » Sun Jul 01, 2012 1:49 am

Done! :) I used the MN composition window (Edit > Magic Nodes settings... or ctrl-9) and in the MediaMonkey.ini the following line has appeared:

Code: Select all

Mask226=Source\<Source|Split by:;>\<Artist>
Macarena wrote:it does not work for me. I used my own CustomField name, and I also deleted some fo the BBCode:

Anamon
Posts: 76
Joined: Sat Jul 21, 2007 4:38 am
Location: Switzerland
Contact:

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

Post by Anamon » Thu Jul 05, 2012 5:20 pm

There seems to be a weird bug with the order of tree nodes using Magic Nodes 4.2 on MM 4.0.6. I haven't used MM in a while, so I don't know about earlier versions. It seems to happen when trying to position a Magic Node after the last regular collection node.

I have 5 Magic Nodes that I wanted to have as the bottom nodes in my Music collection tree, so I set all their positions to "After Previews". However, out of those 5 nodes there is one that is not at the end of the list, but right after the Album & Album Artist node. It is always the last of the 5 masks, so if I change the order of the Magic Nodes masks, it will be a different one.

Image

I can fix the situation temporarily by changing the Position setting of the Magic Node in question, clicking Update, then setting it back to After Previews and hitting Update again. However, for the next MM session the node will be back up again.

The issues don't stop there though, they seemingly also affect the order of regular MM tree nodes. In particular, the Composer node, which I have moved several nodes down to after Year in MM's Collection Settings, will occasionally turn up after Album & Album Artist—the same position the Magic Node always falls back to.

Image

Composer does not always move there, it is seemingly chosen randomly at the start of MM whether it will be in its correct position or not. Also, moving it around in collection settings does not allow me to fix the issue, not even temporarily. However, trying to do so will revert the Magic Node back up to its wrong position, if I have moved it back down before.

None of this happens when I move my 5 Magic Nodes further up, like Before Files to Edit (where they are now).

Image

AlexMhr
Posts: 2
Joined: Sat Nov 06, 2010 10:29 am

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

Post by AlexMhr » Thu Jul 05, 2012 7:39 pm

New to magic nodes tried manual & docs please point me in the right direction if I've missed a read, but wondering if there's a more elegant way to group songs by decade say after displaying by genre. I've realized the functionality using <Year|Trim:3> (all my tag years are 4 digit) but it displays rather crappy (list will read "197" for 1970's, "198" for 1980's etc.). Wondering if there's a better way?

Current mask:
Genres\<Genre>\<Year|Trim:3>

Thanks in advance...
Alex

markeh
Posts: 250
Joined: Fri May 25, 2007 1:30 am

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

Post by markeh » Fri Jul 06, 2012 2:57 pm

I'm trying to list recently added albums. In one example, I'm using this mask:
40 recent Classical|Icon:Top level|Filter:Songs.IDAlbum IN (SELECT IDAlbum FROM Songs GROUP BY IDAlbum HAVING Count(TrackNumber) = Max(Cast(TrackNumber As integer)) AND Count(TrackNumber) > 3 AND Songs.Custom1 = 'c'ORDER BY Min(DateAdded) DESC LIMIT 40)\<Artist>\<Album>
The idea is the 40 most recently added classical albums. Some have been played, some never. Some are mp3, some flac.

I use "class" (songs.Custom1) = "c" for classical.

This doesn't seem to get the correct results. Only some albums are listed, but I'm not sure why some are included, and some are not. Originally I thought that the flac files are left out. But it may also be that albums without a date-last-played (because they have never been played) are being left out.

Anyone have any suggestions?

thnx,

(MORE: trying out RegExp, it appears that tracks with no LastPlayed date don't appear.... but I want them to anyway. So how do I change the mask to get this?? )





.

Guest

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

Post by Guest » Tue Jul 24, 2012 6:53 pm

I want to create a node that shows duplicates in my playlists.

Songs that have the same Title from the same Artists and that are in the same Playlist.

I have tried but just don't know SQL syntax well enough to get it.

Any help would be greatly appreciated.

FG

rrfpacker
Posts: 1041
Joined: Sat Jul 12, 2008 5:47 pm

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

Post by rrfpacker » Sun Aug 12, 2012 11:41 pm

ZvezdanD,

Is there a way to extract information from a node? I have a node you helped create (see below) and I would love to see the weighted calculation by album that it creates. Is that possible? Thanks.

<Group|Name:Album Ratings|Show tracks:No>\Albums with weighted avg. track rating >= 3 stars and at least 5 rated tracks|Icon:Top level|Filter:Songs.IDAlbum In (SELECT IDAlbum FROM Songs WHERE Rating >= 0 GROUP BY IDAlbum HAVING Sum(SongLength * Rating) / Sum(SongLength) >= 60 AND Count(Rating) >= 5)|Child of:Playlists|Position:Child\<Album|Sort by:Avg(Rating)|Statistic:Count(All)>

ZvezdanD
Posts: 3090
Joined: Thu Jun 08, 2006 7:40 pm

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

Post by ZvezdanD » Sun Aug 19, 2012 6:01 am

rrfpacker wrote:ZvezdanD,

Is there a way to extract information from a node? I have a node you helped create (see below) and I would love to see the weighted calculation by album that it creates. Is that possible? Thanks.

<Group|Name:Album Ratings|Show tracks:No>\Albums with weighted avg. track rating >= 3 stars and at least 5 rated tracks|Icon:Top level|Filter:Songs.IDAlbum In (SELECT IDAlbum FROM Songs WHERE Rating >= 0 GROUP BY IDAlbum HAVING Sum(SongLength * Rating) / Sum(SongLength) >= 60 AND Count(Rating) >= 5)|Child of:Playlists|Position:Child\<Album|Sort by:Avg(Rating)|Statistic:Count(All)>
I am not sure that understand what you mean by "extract information", neither I know why you need that. As it is told to you in the Help forum, the Album rating doesn't exist in the database as such, but my add-on calculates that value based on the tracks ratings. Those values are displayed for each album next to their captions in the tree panel when you expand the mentioned Magic node. The Magic Nodes add-on has not an option to export those values to some textual or similar file, but you have at least two another possibilities for that. The first one could be applied using the Tree Report add-on: you should select the mentioned Magic node and choose Tree Report option from the File menu - after you click on the Save As button you would get the .html file with the same data as they are displayed in the selected branch.

The another possibility to get album ratings into some file could be accomplished using the RegExp Find & Replace add-on: select all tracks from the wanted albums and choose the "Assign weighted average Rating of album to <Into Field>..." preset, then specify some unused custom field to store those values. After that you could use some report option from the File menu to get that custom field exported to the textual or .html file. If the built-in reports don't support export of that field, I suppose that there exists some add-on which is able to do that, e.g. Custom Report.
Magic Nodes 4.3.3 / 5.2 RegExp Find & Replace 4.4.9 / 5.2  Invert Selection/Select None 1.5.1  Export/Create Playlists for Child Nodes 4.1 / 5.4  Expand Child Nodes/Expand All 1.1.2  Event Logger 2.7  Filtered Statistics Report 1.6  Track Redirection & Synchronization 3.4.2  Restore/Synchronize Database 3.1.7 / 4.0  Find Currently Playing Track 1.3.2  Queue List 1.2.1  Add to Library on Play 1.0.1  Tree Report for Child Nodes 1.1.1  Update Location of Files in Database 1.4.3 / 2.2.2  Inherit Child Playlists 1.0.2  Add Currently Playing/Selected Track(s) to Playlist 1.1.2

ZvezdanD
Posts: 3090
Joined: Thu Jun 08, 2006 7:40 pm

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

Post by ZvezdanD » Sun Aug 19, 2012 6:11 am

Anamon wrote:There seems to be a weird bug with the order of tree nodes using Magic Nodes 4.2 on MM 4.0.6. I haven't used MM in a while, so I don't know about earlier versions. It seems to happen when trying to position a Magic Node after the last regular collection node.
Thank you for such detailed bug report. Unfortunately, the mentioned problem is not caused by my add-on, but because of the program itself, and I cannot do anything about it. This bug appears since MM v3.0 and MM developers are informed about it already several times in the past.
Magic Nodes 4.3.3 / 5.2 RegExp Find & Replace 4.4.9 / 5.2  Invert Selection/Select None 1.5.1  Export/Create Playlists for Child Nodes 4.1 / 5.4  Expand Child Nodes/Expand All 1.1.2  Event Logger 2.7  Filtered Statistics Report 1.6  Track Redirection & Synchronization 3.4.2  Restore/Synchronize Database 3.1.7 / 4.0  Find Currently Playing Track 1.3.2  Queue List 1.2.1  Add to Library on Play 1.0.1  Tree Report for Child Nodes 1.1.1  Update Location of Files in Database 1.4.3 / 2.2.2  Inherit Child Playlists 1.0.2  Add Currently Playing/Selected Track(s) to Playlist 1.1.2

rrfpacker
Posts: 1041
Joined: Sat Jul 12, 2008 5:47 pm

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

Post by rrfpacker » Sun Aug 19, 2012 9:05 pm

ZvezdanD wrote:
rrfpacker wrote:ZvezdanD,

Is there a way to extract information from a node? I have a node you helped create (see below) and I would love to see the weighted calculation by album that it creates. Is that possible? Thanks.

<Group|Name:Album Ratings|Show tracks:No>\Albums with weighted avg. track rating >= 3 stars and at least 5 rated tracks|Icon:Top level|Filter:Songs.IDAlbum In (SELECT IDAlbum FROM Songs WHERE Rating >= 0 GROUP BY IDAlbum HAVING Sum(SongLength * Rating) / Sum(SongLength) >= 60 AND Count(Rating) >= 5)|Child of:Playlists|Position:Child\<Album|Sort by:Avg(Rating)|Statistic:Count(All)>
I am not sure that understand what you mean by "extract information", neither I know why you need that. As it is told to you in the Help forum, the Album rating doesn't exist in the database as such, but my add-on calculates that value based on the tracks ratings. Those values are displayed for each album next to their captions in the tree panel when you expand the mentioned Magic node. The Magic Nodes add-on has not an option to export those values to some textual or similar file, but you have at least two another possibilities for that. The first one could be applied using the Tree Report add-on: you should select the mentioned Magic node and choose Tree Report option from the File menu - after you click on the Save As button you would get the .html file with the same data as they are displayed in the selected branch.

The another possibility to get album ratings into some file could be accomplished using the RegExp Find & Replace add-on: select all tracks from the wanted albums and choose the "Assign weighted average Rating of album to <Into Field>..." preset, then specify some unused custom field to store those values. After that you could use some report option from the File menu to get that custom field exported to the textual or .html file. If the built-in reports don't support export of that field, I suppose that there exists some add-on which is able to do that, e.g. Custom Report.

Thank you so much for your response, however, I won't be able to research/try either of your suggestions for about a week. I'm not ignoring you, will just be away from MM.

As to why I want to see the calculation, I just think it would be fun/interesting to see my albums ranked using MN weighted calculations. I can get most of what I want using Trixmoto's Advance Report, but I think your node calculations would be closer to actual album ratings. Thanks again.

ZvezdanD
Posts: 3090
Joined: Thu Jun 08, 2006 7:40 pm

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

Post by ZvezdanD » Mon Aug 20, 2012 9:09 am

rrfpacker wrote:
ZvezdanD wrote:
rrfpacker wrote:ZvezdanD,

Is there a way to extract information from a node? I have a node you helped create (see below) and I would love to see the weighted calculation by album that it creates. Is that possible? Thanks.

<Group|Name:Album Ratings|Show tracks:No>\Albums with weighted avg. track rating >= 3 stars and at least 5 rated tracks|Icon:Top level|Filter:Songs.IDAlbum In (SELECT IDAlbum FROM Songs WHERE Rating >= 0 GROUP BY IDAlbum HAVING Sum(SongLength * Rating) / Sum(SongLength) >= 60 AND Count(Rating) >= 5)|Child of:Playlists|Position:Child\<Album|Sort by:Avg(Rating)|Statistic:Count(All)>
I am not sure that understand what you mean by "extract information", neither I know why you need that. As it is told to you in the Help forum, the Album rating doesn't exist in the database as such, but my add-on calculates that value based on the tracks ratings. Those values are displayed for each album next to their captions in the tree panel when you expand the mentioned Magic node. The Magic Nodes add-on has not an option to export those values to some textual or similar file, but you have at least two another possibilities for that. The first one could be applied using the Tree Report add-on: you should select the mentioned Magic node and choose Tree Report option from the File menu - after you click on the Save As button you would get the .html file with the same data as they are displayed in the selected branch.

The another possibility to get album ratings into some file could be accomplished using the RegExp Find & Replace add-on: select all tracks from the wanted albums and choose the "Assign weighted average Rating of album to <Into Field>..." preset, then specify some unused custom field to store those values. After that you could use some report option from the File menu to get that custom field exported to the textual or .html file. If the built-in reports don't support export of that field, I suppose that there exists some add-on which is able to do that, e.g. Custom Report.

Thank you so much for your response, however, I won't be able to research/try either of your suggestions for about a week. I'm not ignoring you, will just be away from MM.

As to why I want to see the calculation, I just think it would be fun/interesting to see my albums ranked using MN weighted calculations. I can get most of what I want using Trixmoto's Advance Report, but I think your node calculations would be closer to actual album ratings. Thanks again.
Well, I still don't understand what you mean with "extract information". If you just want "to see" those values, you already could do that. Just expand the mentioned Magic node and you would see the album ratings in the front of each album.

However, with the mentioned mask those displayed values will not be weighted. I cannot remember when I helped you with that mask, most probably it was before I added WAvg function to this add-on for the Sort by qualifier. So, if you want to get album ratings weighted by tracks length you should replace Avg with WAvg.
Magic Nodes 4.3.3 / 5.2 RegExp Find & Replace 4.4.9 / 5.2  Invert Selection/Select None 1.5.1  Export/Create Playlists for Child Nodes 4.1 / 5.4  Expand Child Nodes/Expand All 1.1.2  Event Logger 2.7  Filtered Statistics Report 1.6  Track Redirection & Synchronization 3.4.2  Restore/Synchronize Database 3.1.7 / 4.0  Find Currently Playing Track 1.3.2  Queue List 1.2.1  Add to Library on Play 1.0.1  Tree Report for Child Nodes 1.1.1  Update Location of Files in Database 1.4.3 / 2.2.2  Inherit Child Playlists 1.0.2  Add Currently Playing/Selected Track(s) to Playlist 1.1.2

rrfpacker
Posts: 1041
Joined: Sat Jul 12, 2008 5:47 pm

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

Post by rrfpacker » Mon Aug 20, 2012 9:08 pm

Ok. I'll check in to changing the avg to WAvg in a few days.

When I expand the node, I see the number of tracks in parenthesis, not average.

jonisaksson
Posts: 42
Joined: Fri Apr 20, 2007 11:02 am

Error #-214748113 –SongsDB.SDBStringlist

Post by jonisaksson » Wed Aug 22, 2012 3:49 am

Hello,

When ever I start mediamonkey I get an error message stating

"Error #-214748113 –SongsDB.SDBStringlist
List index out of bounds (-1)
File: “C:\Program Files (x86)\MediaMonkey\Scripts\Auto\MagicNodes.vbs, Line 13846, Column: 12"


If I open MagicNodes.vbs in notepad and goto line 13846, then that line says "sTreeItem = oKeyList.Item(oKeyList.Count - 1)"

I am running MediaMonkey v 4.0.6.1501

If I click OK, everything seems to work as normal but a bit annoying to have that error message

Many thanks
Jon
Last edited by Lowlander on Wed Aug 22, 2012 10:02 am, edited 1 time in total.
Reason: Merged with existing post

Post Reply