-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Specify how to encode tied chords #60
Comments
A first editorial pass over the spec. Not many significant normative changes. - Grace notes groups were removed from the list of note features since they are a grouping mechanism and they follow their own rules - Similarly, the chord character was removed, since it functions more like a tie, and the order of ties and chords are not really established. (See #60, #2) - Specify that for neume notation, time sigs and key sigs MUST be omitted. This is following the decision to forbid durations on neumes, and the general direction of removing unnecessary attributes for specific notation types. The ordered list of attributes on the notes was kept in the same order until #97 is resolved.
A first editorial pass over the spec. Not many significant normative changes. - Grace notes groups were removed from the list of note features since they are a grouping mechanism and they follow their own rules - Similarly, the chord character was removed, since it functions more like a tie, and the order of ties and chords are not really established. (See #60, #2) - Specify that for neume notation, time sigs and key sigs MUST be omitted. This is following the decision to forbid durations on neumes, and the general direction of removing unnecessary attributes for specific notation types. The ordered list of attributes on the notes was kept in the same order until #97 is resolved.
I would not allow this. Only ties between the whole chords. |
Oh, that's an old, old comment. I'm way past that now. |
Based on #112 and #110, the same mechanism for tied notes can be applied to tied chords.
Would be two C Major chords tied together. Much like the notes, the
Would be a half-note C# Major chord tied over a barline to a quarter-note C# major chord. Note that this doesn't allow for repeating the accidentals in the following chord, so that's one limitation. But in a tied note the pitches are the same, so repeating is mostly a "cautionary" indicator. This, however, would be possible:
(Except that the first and second chords are tied) |
In the spec (V1) there is no explanation how to encode tied chords (the problematic is already mentioned in V2). Some users overcame this by applying own rules:
Whereas the second approach would only work if the two chords are identical, the first approach would give more flexibility if not all the notes in the chord are tied. However it would be to specify whether + or ^ should directly follow the note.
The text was updated successfully, but these errors were encountered: