Skip to content
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

Closed
carlolic opened this issue Oct 21, 2022 · 4 comments · Fixed by #110
Closed

Specify how to encode tied chords #60

carlolic opened this issue Oct 21, 2022 · 4 comments · Fixed by #110
Labels
Type: Spec Clarification Clarifications to existing content in the spec

Comments

@carlolic
Copy link
Collaborator

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:

  • adding a + after each note in the chord, e.g. C+^E+^G+C^E^G
  • adding a single + between the chords, e.g. C^E^G+C^E^G
    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.
@ahankinson
Copy link
Contributor

This should be considered with #2 and #1 as well.

<CEG>_<CEG>

or, to tie only certain notes in a chord,

<C_E_G><CEG>

@ahankinson ahankinson added the Type: Spec Clarification Clarifications to existing content in the spec label May 16, 2024
ahankinson added a commit that referenced this issue May 28, 2024
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.
lpugin pushed a commit that referenced this issue May 28, 2024
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.
@lpugin
Copy link
Contributor

lpugin commented May 29, 2024

or, to tie only certain notes in a chord,
<C_E_G><CEG>

I would not allow this. Only ties between the whole chords.

@ahankinson
Copy link
Contributor

Oh, that's an old, old comment. I'm way past that now.

@ahankinson
Copy link
Contributor

ahankinson commented May 30, 2024

Based on #112 and #110, the same mechanism for tied notes can be applied to tied chords.

^CEG>_

Would be two C Major chords tied together. Much like the notes, the _ would stand for the previously-stated chord, so it could also be part of other groups, or have its duration altered.

2^xCxExG>/4_

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:

2^CEG>8(6{_^DxFA>^EGB>})

image

(Except that the first and second chords are tied)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Spec Clarification Clarifications to existing content in the spec
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants