· I think I've found a bug while updating to the latest version of Roon. There seems to be a bug with Roon tags for tracks. I previously had Roon 2.65 on a Mac mini m4 and just updated to the latest version of Roon. My local files are intact but when I looked at my Tags, they mostly updated fine but ANY tagged track keeps saying "unavailable". I've tracked this down and it seems like if I originally tag a track it say "unavailable" but the rest of the album is fine. If I had tagged the entire album as a tag then no issues. I've tried to disable my local storage and sign out of Qobuz, then restart Roon (restart the Mac mini) and enable storage and log back into Qobuz but the tagged tracks still say "unavailable".
I noticed the pattern after noticing a favorite tagged track was in both a tag named "Jazz" and the same track tagged in "Soul". Please let the developers know and if you have a workaround I'd love to try it.
Tell us about your home network
· Mac mini m4 hardwired to Eero Pro 6 via an English Electric EE8 switch.
Thank you for the detailed report and for narrowing down the pattern — individual tagged tracks showing as “unavailable” while full album tags work correctly is a clear and reproducible scenario that we want to investigate properly.
We have flagged this for our QA team to look into. In the meantime, could you help us with a couple of additional details:
Are the affected "unavailable" tracks local files, Qobuz, or a mix of both?
Does the issue affect all individually tagged tracks, or only specific ones?
We will follow up once we have more information from the team.
1 . (Seems to be both. I found at least one track/album that is stored locally that I own in a folder but the majority of them are from Qobuz)
It does seem to affect all tagged tracks. I thought it was only the ones that were “favorites” but I found some that weren’t “favorites” but were tagged and are now “unavailable”. I did find an example where I didn’t import the entire album but only 1 track from an album and tagged it but it’s also “unavailable”
When Roon loads a tag that contains an individual track (not a full album), it tries to look up the album that track belongs to. While loading that album, it attempts to resolve a performer’s image URI, but the image record in the database has a null URI (likely a corrupt or missing metadata record from the migration). This throws a NullReferenceException which crashes the entire EndMutation() call, leaving those tagged items in an unresolvable/unavailable state.
When you tag a full album, Roon resolves it via LibraryAlbum directly. When you tag a single track from an album, it still has to resolve the parent album (via LibraryTagAlbumItem.Refresh), which triggers the performer/image lookup chain that crashes. The issue lies in that performer image lookup having no null guard.
Next steps to try in the meantime:
Force a full metadata re-fetch
Select all your tagged tracks (browse your Tags, select all, right-click)
Choose Edit → Re-identify to force Roon to re-pull metadata and performer images from scratch, which may overwrite the null record
2. Identify the offending performer/album. The crash is triggered by one specific corrupt image record. If you can identify which album/performer is causing it:
See if Roon Settings > Setup > Clear Image Cache helps at all
It may also be helpful to Go to Settings → Library → and review Clean Up Library
I’d also create a fresh backup just to be safe as well. We’ll be monitoring for your reply Mark, thank you!
FWIW, I think this album is part of the problem "Covered: Recorded Live at Capitol Studios". I can’t delete/remove it from my local storage. It came from Qobuz and there is another version of the album, but the “Versions” link doesn’t show up. When I try to ‘Remove from Library’ it says “No items selected”.
