Hi, I have a question about compositiond merging.
Very often, (expecially for standard with many performances) it happens that there are many replicas of the same composition. Here is an example in my library:
the first
most of the recordings in my library should have corresponding file tags (i’ve checked this for the first 2 entries).
I a situation like this, no matter why roon does not collect the compositions, one would merge them.
But very often, if you try to merge, it happens that onlsy some of the tracks associated to (say) the 2nd composition are actually mapped to the (say) 1st one, but some other tracks remain associated to a second composition that do not disappear whataver you do.
i wonder if this is normal, if i’m doing something wrong, or if there is a solution.
thanks
If composition-related metadata sourced by roon directly from TiVo or MusicBrainz (or provided by streaming services in case of an unidentified album) shows a slight deviation (and may it be additional arranger, order of composers in case there are several, lyricist falsely assigned as composer and alike), roon might not recognize the 2 compositions as being the same, regardless of correct and corresponding local tagging.
I assume you are not using any streaming service such as Tidal or Qobuz from which roon could source additional information on compositions? That might change roon´s handling of compositions being recognized as one and the same, and in many cases it seems to be helpful.
Do you choose the canonical composition - usually the one with composition year and additional information - as the result of merging?
Could you show an example please of such as composition resisting such a merging operation?
I have been having such cases that roon is refusing a composition merge, but it was really really rare. Seems to be a bug.
