· Something’s not working in the Roon interface (buttons, displays, lyrics, etc.)
Describe the issue
When I filter in Tracks delete errors out and says to remove a focus even though no focus has been selected. So you literally can’t search for a group of tracks you don’t want for example by artist and then delete them. Can’t delete from library? If I navigate through a HUGE list of non filtered tracks, it sometimes takes 2 or 3 attempts to remove. No errors here, track disappears then reappears after a delay, so you almost miss the fact that it reappeared. Frustrating enough that I will be canceling if this can’t be resolved. These are basic functions that I expect to work.
Describe your network setup
Just fix your bugs. My network is fine, and also hasn’t changed since this latest issue
You are seeing the “Try removing some focus criteria” message because of the active text filter: your screenshot shows you are actively filtering by Album Artist using the term “morg”. Roon treats all active filtering as ‘Focus’ criteria.
Solution: Simply click the blue ‘x’ next to the search term “morg” in the ‘Album artist’ filter to clear it.
Regarding the deletion from the library, you can use the Ban feature:
Roon offers the Ban function to hide content without touching your files.
Ban Album/Track/Artist: You can use the three-dot menu and select "Ban this album" (or track/artist).
Result: This permanently hides the content from your library view, discovery features (like Roon Radio), and recommendations.
None of that really addresses the problem. My bad for misunderstanding that something called a filter on the screen in the app was actually a focus, but that has nothing to do with the problem. I would think it would be a very common feature to search for a group of tracks and remove them from your library. This is all I’m trying to do. They are not local files, quobuz and tidal. I do not want to ban them. I simply want “remove from library” to work. Even if you dont search first, which is typically needed, when I remove the tracks they just reappear after a short delay. Removing multiple time,3 or 4, often does finally remove them.
If they are not local files or tracks added from a streaming source; then what are they?
If these are ghost stubs, left over from you removing the local files; then you can clean them up by going to Settings/ Library/Library Maintenance “Clean up Library”. Same, if they were favorites from a streaming service that you have removed as a favorite.
I just wanted to note that if those are local tracks, then deleting them from the library will remove/delete the actual files from the drive. And, if those are streaming tracks, then removing them from the library will remove them as favorites on the streaming source.
There is no “Remove from Library” feature that deletes files from disk or from your streaming services. We have two separate objects for streaming services and for the local files in your library.
Here’s how it works in Roon:
Local files: you can use the Ban option to hide them from your library (the files stay on disk).
Streaming services (TIDAL/Qobuz/KKBOX): you can unfavorite tracks or albums directly in Roon or streaming service — this action syncs both ways with your streaming account.
If you meant a dedicated “Remove from Library” button that hides or unfavories items depending on their source, please describe what behavior you’d expect for each case so we can forward it as feedback to the product team.
If you have any problems with the unfavoriting tracks from the streaming services, would you kindly share some recent examples with the timestamp and track name when it was unfavorited and appears again in your library?
the tracks I’m trying to remove from library are Qobuz or Tidal. When I filter (focus I guess), it throws an error when selecting “remove from library”. If I don’t search, and scroll and scroll and scoll and scroll down to the “M’s”, and then select the tracks to remove, it doesn’t throw an error-the tracks disappear and then reappear after a short (about 10 seconds) delay. If I repeat that 3 or 4 times, it does finally delete.
I’m not sure how more specific I can be, seems a simple issue. Please assume in your response that I am familliar with the basic functions of Roon.
As far as the latest response, there is a button called “remove from library”. I’m a bit confused the message stating that function isn’t there. It shows as “add to library” if the track isn’t yet part of your library.
Oh, forgot-for what it’s worth, I’m trying to remove Morgan Wallen from my library. Multiple tracks from a single album, but the behavior is not specific to this. Traces back to the root cause of Profiles doing nothingseparate, so my GF is constantly accidentally adding to my library crap I don’t’ want to hear.
I am not that familiar with the tracks view. I rarely use it. But the comments seem to be saying that you cannot do what you want to do from the tracks view. TBH your 3/4 attempts before an unsuccessful deletion sounds more like a usability error edge case that roon will want to prevent in the future rather than a feature.
Thank you for the update. I have tested both scenarios with removing from my tracks with search and without, and everything is running as expected.
To review your inquiry in more detail, could you please upload a copy of your Roon database? This will help us better understand your current configuration.
sorry for delay, I will have this done this upcoming weekend. out of town with work travel this week, won’t have access to the system till I get home.
thx, Nate
We’ve discussed this with our senior QA and development teams. The team is investigating some possibilities here and, as soon as that investigation is complete, we’ll be sure to follow up ASAP.
You have our apologies for the trouble here, and we’ve greatly appreciated your patience as we continue investigating this tricky issue. We’ll be in touch as soon as we can.
I wanted to touch base with some good news, which is that our technical team has been able to reproduce this behavior and we’ve opened up a bug report with our developers.
While I can’t say for certain when this bug will be fixed, getting things reproduced in-house is a critical first step, and I will keep this thread up to date as the team passes along feedback and work begins to get this resolved. Thanks again for the report!
