"La Mer, L.106" (Tracks 5-7 Disc 3) is being incorrectly identified by Roon as “L’isle joyeuse, for piano L. 109” on the subject album featuring Martha Argerich. I have done the following:
WORK and PART tabs are correctly entered; user edits reverted; album un- and re-identified; prefer file multi-part; rescanned, etc. etc. Allmusic has the work correctly entered.
Question: how do I disavow Roon of this mis-labelling? Thx. [Documenting screens follow.]
I just “un-identify” the album in these sorts of cases. But manually editing the album to identify as much as possible afterwards can then be a lot of work with a multi-CD recital like yours. It would be better if there was a way of “partially” un-identifying the disc as the rest of the disc may be absolutely fine. I’d be interested in a better way of handling these cases as well.
Yeah, did that, stripped out Roon edits, and deleted musicbrainz stuff. Basically, started with file names and titles. No joy yet.
I observe that Roon often ignores file tag edits. I have asked under what circumstances does Roon not reflect tag changes; I got no response.
At another time, I was told it was “Roon’s intent” to honor file tag edits. Oh well. Perhaps one day all will be revealed, OR, all will work.
Oh my yes, how right you are. UnIDing a 50-disc album can be a really stupid move to fix one or two compositions. I know from experience. 
@John_V FYI, Roon’s metadata for this album is complete and, I believe, correct - for all three discs.
I note that you have work and part tags for these three problematic tracks. It appears that your tags are being used, because the part names do not match the lengthier part names from the Roon metadata.
I’m not sure what edits you have done, but perhaps you should remove this album entirely, perform a Clean Up Library in Settings / Library / Library Maintenance, and re-import.
Final question, are you Preferring File tags for Composition/Part Grouping in your Import Settings, or do you manage this on a per album basis?
If what I have suggested does not work, then perhaps we can take a look at your media as is (i.e. no further tag tweaks from a reproducible bad state).
Hi John. Roon identifies from whole sets. Please would you upload the other two discs?
Joel, you were right about the WORK name. The Allmusic track list says, “La Mer” but I failed to see that it was a link to the full WORK title, “La Mer, symphonic sketches (3) for orchestra, L. 111 (109)” Once I changed to that exact wording, the ID changed.
So thanks for pointing me in the right direction.
So what had you done wrong? I can’t quite see it.
Where did Isle Joyeuse come from? Did you confuse 106 and 109 (as in the first sentence of your original post 
).
This was a case where I had “just” ripped the CDs, went through dbPowerAmp’s automatic IDing process, then dumped it into Roon. I did a cursory look-see to spot any obvious shortcomings, then moved on.
It was only when I played the disc that I discovered the error. Sigh. I don’t THINK I would have purposefully changed that work to a completely different name, but hey! I never say never to user error. 
But for future rips, should I bypass the auto-ID process? Or limit it to a particular DB? (I think choices are PerfectData, Discogs, GD3, MusicBrainz, and FreeDB.)
Hi @joel, I have a followup question related to this. With identically formatted track title names I find the following:
So for example with the following Mozart work, I couldn’t get an ID with 1) but it was enough to do 2) to get an ID.
Horn Quintet in E flat, K.407 - 1. Allegro
Horn Quintet in E flat, K.407 - 2. Andante
Horn Quintet in E flat, K.407 - 3. Allegro
That is, I copied “Horn Quintet in E flat, K.407” into WORK. I did not have to copy the canonical name “Quintet for horn, violin, 2 violas & cello in E flat major, K. 407 (K.386c)”.
John’s example is different. He did have to copy in the canonical name. That is, he had to do 3). I cannot imagine anyone has been using canonical names systematically so my question is, why does an ID with 1) work at all? And when it fails, why is 2) sometimes sufficient and 3) necessary in other cases.
Good point, Tony. Another curious facet (to me) is that my change of the WORK tags to “La Mer, L.111” did not cause the composition name to change at all; it stayed “L’isle joyeous” throughout. Only when I entered the canonical name did anything change. If Roon honored tag edits, it would have changed the screen to read “La Mer, L.111” if that’s what I put in the WORK tags. Granted, I might not get a successful ID then but at least it was honoring my edit.
Whenever something works counterintuitively or illogically, users will think the software is buggy regardless if it performs as designed.
Software should be either thoroughly magical or thoroughly logical.
Ona positive note, Danny posted an excellent presentation of the workflow Roon is designing for the artwork cropping and presentation, using similar logic an SLR camera uses when framing a picture. His explanation alone will buy a lot of goodwill and forbearance while Roon gets the bugs out. The same type of explanation should be offered for Roon’s metadata process.
when it comes to any classical when ripping using dbPA, I always check/tweak the metadata. The metadata comparison screen is very handy as it allows you to mix and match the metadata from different sources.
Closed due to inactivity. If you are still seeing this issue, please open a new support thread.
