Re: [Lilypond-auto] Issue 2617 in lilypond: simple chord inversions take 2-octaves

[lilypond]

Updates:
        Status: Fixed
        Labels: -Patch-push Fixed_2_19_11

Comment #11 on issue 2617 by address@hidden: simple chord inversions take  
2-octaves
http://code.google.com/p/lilypond/issues/detail?id=2617

Pushed to staging as
commit 537684520ca3ffa36477042e737aa0b3c14f3004
Author: David Kastrup <address@hidden>
Date:   Thu Jul 10 15:18:38 2014 +0200

    NR: Adapt docs for inversions in chordmode

commit 080d6ab968012d491c7fa70fa962d2001ace1ecc
Author: David Kastrup <address@hidden>
Date:   Wed Jul 9 17:31:11 2014 +0200

    Issue 2617: simple chord inversions take 2 octaves

    With this change, chord inversions transpose all notes following the
    inversion from the original chord down along with the inversion, as long
    as the result ends up below the root note of the uninverted chord.

    So with \chordmode { c:11 } => < c' e' g' bes' d'' f'' >
    we get \chordmode { c:11/e } => < e g bes c' d'' f'' >

    In order to have the Chord_name_engraver reconstruct the correct
    uninverted chord, all the additionally octavated note events are given
    an octavation property like the inversion event itself.

    An "inversion" on the chord root just transposes the chord root one
    octave down, leaving the rest in place.

Let's hope we don't get too much of a backlash because of incompatibility.   
The manual previously just stated that you should forget about being able  
to generate a first inversion, so if people heeded that advice, they won't  
notice things having become sensible.  It's hard to imagine that the kind  
of semi-inverted chords produced previously actually saw much use:  
musically they don't make a lot of sense, particularly not under the name  
with which they were called into being.

And the manual did not even attempt to call them anything but unusable.

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings