Richard Shann <[email protected]> writes: > On Fri, 2015-09-04 at 18:56 +0200, David Kastrup wrote: >> Richard Shann <[email protected]> writes: >> >> > I seem to have run into a snag with re-writing >> > default-time-signature-settings, it works ok if there was previously a >> > rule for a time signature, but adding a rule for one (such as 6/8) which >> > has none doesn't result in the beaming pattern being used. Here is a >> > minimal example. The first bar shows the pattern desired, and this is >> > put into the value for 'beamExceptions in the 6/8 alist, but the second >> > bar is not then beamed to follow that pattern. >> >> That's likely because 6/8 triggers a special case relying on the context >> property >> >> (beamHalfMeasure ,boolean? "Whether to allow a beam to begin >> halfway through the measure in triple time, which could look like 6/8.") > > It sounds like I am tackling this at too low a level then. Is there a > more user-accessible way of setting the beaming rules for an entire > score containing many movements with a variety of time signatures?
Just unset the darn property if you don't want its effect. At any rate, I don't understand why you are not using \overrideTimeSignatureSettings to begin with rather than meddling with the alists used internally. -- David Kastrup _______________________________________________ lilypond-user mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-user
