Overhauled Search in Roon

Yeah, have been for years. I suppose it could be failing, but I really doubt it. Not sure how a failing switch could affect adding a Qobuz album to my Library, but I guess anything’s possible.

This whole SNAFU, the Search problems and not being able to add the album to the library, only occurs (so far) with this one album. I added three other albums last night without any problems.

This morning, I checked last night’s Backup result and there was no message about a corrupted Library. So, unless that logic is not working, my library would seem to be OK.

It wouldn’t, was just trying to figure out if there was something that could cause it.

Seems like it just happens for unknown reasons.

1 Like

So my post was moved to this mistitled thread. The title for this thread should be: Overhauled but Still Badly Broken Search in Roon

Additionally there needs to be a new thread about Roon not correctly adding items from Tidal and Qobuz to one’s music library.

But hey Valance is great!!! :wink:


The thing is that this problem will go right down a rat hole along with all the other Search problems and if there is a resolution users will never know what it was.

As far as indicating that a selection has been added to one’s Library when, in fact, it hasn’t seems like something easy to fix. Still, the solution is probably going to go on a lengthening list of Roon’s bugs to be addressed at some unspecified future time.


The real problem is the fact that Roon and Qobuz/Tidal are partners. One side’s programmers say “hey it’s not our code that’s the problem, it’s their code” and of course the other side says exactly the same thing. Therefore, there is a lot of finger pointing and nothing gets fixed.

Roon software knows when an album has truly been added to one’s library because the add icon stops spinning. Within that code is where the ‘added’ message should be generated.

I stand by my previous post. A lot of finger pointing and no solutions.

Yes, in general I agree with your post, but in this particular instance the fault is in Roon’s code and I hope they see fit to fix it, soon.

I find that besides network issues, the other main source of Roon problems tends to be the Roon/Qobuz/Tidal interface. And since these Roon/Qobuz/Tidal issues tend to not be quickly resolved by Roon I think finger pointing. In the tech world it’s always someone else’s code/equipment/operating system causing the trouble. I guess that’s why people love Apple.

An example search that went wrong. Was looking for the track ‘Into Dust’ by Mazzy Starr. They are not in my library, I have Tidal.

Searching first for Artist and Track:

Searching next for Artist, seems to find the wrong one:

Searching next for Track, finds what I was looking for:

@Anthony_B , it appears you’ve spelled “Mazzy Star” incorrectly in your original searches?


Oh dear, you are correct, well spotted, one ‘r’ too many! Alcohol intake has absolutely nothing to do with this error honestly…but even so it highlights Roon’s intolerance of typos.

‘Mazzy Starr Into Dust’ is pretty close to what I was after…


It happens to all of us. :wink: And I can understand if Roon is looking for “starr”, and not finding it.

If the artist was named “Mazzy Starr” and you searched for “Mazzy Star”, then Roon should have found it (but not vice-versa).

Works well for me:


1 Like

This one should work now. Let me know if you still experience the issue.

1 Like

But if you type Mazzy Starr into dust with the extra R, it still finds it in Qobuz and Spotify but fails on Apple Music and Tidal. Hoping roon can improve their search to overcome spelling errors.

1 Like

We live in hope Mike.

My recurring issue with Search is this: I type in my inquiry and invariably Roon says “no results”. Then I add a space after the inquiry, and the search correctly finds it.


…and now, one day later, the search is working fine. :face_with_raised_eyebrow:

1 Like

solar flares.
That is my excuse for everything I can’t explain.

May it serve you well. :slight_smile:


An ampersand seems to cause issues that I wouldn’t have expected from a cloud based algorithm.

This album seems only to be found because there is a track with “and”on it in its title - itself impressive - but the lack of parsing “&” as “and” and running a parallel search for this seems awry.

Top hit in Spotify