[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: simple chord inversions take 2-octaves

From: Phil Holmes
Subject: Re: simple chord inversions take 2-octaves
Date: Thu, 21 Jun 2012 17:24:39 +0100

"Nucleos" <address@hidden> wrote in message news:address@hidden

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.

This doesn't help you, but for my money, both inversions are incorrect. Correct inversions would look as attached. Wonder if it's an artifact from relative note placement?

Phil Holmes
Bug Squad

Attachment: chordmode.png
Description: PNG image

reply via email to

[Prev in Thread] Current Thread [Next in Thread]