Status: Accepted
Owner: Carl.D.Sorensen
Labels: Priority-Critical
New issue 1456 by Carl.D.Sorensen: timeSignatureSettings does not apply to
any context except for those containing a Timing_translator
http://code.google.com/p/lilypond/issues/detail?id=1456
Although timeSignatureSettings can be specifed by context, the value that
is read when the \time command is executed comes from the Timing context.
Therefore, in the snippet below, both staves get (2 2) beaming, even though
we have asked for (3 1) and (1 3).
\version "2.13.43"
\score {
\new StaffGroup <<
\new Staff {
\overrideTimeSignatureSettings
#'Staff % context
#'(4 . 4) % timeSignatureFraction
#'(1 . 4) % baseMomentFraction
#'(3 1) % beatStructure
#'() % beamExceptions
\time 4/4
\repeat unfold 8 {c''8}
}
\new Staff {
\overrideTimeSignatureSettings
#'Staff % context
#'(4 . 4) % timeSignatureFraction
#'(1 . 4) % baseMomentFraction
#'(1 3) % beatStructure
#'() % beamExceptions
\time 4/4
\repeat unfold 8 {c''8}
}
>>
}
This is a difficult bug. Although it may make sense to have different
timeSignatureSettings for different staves, when we change the time
signature it is difficult (if not impossible) to change the context
settings for each of the staves.
The proper fix may be to remove the context argument from
\overrideTimeSignatureSettings and always have it apply to the Timing
alias. Thus, if we have have the Timing_translator moved to the Staff
context, then \overrideTimeSignatureSettings would apply to the Staff
context; it would not be the user's choice as to which context the setting
applies.
Attachments:
time-sig-context.png 10.1 KB
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
