lilypond-user
[Top][All Lists]
Advanced

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

Re: elegant compound time signatures


From: Graham Percival
Subject: Re: elegant compound time signatures
Date: Mon, 20 Oct 2008 02:21:32 -0700
User-agent: Mutt/1.5.18 (2008-05-17)

Trevor: a top-post in this case makes the thread really bloody
confusing to read.  (I know this email compounds the problem, but
I've given up on this thread)

Hans: at the risk of sounding grumpy, did you try compiling my
example?  I believe it does everything you want.

Trevor again: at the risk of sounding even grumpier, your solution
produces the same output as mine, but uses the much more confusing
#(override-beam...) stuff.  \set beamGrouping is much easier to
understand and use.

Cheers,
- Graham


On Mon, Oct 20, 2008 at 09:49:49AM +0100, Trevor Daniels wrote:
> Hans
>
> I'm not familiar with the whole rhythmic requirement but this seems to  
> reproduce the second bar of the snippet correctly.  Unfortunately  
> subdivideBeams still must be turned on/off manually if the (2+2) pattern 
> is required.  The key is setting the beatLength to 8 rather than the 16 
> derived from the time signature.
>
> (As I'm currently reviewing the Rhythms section of the Notation Reference 
> this might be a useful example of using beatLength)
>
> Trevor
>
> \version "2.11.62"
> \relative c'' {
>  \time 11/16
>  #(override-auto-beam-setting '(end 1 16 11 16)  4 16)
>  #(override-auto-beam-setting '(end 1 16 11 16)  7 16)
>  \set beatLength = #(ly:make-moment 1 8)
>  c16 b a g
>  g f a
>  g8 f16 e
>
>  \set subdivideBeams = ##t
>  c'16 b a g
>  \unset subdivideBeams
>  g f a
>  g8 f16 e
> }
>
> ----- Original Message ----- From: "Hans Aberg" <address@hidden>
> To: "Graham Percival" <address@hidden>
> Cc: <address@hidden>
> Sent: Monday, October 20, 2008 9:14 AM
> Subject: Re: elegant compound time signatures
>
>
>> On 20 Oct 2008, at 06:53, Graham Percival wrote:
>>
>>> On Sun, Oct 19, 2008 at 04:36:48PM +0200, Hans Aberg wrote:
>>>
>>>> This gankino horo snip is typeset as (2+2)+(2+1)+(2+2), again not
>>>> wrong,
>>>> but scores use the styles 4+3+4 or (2+2)+3+(2+2). (Hitting the
>>>> same 2+1
>>>> problem.)
>>>
>>> What, like this?  I think this is the second bar of the gankino
>>> horo snippet. Here's two ways of doing it, depending on how picky
>>> you want to be.
>>
>> Yes, both styles exist in my scores. It is though too complicated to
>> wrte stuff i each measure, as in your second example.
>>
>> I used:
>>   \tempo 4 = 120
>>   \time 11/16
>>   \set beatGrouping = #'(2 2 2 1 2 2)
>>   \set subdivideBeams = ##t
>>   #(override-auto-beam-setting '(end * * 11 16) 4 16)
>>   #(override-auto-beam-setting '(end * * 11 16) 7 16)
>> Now the beaming, in latest LilyPond 2.11.62, the beaming has changed to:
>>
>
>
> --------------------------------------------------------------------------------
>
>
>>
>> Changing the above to
>>   \set beatGrouping = #'(2 2 3 2 2)
>> does not change this output.
>>
>> - I think I know essentially what structure is needed to describe
>> these beaming patterns, and even went as far start writing a Haskell
>> program. But the it is a complicated problem.
>>
>>   Hans
>>
>>
>>
>
>
> --------------------------------------------------------------------------------
>
>
>> _______________________________________________
>> lilypond-user mailing list
>> address@hidden
>> http://lists.gnu.org/mailman/listinfo/lilypond-user
>>




reply via email to

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