pe-ro

@craigsapp, you're right, a `` directive requires multiple MIDI pitch bend events to render (i.e., sound) the desired effect. As you say, these don't have to be explicitly encoded --...

Adding `` should probably be split off into a separate issue.

Laurent and I had a conversation about this recently and decided that the order of values within `@artic` and `@accid` as well as the order of a note's `` and...

I think your example and explanation are on the mark. Since `@place` is missing on the 3rd `` element, the articulations given there would have to follow the renderer's own...

I just realize I contradicted myself (hey, it happens occasionally) re: the order of articulations vis-a-vis #375. Presumably, the encoding order of accidentals would be left-to-right (that is, from farthest...

Making a member of att.staffIdent -- ``` Attributes for identifying the staff associated with the current feature. Signifies the staff on which a notated event occurs or to which a...

`` already has `@startvo` and `@endvo` attributes, so I don't see how `@rotate`, `@angle`, etc. are necessary. As I imagine it, a hairpin has an imaginary line connecting its starting...

Sounds good with adequate testing, of course. 😀

Imagine a visual interface (for a hairpin, for instance) that provides 3 “handles” – one that controls the left side of the hairpin, one that controls its right side, and...

Here’s a crude illustration --  The left and right “handles” control the start and end points of the hairpin in both vertical and horizontal directions. Angled hairpins can be...