WORK and COMPOSITION tags are synonymous. Are are PART and MOVEMENT tags.
If you want to group tracks into compositions, you need WORK and PART tags.
WORK and COMPOSITION tags are synonymous. Are are PART and MOVEMENT tags.
If you want to group tracks into compositions, you need WORK and PART tags.
Mike,
Roon handles COMPOSITION and WORK tags as equivalent. Ditto for MOVEMENT and PART tags. I personnaly use COMPOSITION/MOVEMENT, as the names seem more appropriate.
@Andre_Gosselin Worked great Andre! Thanks for the tip!
andā¦ what about going the opposite way: I mean how can I break into single tracks something that Roon considers a composition?
thanks
Try assigning different composition tags to the tracks you want to stand alone (setting for ex. composition tags to the tracks title). This should work.
You should be able to use the same WORK (or COMPOSITION) tag, same PART (or MOVEMENT) tag, but different WORKID tags for each track.
hhhhmmmmmā¦ Iām using Yate (on Mac OS) as tag editor and Iām quite confused as all I see is āWork Nameā, āMovement Nameā and āMovement ā¦ of ā¦ā
tried anyway setting each trackās Work Name and Movement Name to trackās title (plus Movement 1 of 1 for each) but Roon still shows Track 1 as a composition (named after albumās title) consisting now of just track 1
better than before when all tracks were grouped as a composition butā¦ I suspect one canāt fight on his own Roviās mistakes
album, btw, is Ravi Shankar/Philip Glass āPassagesā
EDIT: ok, refreshed the view (by going to a different album then back) and all is fine now
@joel @support Have you actually sat down and edited work and part tags, track by track using something like dbpoweramp? Do you know what a royal pain in the A it is?
I just want to be able to select a bunch of tracks on an unidentified album and say āThis is a compositionā and have Roon group them. The track names already have the structure āComposer: Work; 1. Movementā - canāt you design something so Roon can read this structure from the track names?
Thanks for sharing your feedback with us, @Malcolm_Percival, and sorry for the difficulties.
Iād like to recommend adding your voice to this post in Feature Requests:
Our product team and developers keep a close eye on that category, so thatās definitely the best place to propose a change like this and get feedback from the Community.
Thanks!
Dylan