On 8/11/10 9:25 AM, "Xavier Scheuer" <x.sche...@gmail.com> wrote:
> On 10 August 2010 14:42, Carl Sorensen <c_soren...@byu.edu> wrote:
>>
>> Yes, this is true. We currently do not have the capability of
>> setting multiple levels of subdivide; we only subdivide on the beat.
>>
>> The exact mechanism of getting multiple levels of subdivision is not
>> yet finalized. We may use a subdivide grouping rule, or we may just
>> use a nested beatStructure.
>>
>> As far as a time for its implementation, I'm not sure how long it
>> will be. I've looked into it, but I haven't yet got the architecture
>> firmly in mind for making it happen.
>>
>
> Thanks for the reply.
>
> I'm sorry I couldn't understand the "multiple levels of subdivision".
> Do you consider "non-subdivided" as one "level of subdivision"?
>
> For example, in 4/4 time, do you consider
>
> 4th as one level (with a beamExceptions
> ((end . (((1 . 8) . (4 4))
> ((1 . 12) . (3 3 3 3))))) ) ;
> 8th as another level (for what I want, i.e. 32th grouped by 8th
> subdivide
> baseMoment #'(1 8)
> beatStructure #'(2 2 2 2)
> **but only for 32th and shorter**) ;
>
> so "multiple levels of subdivision"?
I'm sorry, I mixed two different ideas in my earlier reply to you.
Obviously, for what you want, a beamExceptions entry with subdivide is the
correct solution.
Thanks for calling it to my attention,
Carl
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
