We began the meeting with a quick summary of the changes Adrian has made since our last meeting:<\/p>\n\n\n\n
pointing<\/code> now has an auto<\/code> value;<\/li>\n\n\n\n- accents no longer have
pointing<\/code>;<\/li>\n\n\n\n- fermatas now have
pointing<\/code>;<\/li>\n\n\n\nevent.markings<\/code> now all have an orient<\/code> attribute that specifies whether they are above or below the staff;<\/li>\n\n\n\n- we now have a
bow-direction<\/a><\/code> marking;<\/li>\n\n\n\n- arpeggios<\/a> (and non-arpeggios<\/a>) are now implemented.<\/li>\n<\/ul>\n\n\n\n
Adrian has also updated MNX in notationref<\/a> to account for these changes.<\/p>\n\n\n\nWe spent the majority of the time resuming our discussion about the representation of dynamics, with a particular focus on how gradual dynamics (hairpins, cresc.<\/em>, dim.<\/em>, etc.) should be encoded. After some lively discussion, we arrived at consensus on an approach that Adrian will write up for community discussion in the coming days.<\/p>\n\n\n\nNext meeting<\/h2>\n\n\n\n
The next MNX specification working group meeting is scheduled for Tuesday 26 May 2026<\/strong>.<\/p>\n","protected":false},"excerpt":{"rendered":"MNX We began the meeting with a quick summary of the changes Adrian has made since our last meeting: Adrian has also updated MNX in notationref to account for these changes. We spent the majority of the time resuming our … Continue reading