Windows 10, i3-12100, 8GB RAM
All library on HDD on that PC.
Networking Gear & Setup Details
Speedport 2i as router
Roon Core is connected with Bluesound Node through the router via Ethernet.
Connected Audio Devices
Wired connected (ethernet with Bluesound Node) which does all the playback.
Wireless connection to Android phone and laptop, just for occasional playback and as a remote for the Roon that playbacks on Bluesound Node.
Number of Tracks in Library
~9.000 tracks
Description of Issue
Latest release of Roon on all machines.
When I delete tracks from an album (usually from the Queue), it breaks the order of the tracks on the album. Each track that gets deleted gets replaced with the last track as in a group of tracks. Every other track that I delete, adds another duplicate of the same last song as part of the group.
In order to solve this, I use fix track grouping, but this shouldn’t happen in the first place.
I don’t know as I would never delete a track from an album. Maybe it serves as a workaround to hide them? (Or maybe it still messes up the order, I don’t know, but maybe worth trying)
I don’t think this is a bug as such. If you don’t want to hear certain tracks on an album when you play the album, then it is better to ban the tracks by clicking/touching the icon on the track twice to get the icon to indicate that it is banned. Don’t delete the tracks themselves.
Sorry, but this is not an answer.
You don’t tell your users how to use your product, but you adapt to their needs.
So, the behavior that I showed you on the screenshot, looks to you like a normal working behavior? Replicating the same track and grouping them under a fictional group?
This definitely is a bug, because there are some cases (I don’t understand when) but rarely, I will delete a track and it will just remove the track from the list of the album’s tracks, as expected. There is no way for me to reproduce the expected behavior, but I can replicate the non-expected.
I have my own personal collection and not a public database. I want to be able to delete tracks that I hate because all these tracks accumulate in collections of thousands of songs. That makes it unreasonable to keep them. A lot of space is needed for their storage and their backups. I have them on my CDs and vinyls if I need to revisit them.
Note: if you don’t want the users to delete tracks, then why on earth do you have this as am option? I really like this functionality and that’s the way I’ve been using Roon and I will keep using Roon.
And since these are your own albums, and not albums recognised by Roon, what happens if your simply rescan the album after you’ve deleted the tracks that no longer interest you?
Sorry mate. That was my mistake. You have always been very helpful in every step all this time through various threads. I just hit the reply on wrong user.
I am deeply sorry for this.
You solution is a possible one, but still I believe that the bug still stands, don’t you?
I don’t mean that I have any non-Roon recognized albums. I have my CDs that Roon recognizes. All I am saying is that there is no point in keeping all the tracks of some of these albums, since they are part of my own personal collection. They are not meant to be shared publicly, so this collection’s purpose is to only satisfy myself. I hope that this clears things up.
So, to answer your question, if I rescan any of these albums, or use the fix track grouping, it’s going to be fixed.
Again, these are ways to fix something “wrong” in my eyes. And that’s why I am calling this a bug.
I am just confused. Am I the only one considering this as a bug?
While I don’t know if deleting tracks from an album is the best way to go about it (I would expect that probably something gets messed up), I think I also agree that it shouldn’t break track grouping if you do
I suspect that you are. You are deliberately breaking the identification of albums known to Roon, so you’re on your own here. If you don’t want to hear the tracks, then ban them. Storage is cheap these days, so personally I wouldn’t nitpick over deleting tracks in order to save a modicum of space.
It is still happening though.
Punishing me almost every time I delete a song. (I cannot understand why some rare time it’s not happening.)
Mr. Moderator, before telling me that this is a problem of my own, just consider that from the 3 people in the conversation, 2 of them believe that this should not behave like this.
Is there a difference if you delete from the queue page and the actual album page?
If you delete a track from the file system, does it have the same effect?
This may just be a visual artifact, instead of using fix track grouping, if you just restart Roonserver does it clear the error?
Is it a bug? Something is getting messed up and not working right. Is it a big issue? For you, yes, for the rest of Roon users, probably not.
Most fellow users I know that like to “de-dup”, do so outside of Roon and using some type of de-duping software to help automate the process. I have not heard of any of them having your issues. To be clear, they… 1. Shut off Roon. 2. Remove the files from the storage location 3. Turn Roon back on.
Don’t forget after you have deleted the files, to go to Settings/Library and use the Clean Library options to remove the database entries for the files you have deleted. Cluttering up your database is not good.
Personally, imho, what should happen is the removal of the ability to delete files at all from Roon. It is an exception to their “We don’t touch your files at all” goal, and a data security risk in that anyone can pick up a Roon remote and delete. I know many people who have had their kids, friends, and spouses delete large parts of their library.
Sorry for the late response, but I’ve been away.
And thank you for this response and especially this part, it’s been the most useful.
I really appreciate it.
Thank you for your patience here. There seems to have been a misunderstanding concerning what storage practices and file grooming will interfere with Roon’s identification.
If you have any additional questions please let us know and Tech Support can answer them. Otherwise, consider the advice helpfully shared by our expert moderators above to be the best path forward. You’ll need to adjust your habits slightly for storing music to get the most out of Roon. We’re here to help with that!
Thank you for your kind message.
It’s good that I know how to handle this, even though it feels like a bug to my eyes. At least I know now what is Roon’s way to a workaround.
I would really hope to fix this someday, but until that day comes, I guess I have a way to work this out thanks to @Rugby who really has taken into account my use case.
@Rugby
I changed at the same time with your method (1. Shut off Roon. 2. Remove the files from the storage location 3. Turn Roon back on.) two albums’ tracks.
The first one worked like a charm.
Latest release of Roon on all machines.
icon on the track twice to get the 
icon to indicate that it is banned. Don’t delete the tracks themselves.
