Issue 733 in lilypond: Non-standard octave-limited key signature does not persist

[codesite-noreply]

Status: Started
Owner: v.villenave
Labels: Type-Defect Priority-Medium

New issue 733 by v.villenave: Non-standard octave-limited key signature  
does not persist
http://code.google.com/p/lilypond/issues/detail?id=733

Report from Trevor D:

If a non-standard key signature is defined using the format which limits
the alterations to a single octave, the alterations defined in the key
signature persist only up to the end of the first bar which contains a
pitch to be altered.
They should persist indefinitely.

In this example the F# and Ab are notated correctly only in bar 1.  A Bb
does not appear until bar 3, when it is notated correctly, but is incorrect
in bar 4.

\relative c' {
 \set Staff.keySignature = #`(((0 . 3) . ,SHARP)
                             ((0 . 5) . ,FLAT)
                             ((0 . 6) . ,FLAT))
 fis fis aes aes
 fis fis aes aes
 fis aes bes bes
 fis aes bes bes
}

If the alternative (not limited to a single octave) form is used the key
alterations do correctly persist indefinitely:

\relative c' {
 \set Staff.keySignature = #`((3 . ,SHARP)
                             (5 . ,FLAT)
                             (6 . ,FLAT))
 fis fis aes aes
 fis fis aes aes
 fis aes bes bes
 fis aes bes bes
}

% Neil promised a patch :-)


--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings