Yes, I noticed that too, and I don’t know why that is. I am sure that is somehow related to the issue, though I’m not sure how. The Metadata of the track itself are correct, the track itself is correctly labeled as Track 20 of 20 on Disc 2.
Just for reference, Roon retains database entries even after files are deleted or albums/tracks are removed from streaming services. That can lead to a new import being matched back to an existing entry. To start truly fresh, you have to use Settings > Library > Library maintenance > Clean up library.
AJ
Ok, interesting, thanks. Did that, and there seems to have been 8617 deleted files. Quite a bit, so I did that.
However, it had no bearing on the BD Christmas Jazz compilation.
My only other thought on this is that there could be multiple versions of this album — namely, a version that omits the Mahalia Jackson track, which seems to be the only overtly religious track on the album. And Roon’s own metadata could be for a version without the track.
AJ
1 Like
That’s a bit my suspicion too, though I haven’t confirmed it yet. There are some listings for this album, but I haven’t found a tracklist that differs. But indeed, ROON has identified the album… just not that one track, so that could be an explanation.
The rogue tag is probably in Tivo or MuscBrainz not necessarily in your tags
1 Like
Okay, okay, I got it! The album is now “correct”
What I did next:
This BD Jazz Christmas album is just fascinating. ROON recognizes ALL the tracks are from the same album:
Just all the tracks but one in one album, and that one track and none of the others in another album:
But even now, where all the tracks are clearly identified, and identify the same album,
I still have two albums, one with all tracks and one with just the Mahalia Jackson track.
As you can see, that one track is rogue. The albums are correctly identified, the tracks are correctly identified, they come from the same source (Qobuz), are tagged in an identical manner and are all in the same folder:
So in Roon it now looks like this:
The one difference I note is that for some reason, there is an “Explicit” sign on one album… which I find odd… these are just old jazz Christmas numbers, rather harmless music. But that’s again for another day.
So there is just something, something off. I could pretty much determine that it has nothing to do with my tags. And it has nothing to do with ROON incorrectly identifying the album.
Now what I did next: I removed the folder with the album from Roon, I deleted the album from Roon, I cleaned up the library in Roon, I double checked this album was really, really gone, then I re-inserted the folder. The exact same files. And voila,
This time everything displays correctly. So AJ’s tip with the “Library Maintenance” really helped. Maybe I did not do it thoroughly enough the first time. There must have been something very deep inside ROON that “remembered” these as two different albums, and continued to present them as such, and only after I completely removed the album and re-inserted (the exact same files), ROON re-read the album and put everything in place.
Yes, if Roon splits an album upon initial import, the split tracks are likely to remain that way, regardless of identification status or additional metadata grooming. Only a Merge albums manual edit will mesh them together.
This happens to me a fair bit with multi disc deluxe/expanded film music CDs. However, it is a minor issue of my own making. For illustration, each of the two discs of La-La Land’s “Top Gun” gets a separate folder under the Harold Faltermeyer folder. My preference is different from Roon’s recommended practice of nesting both disc folders under a single “Top Gun” folder. Thus, a few taps of manual intervention oft is necessary to link up a multi disc set.
AJ