MediaMonkey forum

Playlist criteria Any text does not allow ; multiple entries

ie Lyrics contains Lyricator ; Instrumental.... will show tracks where the Lyrics Field contains Instrumental AND / OR Lyricator in it.
but Any text contains Lyricator ; Instrumental....will only show tracks that contain BOTH

Is this a bug, can it be changed?

You can use nested criteria like this: https://www.dropbox.com/s/h7tobvpm4k377 ... 4.png?dl=0

Or alternativelly Any text contains word1 OR word2 : https://www.dropbox.com/s/ybb2lccod78yu ... 6.png?dl=0

Aha! so use "OR" instead of separating with ;

That's what I need

Ludek wrote: ↑Thu Jul 08, 2021 5:49 am You can use nested criteria like this: https://www.dropbox.com/s/h7tobvpm4k377 ... 4.png?dl=0

Or alternativelly Any text contains word1 OR word2 : https://www.dropbox.com/s/ybb2lccod78yu ... 6.png?dl=0

The nested criteria facility is good. I didn't know that.

It seems needlessly confusing that

• An ANYTEXT search uses OR as an operator when searching, but in other tags (AlbumArtist, Album, etc) the "or" operator is a semi-colon ... and in both cases the alternate usage is invalid

And I can't find either of these facilities in the online help.

Yes, the usage of OR and ; is currently inconsistent and not officially supported AFAIK.
It is just that ANYTEXT is more like searching via the search bar -- so the OR operator works like in case of the search bar usage.

So usage of the nested criteria is the suggested/offical way (and should be documented -- if not already).

Ludek wrote: ↑Fri Jul 09, 2021 4:56 am Yes, the usage of OR and ; is currently inconsistent and not officially supported AFAIK.
It is just that ANYTEXT is more like searching via the search bar -- so the OR operator works like in case of the search bar usage.

So usage of the nested criteria is the suggested/offical way (and should be documented -- if not already).

It's not documented (yet). Documentation of this area is virtually just a placeholder.
The closest coverage is here, which would lead one to assume that OR and ; are equivalent, because that is what it says.

I realise that this is not a "now" issue, but should be a sometime issue IMO.
I think that the concept of an "official way" is wishful thinking on your part. It is contradicted by the documentation, also by the reasonable expectations of the user. ... A nested criteria is more complex and more ugly than a simple OR operator, which works in MM5 in some places.

Tracking as https://www.ventismedia.com/mantis/view.php?id=18127