Version 2.53 affecting Tidal track tagging (ref#9KMB2N)

Support
1

I use tags to organize my library, and I use smart playlists to identify which tracks I still need to tag. The primary list I use for this purpose had about 250 tracks on it yesterday. Version 2.53 (Build 1544) installed last night, and I noticed this morning that the list had about 690 tracks on it.

I restored a backup from night before last (under the version 2.52), and before I opened this Smart Playlist, Roon indicated that it had 159 tracks. When I opened the smart playlist, it immediately showed 239 tracks, but then Roon started adding tracks to the list. I clicked the spinny thing at the top, and it shows progress indicators for “Adding music to library” and periodically for “Applying library settings.” The number of tracks on this list went up to 714 and eventually came back down to about 700. About 550 of these are from Tidal (way more than the total number of tracks that was on the list yesterday).

I took some videos that I can link, but here are the screen shots.

Initial Opening of Smart Playlist after restoring backup
Initial Opening of Smart Playlist after restoring backup1506×1342 185 KB

"Adding Music to Library" and "Applying Library Settings"
"Adding Music to Library" and "Applying Library Settings"1470×1365 163 KB

I did a bunch of work with Muse PEQ settings yesterday that I don’t want to lose, so I restored the backup from last night (after the installation of 2.53), and it went through a similar process when I opened the smart playlist: First indicating there were a 150 or so tracks, then opening to show a count of 230ish, and finally settling around 690. (I added tagged about 10 tracks yesterday, so I assume that to be the difference in the numbers between the two backups.)

This indicates that something is changing with Tidal tracks: Either Roon is wiping out the tags, or lots of Tidal tracks are being added back in to the Roon library after I removed them, or for some reason Smart Playlists are picking up a bunch of tracks it wasn’t picking up before.

The only way I know to identify the problem myself would be to install the previous version of Roon, restore a pre-2.53 backup, create and export a static playlist of untagged tracks, then compare it to the version that is created when 2.53 takes over. Is there some other action you recommend? If not, where can I download version 2.52 of Roon?

Here are the pertinent details of my Roon Configuration:

Roon Server: Windows 11 Pro 24H2 (Dell Optiplex 5090, i5-10505, 16GB RAM, Nvme drives for OS and library)

Library: 25,600 tracks, 3,200 from Tidal, others local

2

Hey @Andy_Spinks,

Thanks for writing in and sharing your report! To confirm, in the end, your playlist ends up with 690 tracks?

A bug fix we introduced in the latest update dealt with issues of missing Tidal tracks, and based on your description, it could certainly be the case that you were missing a large portion of Tidal tracks up until updating, where after applying the recent fix, now have the correct number of tracks in the playlist.

From a fresh Roon Server diagnostic report, we’re not seeing any obvious Tidal-related errors - do you think the above could be a possibility for you?

3

This is just awful. I found an installer for 2.52 and reinstalled it. Bouncing back and forth between the two versions, I was able to create a playlist of 462 Tidal tracks that I am almost certain that I tagged previously but are 1) no longer tagged in version 2.53, and 2) visible but not playable or editable in version 2.52. In addition to losing all the tags I had done on these tracks, I have no idea how many Tidal tracks I had added to static playlists that are no longer there. Also, I have about 85 Tidal favorites that are showing zero plays, so that history is gone too.

Losing tracks (and the curation I’ve put into them) is one of the major issues with streaming that I was hoping that using Roon would prevent. I even created a smart playlist that was supposed to show tracks that became unavailable, but I never saw anything come up in it. Maybe that only works for local tracks.

This just feels awful to know I lost all of that work. Do you know when the problem started occuring? Is there any previous version of Roon I could use that would let me recover the tags? Or is the problem all on Tidal’s end? Is there any way to know when Tidal is wrecking our libraries so we can take steps to save our curation work?