Merging didn’t meet my expectations so I have abandoned it. It turns out I probably have a feature request for configurable equivalents instead. Maybe roon can comment. Does merging when you really want to manually add an equivalent have unintended consequences? The thing that worries me all the time with roon is have I inadvertently hidden a bunch of albums because I didn’t understand the consequences?
and… what also puzzles me is… the day an artist/composer Roon doesn’t, at the moment, know a thing about will be in the global database… what happens if I have already merged two instances and picked as main the one Roon will still not recognize?
(eg: at the moment Vienna Philharmonic has pictures and text whilst Wiener does not. Same goes for Alfonso X vs Alphonse etc so these were “easy”. what about two still “unknown” instances of the same artist?)
Thanks for taking a look. Can I ask you how roon decides on the ‘master’ equivalent? The reason is, I decided to go back to the drawing board and start at A->Z in my library and there was immediately an issue with Kelevi Aho and the Leipzig Radio Symphony Orchestra.
If I understand correctly roon maintains “MDR Leipzig Radio Symphony Orchestra” as the master and maps one or more equivalents to it. Unfortunately my choice of “Leipzig Radio Symphony Orchestra” has not been mapped and that is why when I tell roon to use my album artist tags it cannot make a link. But how exactly is roon making its choice of master equivalent? These are the equivalents allmusic knows about:
MDR Leipzig Radio Symphony Orchestra
Das Rundfunk-Sinfonieorchester Leipzig
Großes Rundfunk-Sinfonieorchester Leipzig
Leipzig Radio Symphony Orchestra
Leipziger Rundfunk Sinfonieorchester
MDR Symphony Orchestra
Middle German Radio Orchestra
Orchester des Mitteldeutschen Rundfunks
Rundfunk Sinfonieorchester Leipzig
I had no idea there were so many equivalents and that the choices you make have such wide ranging impacts on your roon experience. But I am very surprised I seem to have so consistently made different choices to roon. I thought I was doing much the same as everyone else as I just picked up “best practice” from the blogs. Mostly I just used databases like freedb, GDI, discogs, musicbrainz when I could and cut and paste from amazon or the record labels when I couldn’t. As a last resort I just copied the backs of album and CD covers. That’s what I remember doing in this particular case because there were only a few tracks and it was quicker:
It is just an observation but I think a lot of the reason why there are such wide discrepancies with the equivalents is historical. This album for example is already 25 years old and I guess the most famous ensembles are almost constantly evolving new names. But I digress. How exactly does roon settle on an ‘equivalence’ master and how can we improve the chances that we have picked equivalents roon knows about?
It’s not really practical for me without a batch script but I thought I would try aligning my tags with roon in a few cases so I understood what was going on. But I got a totally unexpected result when I re-tagged my “Leipzig Radio Symphony Orchestra” references (in artist and album artist fields) to “MDR Leipzig Radio Symphony Orchestra”.
This thread started out because I mistakenly thought I could use “artist merge” to solve the effects of “artist equivalence” I was experiencing. We have established that is not really possible although some can live with the side effects. But what is causing this result? I am just trying to align my metatdata with roon’s but that doesn’t seem to work either. Is this just not possible? Is there some other procedure I should have followed?.
I take your point that roon will never never display duplicate equivalents. But in this case all links point to a BBC Symphony Orchestra page that looks identical to me. It may be the case that they are not equivalents. I don’t know. But from a user perspective they look like equivalents, walk like equivalents and talk like equivalents
This is a case where the implementation of the rule that equivalents will never be displayed on the same page results in a very disorienting user experience. These are a series of piano duets by Kevin Sargent and Phillip Dyson. I would expect the two pianists to be paired together on the various parts of the screen but that is not what happens. Philip Dyson appears as aan album artist and Kevin Sargent appears as a composition artist.
This is of course an extreme example where the splitting of the artists like this is very noticeable. But I come across this all the time with my library where it is often unpredictable whether an artist appears as an album artist or a composition artist. In most cases I would expect both.
It turns out that most of the effects I am seeing like duplicates, missing links and odd groupings are caused by the interactions of equivalents and credits with my library tags. I can see that it is often possible to achieve a cleaner result by editing combinations of primary artists / album artists and credits. “Merging artists” is probably not the way to go. But there are a lot of limitations to this solution approach. The scale of the mismatches makes it impractical and in any case there is not a lot of point in me perpetuating what I consider bad metadata by aligning my tags with roon in every case.
Going forward it will be better if I post my equivalence mismatches here as there appears to be a procedure for contacting the metadata suppliers.:
But there is still a case for a more free-form “classical library issues” thread to collect together topics that are currently scattered around the KB. Is that possible? my list of topics would include:
Tagging best practice
There are no standards out there but iTunes guidelines to its suppliers is the closest to one that has emerged. roon seems to roughly adhere to it. Probably many of us unconsciously already do as well. But there are misunderstandings and inconsistencies of approach and it would be nice to have somewhere to more systematically treat this topic, especially as it impacts classical libraries. For example I would like to find ways of improving the grouping of classical compositions in my library. I don’t see this discussed but I rather suspect that incompatable choices of “delimiters” in track titles effects the consistency with which classical compositions are parsed and grouped
The parsing of “comma” delimiters in artist lists causes a different kind of havoc but at the end of the day they are widespread in public databases and legacy local libraries particularly where artist lists are very long in choral and operatic works. What to do? How to batch groom to overcome “lastname, firstname” cases, for example?
This is going to be an uphill struggle with the metatdata suppliers that may never have a totally satisfactory resolution. It has very widespread impacts on search, grouping, links, reachability. I think it is time to consider the provision of manually configurable equivalence matching and I can raise a feature request but I do not know how realistic this is in the short term. Are there are other workarounds that can be used to improve the roon classical music experience in the meantime?
In several of the most important parts of the roon GUI, search is still prioritisng the “performance” or “production” contribution of composers rather than “compositions”. This leads to very bizare, confsing results with even the simplest searches. Long term, this sort of interface handling for classical music needs a re-think. But as a quick fix it would be nice simply to have the option of switching off performance/production screens for classical or at least ensuring that the default is that composition screens always come up first. Also, a simple list of albums where the composers main contribution is composition should be much easier to find as for many of us this would be a starting point on a search. Again I can raise a feature request(s) but I do not know how realistic that is and I would like to have somewhere to systematically explore the work-arounds particularly as they effect local classical libraries.
Very large numbers of missing classical album reviews. Why is that?
Local metadata control
This is obviously the elephant in the room. There appear to have been great strides in 1.3 but many are still experiencing recurring interaction effects between local library tags and roon metadata. It would be nice to have somewhere to more systematically explore these effects on local classical libraries and have a way of influencing their resolution on the roon roadmap…
For a long time, I used Media Monkey as my metadata editor. This made batch grooming an absolute breeze. Since getting my metadata under control, I very rarely fire it up, and just use dbPoweramp for ripping new CDs and minor tweaks to the metadata.
Yes. I found it. I cannot remember switching crossfade on, maybe another family member, but the effect with HQPlayer is to make most styles of music unlistenable. Maybe there is some other setting because It doesn’t really fade. It is just a very hard cross between tracks:
So I tried it with pop music where I can imagine having a use for it but it’s the same. With HQPlayer there is no real fading. It is just a hard cross. Has this come up elsewhere except in the post I found?
From a classical perspective the issue is more one of adding some intelligence to cross fade so that it knows with classical music different behavior is expected. I have just found out for example that with roon you can expect to have to re-baseline “zone settings” eveytime you, or a family member, switches between genres.
so did I and I already changed artists/composers separator from " - " to "; " (which produced amazing results in Roon’s Artist list )
maybe I’ll also empty the “Artist” tag, in all my classical files, even though I already fixed the “Performed by Johann Sebastian Bach” issue by editing Roon credits
waiting now for an official “wth Roon exactly does with user’s tags” guide before editing more
I often do a search and a replace with mp3tag for this kind of thing but it would normally be for an album, maybe a box set or one of my composer directories. It has been a long time since I would have done this on my entire “classical” directory, and that would have been at a time when it was much smaller.
What happened is that mp3tag failed with a catastrophic “unexpected” memory error. Do not try this at home! The effect is that all my classical artist tags have been blanked and most of my album artist one as well. So inadvertently I have become a test case for the blank canvas approach that roon defacto seem to assume. I keep on seeing that the best thing to do is to blank your artist tags. Well, for better or worse I have actually done that.
The results are not encouraging. I am seeing all sorts of strange effects I cannot make head nor tail of. Even when roon is dealing with a blank canvas of user generated tags it is still populating “primary artist”, “album artist” and what looks like two sets of credits at album level and track level and these are more than enough tags to interfere with each other. So clearly these metadata interference issues are there regardless if users also have substantial self-tagged local libraries or not.
There are a lot of interaction effects. Duplicates, missing links, I even get things like Berlin Philharmonic Orchestra featuring Berlin Philharmonic Orchestra! Generally, the meta data quality is much poorer than I imagined even with very famous names. I get both “Herbert Karajan” and “Herbert von Karajan” for example in his famous 1963 Beethoven Symphony cycle. In general, it is true that I seem to be able to tidy things up by switching on/off the right combination of primary artist / credits and album artists but it is never obvious and it is also very much trial and error. It is also quite hopeless as there is just too much of it
On a couple of albums I have re-tagged the artists just to see the effect but I am at a loss. Without the artists tagged at a track level there is almost no additional information displayed. But the minute I tag artists at a track level then roon finds all sorts of very specific information about recording dates, venues etc. What I don’t understand is, if roon has this track level detail, why does it not display it by default? Why does roon wait until the user inputs the track level artist details? Looks like that would go a very long way to getting me off the hook Personally, if that worked reasonably well I would much rather hand over the tagging heavy lifting to roon / Tidal etc and only jump in with the odd specialist album or vinyl rip.
As you can see these are concertos. So what I am really interested in are the soloists, none of which appear except in the review text. Probably because it is part of a large box set, roon in fact makes no attempt and the primary artist has been set to “Various Artists”. Not much use.
So what I did next (all in my own files not roon) was to go to the Deutsche Grammophon web site and cut and paste the artists at track level. I also cut and paste four soloists into the album artist field because I have discovered that 5 seems to also trigger roon to display “Various Artists” instead. All delimiters were set to “;”.
As you can see, now all the orchestras have duplicates. In order to fix this I have to go to the credits screen at a track level. There I will see that the orchestras involved have been listed as both orchestras and primary artists. What to do? By trial and error I work out that I must remove the primary artist instance which in the case of Vienna Philharmonic Orchestra is also an equivalent called Vienna Philharmoniker Orchestra.
Finally, I loose the will to live and accept I have almost get what I was looking for except:
a) I have to make the compromise of no links in the primary artist section at the top of the screen. roon seems to have an either/or logic here. You can have links at the “work” level or the “disk” level but not both (which would be my preference).
b) Apparently Weiner Philharmoniker features Weiner Philharmoniker . This is not an isolated example. I see this “recursive” artist self referencing a lot.
This is clearly an awful lot of work and it is still wriong, so I simply will never do this in any systematic way across my entire library. What surprises me is this is a “core” album of core artists and repertory which I would have thought would have been much more subject to metadata QA than more specialist titles. I have seen several comments that blanking your artist tags is the way to go. I think the consequences of that strategy needs a lot more investigation.
Got confused. I can see I actually fixed Weiner Symphoniker featuring Weiner Symphoniker by removing the primary artist instance in credits. But I still have absolutely no idea why that works or even if it does work without having a knock on effect elsewhere.
I can see now that there is a general misunderstanding that you can blank your artist/album artist tags and roon will somehow work better. It is not really like that. What roon is really saying is that they will interact with your library much better if you use ENSEMBLE, SOLOIST & PERSONNEL instead of ARTIST/ALBUM ARTIST.
So what they would prefer you to do is re-tag in that way and not just blank your legacy tags like I have inadvertantly done. I have nothing to loose so I have customised mp3tag to write these new tags. The trick is to map 1.3 tags to unused mp3tags. With some of them the choice is easy, but with others it is not and it all smacks of the old days when everyone put the composer in the artist field which is what created most of the mess we have today. The other thing is that depending what you are doing in mp3tag you have to remember the name of the original mp3tag tag rather than the name of the 1.3 tag you have mapped it to. Other than that it seems to work. I mapped this way:
WORK -> WORK
MOVEMENT -> PART
INVOLVEDPEOPLE -> PERSONNEL
GROUPING -> ENSEMBLE
ORIGARTIST -> SOLOIST
It sort of works with flac (at the moment I have huge numbers of artwork that hasn’t loaded but that is another story). I haven’t tried other file types. But there are other problems. I don’t know how much of roon is really geared up to using these new tags. You can see in this screenshot that none of the primary artist / album artist fields at the top of the screen are being populated. Also the identification screen doesn’t work either because roon is still looking at the artist fields etc. not the 1.3 ones. I’m not sure how in practice this will all work. Are we now expected to maintain two sets of tags?
Thanks a lot @tripleCrotchet for your thorough investigation. I am totally with @Andre_Gosselin insofar as I’ve currently given up to understand. I wait for an explanation.
And I don’t have the energy to investigate myself and discuss anymore, since it is not clear to me what to discuss about. Unless there is a documentation on what Roon does with external tags and how these interact with Roons metadata it really makes no sense to discuss further. We are all speculating here and that’s not a good thing.
It is not much help I know, I’m just saying the same thing in different words, but the roon metadata model doc has a long list of metadata sources: http://kb.roonlabs.com/Metadata_Model and says:
“The “ands” and “ors” in that column are significant–they tell you whether data is being chosen from one of the sources, or blended across multiple sources. When blending happens, it is usually not a simple union–there is a merging algorithm that tries to make good choices to produce a clean result.”
Mostly the blended “ands” are the credits and of course the merging algorithms are not specified.