On 3/28/17 9:06 AM, "Winston, Charles R." <charles.wins...@tufts.edu> wrote:
>Is the main goal of this project to expand the functionality of chord >mode, so as to allow the user to input arbitrarily complex chords? Or is >it to develop a more powerful internal interpretation of > chorded notes (i.e. <c e g>)? Your example of the problematic ambiguity >in the chord <c e gis> ‹ is it C aug, E aug, or G# aug? ‹ is what makes >me think it is probably the latter, because if the user were to enter >into chord mode c:aug, e:aug, or gis:aug there > would be no ambiguity. The main goal of this project is to develop an internal representation of chords that captures the appropriate musical semantics. Once we have the appropriate internal representation, we can then move in two additional directions: Strengthen/simplify the chord name output Improve the chord mode input But these two projects only follow the first. As mentioned, when the user enters c:aug, e:aug, or gis:aug there is no question in the source file. But once this is translated into a list of pitches, the semantics are lost. So the difference is no longer reflected in the internal representation. That's what we're trying to fix. Hope this helps, Carl _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel