bug-lilypond
[Top][All Lists]
Advanced

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

Issue 2361 in lilypond: Beams with multiple subdivisions


From: lilypond
Subject: Issue 2361 in lilypond: Beams with multiple subdivisions
Date: Mon, 27 Feb 2012 00:53:11 +0000

Status: Accepted
Owner: ----
Labels: Type-Enhancement

New issue 2361 by address@hidden: Beams with multiple subdivisions
http://code.google.com/p/lilypond/issues/detail?id=2361


Carl Sorensen posted to request this enhancement to Lilypond:

http://lists.gnu.org/archive/html/bug-lilypond/2012-02/msg01097.html
http://article.gmane.org/gmane.comp.gnu.lilypond.general/70226

Original enhancement request follows, including David Bobroff's post to lilypond-user:

On 2/26/12 2:10 AM, "David Bobroff" <address@hidden> wrote:

I'm looking for a way to achieve this beaming pattern:

http://notendur.centrum.is/~bobroff/lily/complex-beam.png

Can LilyPond do this?  I suspect I'll have to use a combination of
subdivideBeams and stemRightBeamCount/stemLeftBeamCount.  Is there a
known solution?

Thanks,

David




Lilypond does not currently do "second-level" beam subdivisions.

Please add this as a feature request.  I have been looking for a good
example of what it means to have multiple subdivision.

I believe this can be achieved; I will try to get to it in the next couple
of weeks.

I believe this beaming could be expressed as something like:

(subdivide . ((1 . 8) . (1 1 1))
             ((1 . 16) . (1 1 1 1 1 1)))

although I am not proposing this as the syntax.

It might be better to change subdivideBeams from a boolean to a list,
where each element of the list would be a beat length at which to
subdivide.  If that were the case we would achieve the beaming in the
sample by

\set subdivideBeams = #'((1 . 8) (1 . 16))

Or perhaps

\set subdivideBeams = #'((ly:make-moment 1 8)
                         (ly:make-moment 1 16))

Or perhaps even (with David K's new syntax, where we can have duration
elements)

\set subdivideBeams = #'( 8 16 )

I'll put this in the hopper and think about it.

Thanks,

Carl





reply via email to

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