The “performing orchestra”, “Orchestra”, and “Primary Artist” listings are redundant. Experience tells me that Roon displays Orchestras and Conductors quite well without the Primary Artist tag added to them. I would prefer just one listing and treatment, the Orchestra one.
The ‘performing orchestra’ tag should be treated by Roon as an Orchestra tag, without duplication in the Credits list (IMO). Musicbrainz uses this tag extensively, and these are particularly troublesome to edit because they are in one or both of Musician Credits or Involved People.
Primary Artist tags for Conductor and Orchestra are redundant, IMO. They clutter without purpose. Or perhaps I don’t understand why they are present.
Great job by someone (Roon?) somewhere (on import or upon album recognition) in translating “Sinfóníuhljómsveit Íslands” into “Iceland Symphony Orchestra” (Symphony of the Ice Island?)
To summarize: 1) treat “performing orchestra” tags as “Orchestra” tags on import; and 2) do not create Primary Artist tags for either Orchestra or Conductor.
Briefly (and I don’t have the time to get into an involved discussion here):
For Roon, Primary Artists are typically the main performing artists listed on the cover of the album (the spine of the album if we had that information). This is our long held and stated opinion and is not up for negotiation. Whether or not the performer in smaller lettering is deemed an album main performer is completely subjective.
There is a case for munging Performing Orchestra into Orchestra. (Presumably Performing is needed to differentiate from a Standing Around Doing Nothing Orchestra.) I’ve made a note to consider this when we next review the set of credit roles; however, for fairly obvious reasons, local file tags are handled differently to metadata that we process in the Cloud so any changes may involve a fix in the product main.
No they’re not. As I stated in my response (1), Primary Artists are essentially the main performing artists on the cover of the album. Specific credits identify the roles of these and other artists at track and/or album levels.
Pretty sure that was us; thanks for noticing.
performing orchestra coming through from your tags verbatim in lower case seems like a bug to me.
Actually, I think it’s used at musicbrainz to distinguish between
Release relationships (orchestra only) and
Track relationships (performing orchestra)
It makes sense how it’s done at musicbrainz but Roon doesn’t make use of Release relationships (yet), I believe - at least not in a way that would or could match the musicbrainz logic. (Note: I don’t suggest to discuss it. )
From the little experience I have with adding stuff at musicbrainz it seems like there’s no need to know when entering data because musicbrainz automatically adds “performing” when an orchestra gets added as a recording relationship of a track.
By “natural name”, @Joel, I mean the Orchestras are called Orchestras in the Credits list, and Conductors are called Conductors. For those two, the additional label of Primary Artist is redundant.
One can remove a Primary Artist tag via a Roon track edit, and nothing changes except on the Credit List where the redundant label of Primary Artist is removed. The “Performed By” XYZ Orchestra and “Conducted By” lines remain as was above the tracks listing, and the second line (beneath the album title) is unchanged.
As for why “performing” is added, I have no idea. You’d have to ask MusicBrainz. But it is routinely added.
Now, I, like you, “don’t have time to get into an involved discussion here”, and “the subject is not up for negotiation.”
I’m not sure if it’s that simple. Merging Primary Artist and Conductor and/or Orchestra might be a presentational option on the credits tab, but maybe not a functional one. Admittedly I didn’t fully grasp the implications (and am not sure if I need to) but it seems like there’s more to this - even so it looks redundant in the credits tab. How can you be sure that all what comes with the (coded) privilege of being a Primary Artist will apply to Conductor and Orchestra too? Not everything might be obvious at first …
See my comment further above for my idea about it.
I have often wondered about this (I don’t know the answer either). I routinely delete primary artist tags for orchestras but not to remove the duplicates on the credits page. I do this to remove duplicates on the main album page. I get these duplicates a lot and my experience is the primary artist link is usually “dead” in the sense that either the link doesn’t work at all or it just goes to a “text string” with no bio or artist art.
You are quite right, @anon47919701, things rarely as simple as they seem particularly in RoonLand. But as @Tony_Casey added, I too have deleted these apparently dead links without obvious side effects. Too bad we have to guess about this stuff.
It gets me back to the problem of working with black boxes. Some mystery can be delightful; too much mystery is irksome.
This usually indicates that an artist from file tags couldn’t get merged automatically with the artist Roon has on records for the track. The reason: who knows … at times, Roon may still have two entries for one artist in its data set - even so I understood that recent changes at the way multiple metadata sources are merged in the cloud will clear up this; at other times there may be a data point we just don’t see which leads Roon to decide not to merge an artist. Speculation, speculation …
This is not happening to me occasionally. With orchestral music It happens 100% of the time. I have seen the occasional post concerning duplicates but I am really surprised it is not raised more often as an issue.
This is a totally random example. Nothing special about it, happens to me all the time.
Mostly I use roon. There are a couple of exceptions (artwork, composers, label, catalog and a few others).
One thing though is that with a largish library I cannot see any practical way in which I could change these settings now. If you do, then roon re-writes the entire library (not just future imports) and that has the effect of overwriting all sorts of edits I have made to make the display work with this particular combination of settings. I have tried doing that a few times but then everything is a much worse mess that would be a nightmare to re-edit so I end up reversing it. Now to all intents and purposes I seem to be stuck.
Hmm, so with “Prefer Roon” file tags are treated as additional entries for performers on track level. The to be expected behaviour, I’d say.
Since it’s kinda hard to predict what will change and what sticks when you alter an import setting I understand that you’re reluctant to try. Even so with a backup done right before the change a trial run seems possible. I’ve set “merge Roon and File” for all credits except production and seem to have less doubles.
Sorry to revive an old discussion…I know that @joel said this was working as designed, but I want to pick this apart a little bit.
All of this repetition is not adding any value, just clutter. There is really no added value to displaying someone as a primary artist in credits if they already have a conductor, composer, or ensemble role in the same list.
The question is–do we clean this up with smarter display logic, or do we clean this up with a little bit of an auto-grooming pass over the source data?
Both are feasible, but have different tradeoffs. Fixing it in the source data lets the user interface remain “dumb” with respect to this–which makes the editing model a little bit more comprehensible since there is no hidden logic between what you edit + what you see…but that also means that with edits or bad file tags, you can still get some of these obvious repetitive situations.
I think I would be comfortable with either approach. I am slightly worried about the confusion that doing it in the display layer may cause for editors/groomers. Doing it in our source data is a bit more pure to our ideals about automatic metadata improvement/identification, and I think our source data is where most of this mess is coming from.
I tend to agree. We can also do more intrusive cleanup there. I would feel weird doing a “Performing Orchestra” -> “Orchestra” rewrite on someone’s manual edit, or file tags, but not weird at all about doing that to source data.