Fermatas (issue #106<\/a>) are now complete, and can be found in the specification here<\/a>.<\/p>\n\n\n\n One missing detail is that we do not currently encode both the orientation of the fermata relative to the staff as well as the direction in which the fermata symbol itself is pointing. Adrian proposes that we encode this using Adrian proposes that we add up bow and down bow to We discussed how arpeggios could be encoded. After some back and forth, we propose that a list of arpeggios should be found in the part We also propose a similar object for chords that definitely should not be arpeggiated, which is typically drawn as a square bracket to the left of the chord, the equivalent of MusicXML’s Towards the end of the meeting we began a brief discussion about hairpins (continuous gradual dynamics). There is much more to discuss, but as a starting point, we plan to extend the existing Our next meeting is scheduled for Tuesday 12 May 2026<\/strong>.<\/p>\n","protected":false},"excerpt":{"rendered":" Fermatas Fermatas (issue #106) are now complete, and can be found in the specification here. One missing detail is that we do not currently encode both the orientation of the fermata relative to the staff as well as the direction … Continue reading orient<\/code> for placement and pointing<\/code> for the direction of the symbol. We will also add this to the other event.markings<\/code> items for which it makes sense (for example, pointing<\/code> makes sense for strong accents\/marcatos, but not for regular accents).<\/p>\n\n\n\nBowing marks<\/h2>\n\n\n\n
event.markings<\/code>. We propose adding a bowDirection<\/code> entry with an enumeration with values representing up bow, down bow, and bowing freely (which is sometimes depicted as showing both up bow and down bow symbols next to each other).<\/p>\n\n\n\nArpeggios<\/h2>\n\n\n\n
measure<\/code>, at specific rhythmic positions (in the same way that clef changes are encoded). We propose a direction<\/code> enumeration with auto<\/code> (implying up), up<\/code>, and down<\/code>, and a boolean arrow<\/code>, false by default, that specifies whether an arrow should appear. We also propose an object to encode the starting and ending notes by ID, which if used must specify both. (This may prove useful for other similar notations with specific starting and ending points in future.)<\/p>\n\n\n\nnon-arpeggiated<\/code> element.<\/p>\n\n\n\nHairpins<\/h2>\n\n\n\n
dynamic<\/code> object to have an optional end position (or ID for an event) so that it can describe a range, and then consider how to specify the value<\/code> (dynamic type) in order to denote that it represents a gradual vs. immediate change. Adrian will make a proposal for community discussion.<\/p>\n\n\n\nNext meeting<\/h2>\n\n\n\n