[Top][All Lists]

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

Subdivided beams

From: Urs Liska
Subject: Subdivided beams
Date: Thu, 23 Apr 2015 18:06:35 +0200
User-agent: Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.6.0

I had the opportunity to have a look in the German translation of "Behind Bars" (which is BTW an exceptionally good translation. Usually I prefer reading this kind of books in the original language, but here I don't see any problems reading the translation).

There I found a rule where LilyPond's behaviour differs. The rule makes perfect sense to me, and the (very few) examples I could immediately find confirm it.

Consider the following example of beam subdivision

According to Gould (sorry, I don't own the book, so no page number available) the rhythmical organization is indicated by the number of remaining beams in the subdivisions. Depending on the length of the following group there should remain one or more beams.

In the example in the docs the third beat is correctly divided in two groups of a quaver's length, thus having a single beam in the middle. But in the fourth beat the first and the third subdivision should have *two* beams, indicating that they separate groups of a sixteenth note length each.

From the description it seems that LilyPond doesn't do that and can't easily be talked into doing it, so this seems an "embarrassing" bug.

First question: is it possible to engrave that at all, i.e. create one beam with different subdivisions? If yes, this should be investigated, documented and made available with a reasonable interface (I mean an interface that is not more complicated or obscure than the subdivision interface described there already). If that's possible one should preferrably see if it's possible to let LilyPond do it correctly automatically. I mean: From what Gould writes and what I have seen in at least one Henle-Mozart score the subdivision beaming structure is directly related to the note values. So it should usually not be necessary to fiddle around with baseMoment and/or beatStructure at all.


reply via email to

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