[Pflichtfeld]

In English, the other dropdowns say "Any", meaning any value will be considered a match. The idea was that, if you selected specific values, those would be listed, otherwise any value would be considered a match, hence the wording. Saying "None" makes sense if we think of it as "No filter is selected", but it doesn't really make sense in the context of "None will be matched".  ...  My own personal opinion is that I think I prefer "Any" when nothing is selected and "All" when all values are selected, but I don't know if that's confusing to some people, as I think some people may expect to see something more like "None", meaning nothing is selected.

Mike

Thanks Mike.
I originally was pointing to the inconsistent behaviour  of the collection-field compared to the other fields.

But then:
what you write makes no difference for me in the result of the filter: If one searches ANY or ALL, that is the same match in search, isn't it? Or did I understand something wrong?
But, if ANY (with having selected no entry) and ALL (with having selected all entries) leads to the same filter-result, that is an oxymoron, mathematically wrong and not logical.
But I can see your problem: How to treat the search with the item NOTHING? Imho the result should differ from a ALL-filter, shouldn't it?
I would expect (and propose), that a NOTHING-filter shows all songs, which actually have NO ENTRY in this field. This would be mathematically correct and for some users probably helpful:
"Are there any songs, where I forgot to assign a specific value in this field?", "Show me all songs without an entry in field A but with other filters in field B, C..."
BTW: The default for this dropdowns should be ALL. And opening a dropdown with ALL should show all the list-entries selected. This would make it clear.
Your interpretation with ANY and ALL confuses imho.

But definitely: A wonderful program!