I used to have this all the time, drove me absolutely mad.
Recently I got so sick of the issue (among other things), I started changing things in my setup piece by piece to figure out what happened.
When I switched from NAS to an ssd directly connected to the core this issue was eliminated.
That issue is particularly annoying because in my experience it didn’t tell me it failed to add the album to my library. So a week later I’d discover that an album I added and liked was actually still not in my library.
Exactly. The message that an album was added shouldn’t be displayed until the album is actually added. Just another logic problem within Roon’s code that should be easy to fix if someone tried.
Thanks for the suggestion, but my music files are on a 2nd drive in my ROCK NUC.
Interesting, the other change I made was introducing a network switch but from testing it made a massive difference to latency but didn’t seem to solve this issue.
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.
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 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.
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…
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.
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.