Not sure if Iâm barking up the correct tree here, but I thought this way Iâd at least reach the right audience!
Iâve got a pressing matter thatâs been gnawing at my nerves for quite a while now and itâs this:
Roon often has two instances of a song in its composition database:
- An individual song that is part of a collection or cycle that carries both an opus number as well as an order number
- The collection of songs or the cycle, carrying only an opus number
Hereâs an example of the first case, the Brahms song Wiegenlied:
And hereâs the complete Opus 49:
Now Iâd like to make an informed choice when I adapt my own file tags. Up until now, Iâve always tagged songs such as Wiegenlied when itâs recorded on a cd without its brethren from the same main composition, in this case opus 49:
Title-tag: Op.49: 4 Wiegenlied âGuten Abend, gutâ Nachtâ (1ste strofe: Aus: âDes Knaben Wunderhornâ / 2de strofe: Georg Scherer)
Album-tag: Brahms - FĂŒnf Lieder, Op.49 (sel) (RenĂ©e Fleming, Hartmut Höll 24-48 2017)
Composition-tag: FĂŒnf Lieder, Op.49 (sel)
Movement-tag: 4 Wiegenlied âGuten Abend, gutâ Nachtâ (1ste strofe: Aus: âDes Knaben Wunderhornâ / 2de strofe: Georg Scherer)
Composer-tag: Johannes Brahms
Note: The Composition and Movement tags actually are the Custom1 and Custom2 tags that MediaMonkey does support where it fails to support the WORK or PART/MOVEMENT tags that Roon reads and uses. But thatâs beside the point for the moment. I have found a way to make MediaMonkey write WORK/MOVEMENT tags programmatically using a script. And Iâm very slowly working my way through my collection exchanging my previous Dutch language compositions for the canonical, English ones that Roon uses, simply because I want my library to be consistent within itself AND congruent with Roon.
By the way: the rather awkward way in which I filled Album tags was my original way to have the composition written out in full in the Album title while the movement could het its due within the Title tag. These two unfortunately are the only tags that Sonos showed (besides the Artist tag that Roon has now made entirely unusable for me) giving me composition-related information and I wanted to be able to use Sonos next to my Linn, for which I could use BubbleDS in conjunction with MinimServer. For those in the know this might begin to explain why I used to tag my files in such a strange wayâŠ
I am almost totally âconvertedâ to the Roon way of doing things which means, among many other things, that Iâm now slowly replacing the many Album titles I used for one album, with just the one Album title which is the one on the cd cover. This helps having Roon recognize and identify more of my albums.
I still use my three Sonoses (in the bedroom, bathroom and kitchen) a lot but I really dislike its controller app. So in the end I will just use Roon to stream music from my library to the Sonos endpoints.
There are many many things wrong about Sonosâs software! To name just two more: thereâs a limit to the number of tracks that it can hold in its database (ca. 64,000 but in practice much less when the tag values contain a lot of characters) and it doesnât know about Composers, except when in search mode. And search mode only works when you keep your library under the 64k limit which I crossed quite early on forcing me to trick Sonos with the aid of .m3u playlists, one for every classical album (actual issues, not the type of album that only holds one compositionâŠ), so I could make Sonos count only these playlist files and not the actual number of tracks. A complex and difficult story that I wonât bore you with any furtherâŠ
Right now Iâm completely at a loss as to which composition I should use for a seperate song such as Wiegenlied.
The description of the complete Opus 49 Roon gives is:
while the description of the individual Wiegenlied look like this:
As one can see, the descriptions are quite different and sort of complement each other.
I think that I would prefer if Roon found a way to merge these two sources of information into one. But thatâs probably not going to happen anytime soonâŠ
Whatâs your perspective on this matter, @bbrip, @Tony_Casey, @Martin_F, @dylan and others?