As these discs are first imported Roon scratches its head and takes awhile to display them but then presents it as one album with duplicated track numbers.
In itself this is a puzzle as CD2 has the first track nominated as no 18, next 19 etc but Roon ignores that and renumbers them 1, 2, … etc
So, with editing the tracks are re-numbered correctly and identification done. Yes Roon finds the work and agrees the tracks are now correct but upon “Save” hashes them all up again and pronounces it as “unidentified”.
So, as it stands now, no extra data can be associated with this release if the tracks are to be retained in their correct order with it as one album, not two .
John, no sensible tagging mechanism has CDs which do not start at track number = 1. If this is how your tracks are tagged, I am not surprised that Roon is struggling. We are certainly not going to change anything to accommodate such tagging.
The Roon metadata for this album are good - very good in fact. Please ensure that:
All tracks on CD 1 have a disc number tag = 1.
Tracks on CD 1 have track numbers 1 through 17.
All tracks on CD 2 have a disc number tag = 2.
Tracks on CD 2 have track numbers 1 through 21.
I’m talking about FLAC tags not filenames.
IN ADDITION, the directory structure must be something akin to the following in order for Roon to group all of the tracks correctly into a single album:
But what John has done is simply ignore the CDs within the release and number the tracks from 1 - N. The logic behind this (especially for Classical music) it that CDs can create artificial boundaries (80 minutes) that have nothing to do with the intent of the composition. Its clearly incorrect for track 1 of CD2 to be set to 18 rather than 1, but I do think there is a case for storing the contiguous trackno as if the release consists of a single disc, (that is why SongKong writes such a field called SINGLE_DISC_TRACK_NO (Flac) to releases).
The other issue is that rippers that lookup cds from Gracenote/Amg (such as Naim UnitiServe) do this on a disc basis and therefore organize multi-album releases as a series of single disc albums rather than a single album comprising multiple discs, so for some users a disc is analagous to an album.
I think there is an argument for getting ROON to understand when a user has done as John has done as it is quite common, especially since many users are aware of the TrackNo but not the DiscNo field
I do not really agree. Roon’s job is to identify a release as it was released, (i.e CD 1, CD 2, etc.). There are too many personal methodologies to account for them all. However, once identified, Roon should and does provide the flexibility to organized as you wish, turn multi-disks into 1 Disk, or turn 1 Disk into a muli-disk.
let Roon Identify the album in question as Disk 1 and Disk 2. When that is all squared,
edit the album and choose Fix Track Grouping,
On the left hand side where the disks are listed, edit Disk 2 to 1. It will give a warning about track numbers, choose Re-Number Tracks ( it will renumber them as displayed on screen), Choose Yes.
Then on the bottom right hand side, Choose Create Album. Done, identified album with all the tracks number 1…N in one disk.
Which is why Roon has a composition View. In this view, if I play a Mozart Symphony that just happens to fall at the end of Disk 1 and continues on Disk 2, it will play the piece as a whole ignoring the physical divisions of the original CDs.
Can’t remember if metadata settings are remembered on a per-profile basis. Certainly on PC (where I did the vast majority of my ripping) I didn’t write a disc number tag for single discs. For multi-discs, I certainly did.
The key thing with dbPoweramp is always to review the metadata before ripping - make sure that the disc and total disc numbers are correct. I’ve often found 1/1 on one disc and 2/2 on another, or 1/2, 2/2, and 1/1 on the third disc…