|
From: | 70147persson |
Subject: | Re: Re: Chords and what they mean |
Date: | Thu, 17 Sep 2015 16:18:28 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 |
I had already discovered the "chordnameexceptions", but as I do not know the Scheme language (yet), I had not seen exactly how to use it. And the explanation in the Notation Reference is really not very exhaustive. So the construct with "powerChordExceptions" was new to me, as well as that with "\powerChords". Even if I had already come in contact with power chords and roughly understand what they mean, it was first after following your advice, I found them in the "Guitar" section. I had really not looked there, as my target was a piece of piano music.
But thank you everybody for your contribution to my new knowledge. /Kaj On 2015-09-17 13:29, pls wrote:
Thomas Morley <address@hidden> writes:2015-09-17 10:47 GMT+02:00 Simon Albrecht <address@hidden>:Hello Kaj, On 17.09.2015 09:27, address@hidden wrote:First I will declare, that I am not 100 percent sure this is a bug, but friends of mine, musicians, say it probably is. Also, as I am not an expert, I have tried to learn by searching on among others Wikipedia. It is about chords, a few of them. It started when I should clean write a score from a manuscript. In one measure there were noted two chords, C5 and C. Obviously not the same, as they stood just beside of each other. A search on Wikipedia also told me, and this was also confirmed, the author's intention, that C5 means C(no 3), hence <c g>, while the chord C means <c e g>. But LilyPond treats these two the same and produces the same notes. This is also clearly said e.g. in Appendices A.1 and A.2 of Notation Reference, as well as in the text part. However even if possibly a correct procedure, is it a correct practise? Another such discrepancy is about Csus, which Wikipedia (and my friends) says is equivalent to Csus4, hence <c f g>. But LilyPond produces <c g>, hence what should come from the notation C5 as in the previous paragraph. So, what is the truth?There are others who are more into the subject, but I may say: There is no ‘truth’. With chord names, there are so many different conventions and fiercely defended convictions that it’s impossible to define a single ‘standard’ naming scheme. (Edit: just like the NR says)Very true. It's a mess, but LilyPond can handle it. ;)Many things in the chords rendering may be overridden in LilyPond. In case you’re not aware yet, check out <http://lilypond.org/doc/v2.18/Documentation/notation/displaying-chords#customizing-chord-names> and perhaps the LSR <http://lsr.di.unimi.it>. If that doesn’t cover your wishes, you may come back with a code example, I’d suggest. HTH, Simonchrds > \chordmode { \set chordNameExceptions > #(append powerChordExceptions ignatzekExceptions) c:1.4.5 c:1.5 \notemode { <c' f' g'> <c' g'> } } << \new Staff \chrds \new ChordNames \chrds If it's not sufficient you can set your own 'exceptions' for chord-naming, see the links Simon provided. HTH, HarmIt's not necessary to define power chord exceptions. They are already defined. All you have to do is: chrds = \powerChords % e.g. \chordmode { c,:1.5 } % or e.g. <c, g> } << \new Staff \chrds \new ChordNames \chrds BTW: The power chord examples here: http://lilypond.org/doc/v2.19/Documentation/notation/common-chord-modifiers are not complete. The chord names are missing. hth patrick
[Prev in Thread] | Current Thread | [Next in Thread] |