MediaMonkey forum

I realized that what takes a lot of time is determining which tracks don't have a cover at all. It may possible to improve the performance, but for now the following node should be very fast:
To see which files don't have an associated cover you can use the regular files to edit/unkown cover MM node.

You may be right MM only supports one type of lyrics, I am not exactly sure what it does support lyric-wise.

I do have access 2000, but thats not required for MM or MagicNodes, unless you are wanting me to test something?

I tried the node you indicated, and it does not seem any faster. The main delay comes when you first expand the Cover-Storage node, after its expanded it performs at a more normal speed.

I suspect it is MM trying to read the coverstorage from every file, I don't think cover-storage is an actual MM database field is it?

Teknojnky wrote:I suspect it is MM trying to read the coverstorage from every file, I don't think cover-storage is an actual MM database field is it?

It is an actual database field (CoverStorage in the Covers table). MN works only with the database, i.e. it never accesses tracks directly. Now I think it's slow because it is a many-to-many relation, but I will investigate further.

I was asking if you had Access for testing, but for now it's not needed.

Hi... hope you can help me. Im trying to get something done that i fear is too much for me

I´ll explain to you what i want to get:

I want to use the 3 Custom to make a classified tree of genres. This way i call Custom1 EstiloA , Custom2 EstiloB and Custom3 EstiloC.

im using this code: But some genres have more subgenres than others (in my own classification) so some tracks have the three custom used (example: Rock->Hard Rock->Trad Rock) and other tracks have only 2 custom used (example: Rock->Folk Rock) and this later songs will have an ugly "Unknown" node-tree between EstiloB (custom2) and the album artist name.

What i want is some code that strips out the EstiloC (custom3) when there´s nothing written in it. I tried this with no luck: ¿Any clue? Please i need your help. Big thanks in advance.

(Hope my english and explanation are understandable enough)

keiju, what you want is perfectly clear but it's not currently possible. I'll see whether it can be implemented in the next version.

Is there a magic nodes field to access "Album Comment"?

And if not, would it be possible to get one added in for the next update?

This field is available by going to the 'properties' of a standard 'album' node.

Teknojnky wrote:Is there a magic nodes field to access "Album Comment"?

And if not, would it be possible to get one added in for the next update?

This field is available by going to the 'properties' of a standard 'album' node.

This will be added in the next version. Thanks for noticing.

Pablo!

Just popping in to say i'm glad you're back and i'm looking forward to the next version of this great script!

PS Thanks for the note.

/Bex

Pablo wrote:keiju, what you want is perfectly clear but it's not currently possible. I'll see whether it can be implemented in the next version.

Oh, ok Pablo. BIG THANKS Anyway for the answer and the great script.

Muchas gracias por la ayuda (i hope u can read spanish)

How do I make nodes that are boolean combinations?

For example, I want to create the following nodes:
- has art of type 'Cover' and 'not specified'
- has Cover art and does not have 'not specified' art
- has 'not specified' art but not 'Cover' art

- has lyrics but no cover art
- has any kind of art but no lyrics
- has lyrics and 'cover' art but not 'not specified' art

Thanks!

Hi guys.

I am trying to make some magic nodes like this...

Popular Albums (past week)
Popular Albums (past month)

etc
Each node should show the albums which has had the most plays over the past week, month, etc.

I've had a crack and I don't understand why this brings up an SQL error?

Popular Albums (past week)|filter:days since last played <= 7\<album|sort by:sum(played)|sort order:desc|top:20|unknown:no>

Any guidance would be appreciated

i'm sorry if this has already been asked, seems simple, but just haven't found the answer in my searching yet.

When MM starts, I want the Magic Nodes node to start out collapsed. How do I do that?

Thanks.

Anonymous wrote:How do I make nodes that are boolean combinations?

For example, I want to create the following nodes:
- has art of type 'Cover' and 'not specified'
- has Cover art and does not have 'not specified' art
- has 'not specified' art but not 'Cover' art

- has lyrics but no cover art
- has any kind of art but no lyrics
- has lyrics and 'cover' art but not 'not specified' art

Thanks!

You would basically need to use SQL filters for this. Some of those are tricky and the resulting nodes may be quite slow, but I can give it a try.

Anonymous wrote:
I've had a crack and I don't understand why this brings up an SQL error?

Popular Albums (past week)|filter:days since last played <= 7\<album|sort by:sum(played)|sort order:desc|top:20|unknown:no>

Any guidance would be appreciated

Well, the filter: qualifier sometimes works and sometimes doesn't. In really complicated nodes like this it usually will not work. I expect to improve the filter: qualifier but I'm afraid it'll continue to be hit or miss just because of the way MM and the script are structured.

confyoosed wrote:i'm sorry if this has already been asked, seems simple, but just haven't found the answer in my searching yet.

When MM starts, I want the Magic Nodes node to start out collapsed. How do I do that?

Thanks.

It's not possible, but I will keep it in mind for a future version (may be some of the other scripts that allow tu customize and tweak MM could be of help).