lilypond-user
[Top][All Lists]
Advanced

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

Re: Help for \beamExceptions


From: David Kastrup
Subject: Re: Help for \beamExceptions
Date: Fri, 04 Sep 2015 20:20:19 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux)

Richard Shann <address@hidden> writes:

> On Fri, 2015-09-04 at 19:25 +0200, David Kastrup wrote:
>> Richard Shann <address@hidden> writes:
>> 
>> > On Fri, 2015-09-04 at 18:56 +0200, David Kastrup wrote:
>> >> Richard Shann <address@hidden> 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.
>
> which property do you refer to?

beamHalfMeasure.  What other property were we talking about right now?

>> At any rate, I don't understand why you are not using
>> \overrideTimeSignatureSettings to begin with rather than meddling
>> with the alists used internally.
>
> Is that to say that my explanation before "it applies
> to a particular instance of a time signature change, the user has to
> re-define (or cut and paste) to use it in another part of the score."
> was unclear?

It's wrong.

> As far as I can see, \overrideTimeSignatureSettings needs to be
> invoked at every time signature, rather than being applied to a
> complete book.

How did you reach that conclusion?  Have you _read_ the documentation of
\overrideTimeSignatureSettings I pointed you to?  Where does it say
anything like that?

> Please correct me if I am wrong, but at the moment I don't know how a
> user can place a something at the top of a LilyPond file that will
> result in a particular beaming rule being applied whenever they use a
> particular time signature.

\layout {
   \overrideTimeSignatureSettings ...
}

-- 
David Kastrup



reply via email to

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