lilypond-user
[Top][All Lists]
Advanced

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

Re: beatLength / beaming in 4/4


From: Carl Sorensen
Subject: Re: beatLength / beaming in 4/4
Date: Mon, 14 Jun 2010 07:37:22 -0600



On 6/14/10 7:18 AM, "u_li" <address@hidden> wrote:

> Am 14.06.2010 15:04, schrieb Carl Sorensen:
>> 
>> 
>> On 6/14/10 5:24 AM, "u_li"<address@hidden>  wrote:
>> 
>>   
>>> [sorry if this should be a double post. When I first sent the message I
>>> didn't
>>> configure my current email client to use my registered address. As I don't
>>> see
>>> my post on the list I assume it didn't get through. If it did please ignore
>>> this second post ]
>>> 
>>> Dear community,
>>> 
>>> it seems I have yet another problem with automatic beaming (similar to
>>> problems I read about recently).
>>> What I want LilyPond to do is to beam consecutive 32th notes in a 4/4 time
>>> in
>>> groups of 4 (i.e. 8 groups of 1/8 length each).
>>>     
>> What version are you using?  This is an important question, because the
>> autobeaming is changing right now.
>> 
>> Thanks,
>> 
>> Carl
>>   
> The example file says "2.13.19" and this is probably true (I say
> probably because I am not at my lilypond computer right now).
> So I can just update regularly and hope that my issue ist right now
> being addressed?
> Would be quite good luck ;-)

I couldn't see the example file in my email (the forwarded email came
through as an inlined binary file).

beatLength only adjusts beaming if there is not an explicit rule for the
time signature.  beatLength is mostly used for beam subdivision, rather than
beam division.

See the Notation Reference for setting automatic beam behavior:
<http://lilypond.org/doc/v2.13/Documentation/notation/beams#setting-automati
c-beam-behavior>

You will need to use the overrideBeamSettings command to set this up.

There is currently a patch in review that will change this functionality.
So if you don't need the score in the next week or two, you might want to
wait until the patch is resolved.

Thanks,

Carl






reply via email to

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