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, @MalcolmP17, 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