[Top][All Lists]

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

Re: Settings for bagpipe music

From: Stephen
Subject: Re: Settings for bagpipe music
Date: Fri, 29 Jul 2005 09:12:51 -0500

Oh yeah, Sven

It is interesting that Sven is the goto man for preserving a great Scottish music tradition.

You could adapt the technique used for Atonal music in the Nicolas' atonicKey funtion as I modified it. put it in D major and supress the printing of the key signature with the line:

\override Score . KeySignature #'print-function = ##f

You would then have to put it in the key of D major in order to suppress C sharp and F sharp it think. I am not sure of the effect that renaming the pitch names has however.

Adding new pitch names to the list might be a good idea too:

(bb . ,(ly:make-pitch 0 6 FLAT))
(Bb . ,(ly:make-pitch 1 6 FLAT))

for instance.

I think removing the Auto Engraver is a mistake. You can just put everything in the key of D major to suppress the C and F sharp while still getting a flat if you need it.

I am repeating myself aren't I? To recap, my idea is to keep the key signature and accidental engraver and just suppress the printing of the key signature as a way to print flats when you need them.


----- Original Message ----- From: "Sven Axelsson" <address@hidden>
To: <address@hidden>
Sent: Friday, July 29, 2005 2:15 AM
Subject: Settings for bagpipe music

I've been using Lilypond to write music for the Scottish highland bagpipe for
a while now, and have made a fairly complete package to handle the complex
grace notes used. I suggest this should be included in the official
distribution to save everyone from the hassle of doing it themselves.

I've attached the settings file together with an example of the notation
available. In case attachments are stripped, the same file can also be
downloaded here:

Bagpipe music is a bit special since it is written without a key signature
even though it actually has a signature (D major). The way I deal with this by removing the Key_engraver and Accidential_engraver might not be optimal since there are instances (though very rare) where you do like to show accidentials on certain notes. I provide a \flatten markup for those cases, but maybe there
is a better way?
Sven Axelsson


lilypond-devel mailing list

reply via email to

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