[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Chord names broken since 2.16
From: |
Amelie Zapf |
Subject: |
Chord names broken since 2.16 |
Date: |
Sun, 15 Mar 2015 10:57:59 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 |
Dear lilypond-user team,
starting with LilyPond 2.16, and on into 2.18, the chord naming
algorithm does not distinguish between a chord <c e g bes d> and <c e g
d'> in relative notation. Both are named "C9". This is wrong, since
functionally, the former is a dominant, the latter a tonic, so there
must be a distinction between the two. The behavior up until 2.14 (which
I used until recently) was correct, in which the former was called "C9",
the latter "Cadd9".
Is there a script file I can modify so I can get the system to behave
correctly?
Kind regards,
Amy
- Chord names broken since 2.16,
Amelie Zapf <=
- Re: Chord names broken since 2.16, Amelie Zapf, 2015/03/15
- Re: Chord names broken since 2.16, Thomas Morley, 2015/03/15
- Message not available
- Re: Chord names broken since 2.16, Thomas Morley, 2015/03/15
- Re: Chord names broken since 2.16, Johan Vromans, 2015/03/15
- Re: Chord names broken since 2.16, Jan Kohnert, 2015/03/15
- Re: Chord names broken since 2.16, Kieren MacMillan, 2015/03/16
- Re: Chord names broken since 2.16, Jan Kohnert, 2015/03/16
- Re: Chord names broken since 2.16, Johan Vromans, 2015/03/17
- Re: Chord names broken since 2.16, Jan Kohnert, 2015/03/17
Re: Chord names broken since 2.16, Jan Kohnert, 2015/03/15