Have fun with testing!
\version "2.19.25"
#(set-global-staff-size 30)
chordtest = \chordmode {
c:sus %power chord Lilypond calls it wrong as C
c:sus3 % power chord Lilypond calls it correctly as C
c:sus5 %power chord Lilypond calls it wrong as C
c:1.4.5 % equal to:
c:sus4
c:1.5.2 % equal to:
c:sus2
c:sus3 % normal c major chord Lilypond calls it correctly as C
c:5.3 % normal c major chord Lilypond calls it correctly as C
c:5.3+ % normal c major chord Lilypond calls it correctly as C,
%3+ is written as e#
c:sus6
c:sus7
:sus
c:7sus
c:7
c:3.5.30
c:5.30
c:m30
c:m
c:min
c^3
c:5
}
<< \context ChordNames \chordtest
\context Voice \chordtest
>>
On 20.09.2015 14:31, Thomas Morley wrote:
2015-09-20 14:14 GMT+02:00 BB <[email protected]>:
I absolutely agree! I did not understand as I read that Lilypond now
supports misbehavour of some lazy people with reduced harmonic skills.
There are a bunch of "coloured" sus chords, not just sus4 for every sus
sign.
No idea if anyone tested my recent proposal, seems not.
From the user's point of view it simply aliases
c:sus to c:sus4
and
c:5 to c:1.5 or c^3
no other sus is changed or impossible to use, c:5 will only work if
the 5 is the one and only modifier, hence no other stuff is concerned.
If it turns out that my low tested proposal doesn't warrant this, it
needs more work, ofc.
Though, I really don't understand why people don't test and give feedback.
Instead more and more mails cumulate.
-Harm
P.S.
David announced an own patch. I'm quite confident he will do better
work than me.
On 20.09.2015 13:38, Johan Vromans wrote:
So what is the big deal to write c:sus4 when you want to designate your
flavour of Csus?
_______________________________________________
lilypond-user mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-user
_______________________________________________
lilypond-user mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-user
