Using Boolean parameters in seach

Hello all,

Perhaps it’s me, but I find the search engine in Roon bothersome. If I try to search for a group/song/conductor etc. and I’m not sure of the correct name/spelling I like to use things like part of name * or Booleans like AND / OR / NOT or like in Google the minus sign (not). Somehow Roon does not allow me to use these. And when I forget eg an " over an a, it misfires. How can we make the search engine intelligent (or am I in the wrong?)

1 Like

For boolean:

And for good measure :slight_smile:

As for fuzzy search with typos etc: There has been ongoing work on search for literally years and it has become better (even sometimes allowing the odd typo now) but there is a long way to go still. There are endless discussions in older threads.

2 Likes

@Raphael_Gallis - I agree that there is a lot of opportunity to improve Roon’s search, but one handy thing to be aware of (and maybe you already are!) that’s not at all intuitive is that any selected filter criteria in purple can be "NOT"d by clicking on it, and it will appear in red, e.g.:

image

3 Likes

Roon is a piece of music software not a super refined search engine.

Maybe you need t play music through Google ? :smiling_imp: :rofl:

At least it would find what you’re actually looking for.
Roon has its own ideas on that unfortunately. It is the worst search function of any app I have used. Tries to do it all for you but fails miserably.

I agree, I don’t defend it but I was just pointing out the degree of specialization required.

After all its searching 110 million potential tracks for a Tidal user , no mean feat. My coding experience is limited to T-SQL where some wild cards are possible Like ‘%Text%’

I rarely if ever use search and certainly not for complex string searches , maybe the odd Artist where a direct match is possible.

There are many ways of skiing the Roon Cat :smiling_imp: