MediaMonkey forum

Thanks for the report.

Is there a way to create a node that will compare one field to another?
I want to compare a custom field, 'Folders', to the Path.
ex.
Path = F:\AMI.A1.0P\GenreID Greatest Band Ever\ReleaseID No Other Album Like It\The Song That Everybody Loves.flac

Folders = \AMI.A1.0P\GenreID Greatest Band Ever\ReleaseID No Other Album Like It\

1. Only the 'folder levels' would be matched.
2. The above example is 'ideally' how I want everything to match, but if
there are any 'differences' between the two those files would be shown in the file list.

Possible? Can fields be adjusted in MN, or only numbers? Maybe not with all fields?

MMFrLife wrote: ↑Sat Jun 19, 2021 1:50 pm Is there a way to create a node that will compare one field to another?

Maybe you could try the next Filter (assuming that you named Custom1 field as "Folders"):
<Path> LIKE '%' || <Custom1> || '%'
or (if data in your custom field always ends with the "\"):
<Folder> LIKE '%' || <Custom1>

Notice that <Folder> is a built-in MN field. You could write <Folders> instead of <Custom1>, but it is not recommended to use custom names for tags in masks.

MMFrLife wrote: ↑Sat Jun 19, 2021 1:50 pm Can fields be adjusted in MN, or only numbers?

No, MN supports only numbers and strings in the adjustment dialogs.

The options you gave appear to only show fields that "ideally" match, so to clarify...

MMFrLife wrote:2. The above example is 'ideally' how I want everything to match, but if
there are any 'differences' between the two those files would be shown in the file list.

The example is how I wish them to be, but I 'only' want the filter to show the files with 'differences'
between the fields. That way I can correct the <Folders> field to match the folder levels in the path
so they 'do not' show up as a match in the node.

One example of an obvious node match would be if <Folders> is empty (that should also show in the file list).
It would correctly match according to the node filter, but not match ideally.
I get 2, 530 matches and they all have something in the Folders field. I'm pretty certain there should be some that are empty.

Let me know if that is what you thought/created and I will try to analyze more carefully to see if I missed something.

MMFrLife wrote: ↑Sat Jun 19, 2021 5:41 pm I 'only' want the filter to show the files with 'differences'
between the fields.

Just replace LIKE with NOT LIKE.

hmmm...

With NOT LIKE it now shows both kinds of differences.
1. <Folders> is filled but contains some minor differences such as with Release ID, like, (A00_ vs B01_, etc)
2. <Folders> is different because it is empty.

3. Unfortunately, it still shows examples (if not all?) of folder levels that are exactly the same.

I'm guessing it is showing the ones that are the same because it is detecting the ends of the path as
being different from what is in <Folders> ('F:\' and filename).

Is the filter written to filter out both ends of the path when attempting to match?
What do the double bars mean '||' and apostrophes that 'enclose' the percent sign '%' as opposed to one side of it?

MMFrLife wrote: ↑Sun Jun 20, 2021 12:03 pm With NOT LIKE it now shows both kinds of differences.
1. <Folders> is filled but contains some minor differences such as with Release ID, like, (A00_ vs B01_, etc)
2. <Folders> is different because it is empty.

That was a request, right?

MMFrLife wrote: ↑Sun Jun 20, 2021 12:03 pm 3. Unfortunately, it still shows examples (if not all?) of folder levels that are exactly the same.

I'm guessing it is showing the ones that are the same because it is detecting the ends of the path as
being different from what is in <Folders> ('F:\' and filename).

Examples, please.

MMFrLife wrote: ↑Sun Jun 20, 2021 12:03 pm Is the filter written to filter out both ends of the path when attempting to match?

Yes, the first one filters out both ends. The second one filters out only the beginning, which is why I said that you need data in the custom field ending with "\".

MMFrLife wrote: ↑Sun Jun 20, 2021 12:03 pm What do the double bars mean '||' and apostrophes that 'enclose' the percent sign '%' as opposed to one side of it?

The double bars is SQL operator for concatenation, the apostrophes are used in SQL to enclose strings, the percent sign is a wildcard character similar to * in DOS.

Okay, I'm getting excited now.
Upon more careful analysis, it looks like it works.

A couple of the ones that looked the same only have a one character difference and my brain just didn't register it a first.

This will save me a TON of time not having to track down mistakes and things that are/or might be too many to remember.

The idea is to 'select all' and just correct them at once, but to make sure it is optimally working I will correct them in large groupings. I can look over them more carefully while still being quick now that I know the areas where most of the discrepancies tend to be. It is still a lot faster than manually hunting them all down!

Just to be sure my thinking is correct:
I'm using, <Path> NOT LIKE '%' || <Folders> || '%'
(I want <Folders> to end with the slash, and most, if not all, do. I'm using this one because if it is missing it should also be detected and I can correct it, right?)

MMFrLife wrote: ↑Sun Jun 20, 2021 1:57 pm I'm using, <Path> NOT LIKE '%' || <Folders> || '%'
(I want <Folders> to end with the slash, and most, if not all, do. I'm using this one because if it is missing it should also be detected and I can correct it, right?)

Yes, that one should also detect <Folders> without the "\" on the end.

However, if you want to find out files with <Folders> without "\" on the end to correct them, you could use this Filter:
SubStr(<Folders>, -1, 1) <> '\'

But, as I said, I don't recommend using custom names for tags. It is better if you type <CustomX> instead of <Folders>, where X is between 1 and 5, depending on which one you renamed to Folders.

Morning. I'm struggling with something which I think ought to be really simple to do.

I want to create a new node which shows me unplayed tracks with the genre "Classical" with subnodes for each track length showing track count for each length. What I have so far just shows me subnodes in minutes and really want is to then have subnodes underneath that show length in minutes: seconds.

I note that the pdf manual says:

"Length: This is displayed as nn to nn+1 minutes as a node but as [[hours:]minutes:]seconds as a Statistic:. When used in an
expression it is a numeric value in milliseconds."

I'm sure that this is possible, but I can't find out how to do it. Any advice?

Here's the code which displays the following Nodes on my tree:
PORTFOLIO • (Collected Works)|Child of:Library|Filter:<Grouping> LIKE '%PORTFOLIO%'|Icon:13|Position:First child\<Original artist|Statistic:Count(Original title)>\<Title>

This is an example of what is shown:
Bach, J.S. (10 original titles)
Mussorgsky, Modest (1 original title)

Is there a way to have the Nodes display this....
Bach, J.S. (10 original titles)
Mussorgsky, Modest

Basically, I don't want it to tell me there is only 1 original title -- I already know that just because the name of the Artist shows up. I only want it to show if there are 2 or more original titles. Can this be done, and if so, where and how...?

Thanks.

TWKArtist wrote: ↑Wed Oct 20, 2021 4:04 pm I only want it to show if there are 2 or more original titles. Can this be done, and if so, where and how...?

The Statistics values cannot be conditionally shown/hidden. However, you could create a node which will display only the original artists that have 2 or more original titles using the Filter qualifier applied on the Original artist node level (in MN v5+).

OK. I'll try that.

Thanks, Zvezdan!

Hi Zvezdan...!

A new question.
I have entries in the "Quality" field of MM which read things like "KEYS_Piano" - "KEYS_Organ" - "KEYS_Sampler" etc.

I can make a node where all of these are listed, but what I'd like to try is having one node where the word "KEYS" is listed and then it has a number of sub-nodes with "Piano" - "Organ" - "Sampler" and so on. The reason is to have the sub-node "Piano" of the node "KEYS" then hold all music tracks with the "PIANO_Keys" quality, regardless of what else is there (since it's a multi-field).

I've tried any combination of split settings and nothing seems to work. Any ideas....?

>>TImK

TWKArtist wrote: ↑Mon Nov 22, 2021 2:53 pm I've tried any combination of split settings and nothing seems to work. Any ideas....?

If you have a fixed string on the beginning, e.g. "KEYS_", maybe you could try the first node level using Trim = 4, then the second level using Substr. start = 6 and Substr. lenght = 0. Or, in this example, you could just use Right of = "KEYS_" for the second level.