Composer set for album will not show up in library/composer until being set for each track

I have manually set the composer for an (unidentified) album. Looking it now up under library/composer the album will not show up. I have to go to each single track and set the composer for to show up.

Is there a better way achieving what I want?

How have you set composer for an album? I didn’t know you could do that. The composer is an attribute of a composition, not an album. You need to set composer for a composition. In many genres that will indeed mean setting the composer for each track.

External taggers make the bulk setting of attributes like composer for all tracks easy. I don’t know if you can bulk set attributes for all tracks of an album within roon. I try to edit within roon as little as possible as I use several other players and prefer to edit the album files directly.

Album editor - edit credits.

I am asking on behalf of a customer who paid USD 699,- to get rid of working with computers and nerdy tools :wink:

We will BTW also look why the ripping process did not yield all the metadata correctly.

Just to confirm that doesn’t work for me either. The composer needs to be set at the composition, i.e. track level, which you have done. Good luck editing the missing meta-data within roon without some nerdy tools.

So at least now I can be sure that I tried it the correct way.

But Tony, one question: Are you really buying more into the Roon logic of a composer can only connect to a track rather than the Roon promise of offering the easiest way to handle Metadata?

It’s not really a question of buying in or not buying in. It’s just the way roon works. There are many, many threads going back years on this forum where each generation of new roon user is surprised that legacy functionality and organizing principles they took for granted with their old players are simply not supported by roon. Depending on genre, you will find that roon makes quite a break with the past in many areas and often makes no attempt to be backward compatible.

Depending on the genres of your clients library there will be more/less customization of legacy meta-data required to get the most out of roon. With the genres I am interested in I have actually found the meta-data editing requirements much higher with roon than the previous players I used to use. Roon has some internal editing capabilities but in general the meta-data customization needed with some genres are a lot easier with an external 3rd party tagger. This is particularly the case at the beginning of the migration process where you might want to do a lot of bulk editing across the entire library. I don’t know if this is relevant to your clients case but, for example, with a predominantly Classical library you may need to get the composer names out of the artist tag and into the composer tag across the entire library. It was common in the past to put the composer name in the artist tag but if your clients library is organised that way roon essentially will not work, or will work in a very sub-par fashion. Making these sorts of bulk edits and many others you may want to make are a lot easier with 3rd party tools. This may, or may not be important to your client. It seems to be very genre specific. Some roon users have clearly had a very painless migration experience. Others, notably Classical and EDM and some other genres still find the migration process worthwhile but there is no getting a way from it requiring a sometimes considerable investment of effort.