[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: KeyCancellation spacing issue when staves have different key signatu
From: |
Neil Puttock |
Subject: |
Re: KeyCancellation spacing issue when staves have different key signatures |
Date: |
Tue, 4 Sep 2007 22:40:00 +0100 |
Hi Mats,
On 9/4/07, Mats Bengtsson <address@hidden> wrote:
>
>
> If you don't typeset the key cancellation when you change to C major,
> there's no
> way for the musician to recognize that you did a key change, right?
> Therefore
> LilyPond is clever enough to always print the key cancellations to C
> major, no
> matter if printKeyCancellation is set or not.
Yes, I should have realized that; I see that it is the fault of the
KeyCancellation object.
If you really want to get
> rid of it
> anyway (which means that you have to invent some other method to tell your
> musicians that there is a key change), you can use brute force:
> \override Staff.KeyCancellation #'stencil = ##f
>
I don't! I'd just like the extra space to be removed.
I've been thinking of a workaround which involves overriding KeyCancellation
#'stencil, then explicitly setting keySignature as a fake key cancellation.
I think this would work if I could work out how to set the order of the
accidentals.
In the documentation, there's the property keyAlterationOrder, but it
doesn't seem to work for new key signatures:
\set Staff.keyAlterationOrder = #'((6 . 0) (2 . 0) (5 . 0) (1 . 0) (4 .
0))%set accidental order
\set Staff.keySignature = #'(((1 . 1) . 0) ((1 . 2) . 0) ((0 . 4) . 0) ((0 .
5) . 0) ((0 . 6) . 0))%print fake key cancellation for D flat - C major
Any ideas why this doesn't work?
Thanks,
Neil
Re: KeyCancellation spacing issue when staves have different key signatures, Graham Percival, 2007/09/05