![]() ![]() ![]() Roon and MinimServer but these two applications have different incompatible ways of dealing with Work, most notably Opera usually consists of Works, Acts and Scenes. Of a number of works, each containing a number of movements. This prevents these fields being used when we match to a Classical album, non classical albums are unaffected.Ĭlassical albums create extra compilations for metadata tagging. We do this by adding (Track) Artist to the Never Modify or add these fields option on the Classical tab, we also add the plural and sort variants. Since this we have separate fields for conductor/performers/choirs/composers anyway it is usually better to leave the track artists blank and let roon work out the best track artist from the other fields PopRock music usually has a well defined track artist but Classical music doesn’t have an easily defined track artist, it can be defined by the conductor/performers/choirs/orchestras on the track but is difficult. So we add Performer to the Never modify or add these fields option, we also add to the new Delete all metadata from these fields option, this means that if you have some existing performer metadata it will be deleted.ĭon’t worry this performer data is also written to the InvolvedPeople field, and Roon understands this field and uses it to create the credits. However Roon uses the Performer field to identify the primary artists (without their instruments) so you really don’t want to use Performer field when writing to Roon. SongKong and many applications use the Performer field to store musicians and their instrument, including session and secondary musicians. We discuss the key settings in this post. SongKong comes with a Roon, Fix Songs profile, you usually want to use this because it sets the options for the optimum compatibility with Roon. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |