Roon guide lines are good but experience is better, seeing how a specific album reacts. This however is only useful if the Box is a collection of individual releases otherwise it creates a Tag with ONE entry The ROONALBUMTAG is very useful when importing Box Sets as Roon will create a Roon Tag for the Box. This is deserving of a thesis in its own right !! If not split then make the Album tag the Box Set name and Roon should ID it. Often CD’s (previous vinyl releases for example) are padded with extra tracks that prevent them from being ID’ed. The second tip is to avoid “splitting” box sets into individual albums unless you can be sure that those albums were actual releases. This is historical as I had started the LONG process of adding Composition and Movement to my classical library before starting with Roon almost 5 years ago.įortunately Roon recognizes both Work and Part and Composition and Movement so it imports fine I use and have used a different structure of Composition (Work) that Roon finds from AllMusic/MusicBrainz eg Sonata for Cello and Piano in Roon, I use Cello Sonata. Otherwise Roon will churn away at every typed change, literally. I find the secret is to work on Tags in a “working folder” before dropping an album into the main (watched) library. That said I have laboured long and hard to add Composition/Movement to my library in a Roon friendly manner. Unfortunately Yate is Mac only, I use a mix of JRiver, MusiCHI Tagger and SongKong on Windows 10. I should say that the manual set of tags in my existing Yate setup does not seem to have caused any problems with Roon so far… the tagging which Roon achieves seems near perfect. Or is it likely that - despite what the label published as metadata with the music -Yate* will somehow have (pre-) populated the requisite tags/fields as a result of my having chosen the right Preset (1,2,3 above)? and/or downloading one (both?) of those Presets, importing them, and then also trying to add/amend what I have been putting in #1, my own fields/tags so far manually.Īfter I’ve done the right thing there ( ) - thanks to your guidance - I am not sure ( how) or whether to manually edit any of the resulting fields in my (new) Roon Preset for any given FLAC file… does Yate effectively do the work of duplicating Title into Work (?) etc?.downloading and importing (one of? Which: ‘Roon Mappings’ and/or ‘Synthesize Work and Part’) the Roon resources here, on the one hand.building a Roon preset of my own - almost from scratch and what I have learn from Barry.I am torn between what look like three courses of action: For which (needless to say) Barry is being extremely helpful… as always. Īnyone know and can spare five minutes to guide me, - thanks so much for jumping in! This one suggests that all I have to do is follow the ALLMusic conventions for Work and Part and Roon will… ‘obey’. If I’m understanding that properly, does also populating ( Yate’s) ‘Work’ and ‘Part’ achieve anything (extra)? This post, for instance, suggests that other fields in Yate will (allow Roon to?) map Yate’s ‘Work name’ and ‘Movement name’ onto the fields which Roon recognizes best. I’ve searched the online help and this forum but am still confused. He tells me that Roon has specific requirements for the following four tags/fields:īut I’m not sure what I should put in those fields in Yate. In the six months that I’ve been using Roon I’ve been very impressed with the way it ‘finds’ and tags the 99% Classical (95% FLAC) files which I import into Roon - exactly as members of this forum told me I would!īeing a bit of a perfectionist, I’ve been corresponding with the extremely helpful and responsive developer of Yate in order to pre-tag as many of the fields in my downloads which are either missing and/or need editing.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |