

One argument might be that artists are well supported in players and music can be easily sorted by artist, and since users want to listen to music of specific composers that makes it convenient for them. I’m personally not sure and never fully understood it. All the release information is incomplete without the composer, and the composer usually appears quite prominently on the cover.įor 2. What are the advantages of putting the composer into the title? What are the downsides?.What are the advantages of crediting the composer as an album artist? What are the downsides?.So for me the following questions would need to be answered: If that’s true, we can let the “only use the dedicated composer field” go down the river. There seems to be some general agreement here that the composer of a work for classical is so important that it deserves some special handling. Hence I propose the rule to put the composer at the start of the album title, followed by a colon.” has some flaws When I started to read your comment I was originally assuming you were arguing against the composer in title. Putting several data into one field is the biggest mistake. Just wanted to point out that an argument chain like “There is already a special field for composer. Again: all the other artists besides the ONE album artist should be mentioned on the track level, not the album level. THAT is inconsequent, isn’t it? My argument is to do it the same way as well with only one one composer AND to use the composer tag as intended (on the track level) AND to not cramp the composer into the album artist field AND to restrict the album artist field to just one name for structural reasons regarding the folder structure that music softwares generate. IF several composers are mentioned on the cover, THEN MusicBrainz already advises us to suddenly put them into the album title nevertheless: “Beethoven: Symphony No. They can easily mentioned at the track level for each track, but don’t appear in the album title if not mentioned on the cover. To make it even clearer: Sometimes you have additional composers on an album, who aren’t mentioned on the cover. That’s the same as printing Dollar bills without mentioning “Dollars” only saying “100” – 100 what? There are dozens of ninth symphonies from dozens of composers. Now you can say: “See, the composer AND the album title!”, but I say the composer IS part of the album title, because you don’t even have an album title when it only says “Symphony No. Look at any classical album you want: There is always the composer mentioned with the work(s). MusicBrainz tries to re-invent the wheel here instead of just complying with best practices … Oh, and dare you to call MusicBrainz an “Encyclopedia of recorded music”? “Mess of recorded music” would be a better fit …Įdit: And I’m in tune with Apple Music and the rest of the classical music industry, exhibit 1 is the aforementioned document (look who has co-authored it!). And voilà: automagically audio players will handle classical music like it is meant to be presented, just like Apple Music does, but most others I’m aware of, too.


That is what I propose: to give everyone their own field in the database, as there are equivalent tags for them as well. Same with say a violin concerto: here the soloist takes the main attention, the conductor and the orchestra fade into the background (=artist field). Because which orchestra he conducted in this particular release isn’t as important as the fact that HE conducted. The second bit is of course “Karajan” as THE one and only Album Artist. Two because there cannot be an album tag with just 9th Symphony – from whom? It must be “Beethoven: Symphony No. Of course you could ask further to gather more information, but these TWO, not three bits of information are essential. You ask: “What’s that?” The answer will most certainly be like: “Beethoven’s 9th Symphony with Karajan.” – And you have all you need in a short sentence. Imagine you enter a friend’s room and classical music is playing. The composer has his own tag, so why cramp him into the album artist field? “Oh, but you can write a script to pull it apart again as it is supposed(!!!) to be separated by a semicolon from the other album artists, which are divided between themselves by commas!” … except when they aren’t, like in the sort album artist field. It becomes inconsistent and you have to force your contributors to obtain certain rules of filling in fields. The biggest sin one can make with databases is to put several different things into one field.
