[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Bug: simple chord inversions take 2-octaves
From: |
Nucleos |
Subject: |
Bug: simple chord inversions take 2-octaves |
Date: |
Thu, 21 Jun 2012 17:32:59 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux i686; rv:12.0) Gecko/20120430 Thunderbird/12.0.1 |
Hello,
c major is : <c e g>
The first inversion would be <e, g, c>. This is what I call c/e.
The second inversion would be <g, c e>. This is what I call c/g
The code below triggers nevertheless Lilypond 2.14.2 to display <e, c g>
-- which is 2 octaves wide !
Weirdly, Lilypond seems to think my definition of inversions is right
for c/g (it displays <g, c e>), but uses a weird definition for c/e. Why
is that?
The code :
********************
\version "2.14.2"
{
\chordmode {
c1 c/e c/g
}
}
********************
I suggest the behaviour should be:
1) build the chord "c" is <c e g>
2) when the bass of the chord is given, take this bass and then follow
the natural order of "c e g c e g c e g"... and display three successive
notes of that sequence.
Cheers,
--
Nucleos
- Bug: simple chord inversions take 2-octaves,
Nucleos <=