On 9/29/10 4:18 AM, "Dmytro O. Redchuk" <[email protected]> wrote:
> On Wed 29 Sep 2010, 02:35 Keith E OHara wrote: >> On Wed, 29 Sep 2010 00:13:44 -0700, Dmytro O. Redchuk >> <[email protected]> wrote: >> >>> Sorry, why do you expect it to work? I wouldn't expect, because of the >>> nature >>> (my understanding of) of cadenza... >>> >> >> Dmytro, >> Very good point. >> >> Reasons to expect auto-beaming to work: >> >> Even though a cadenza has a free rhythm and is not divided into bars, it >> usually has a rhythmic structure, and is written using the usual conventions >> of music with a beat. Beethoven's 'emperor' concerto (small image attached) >> opens with a cadenza, but is written using tuplets and beams to show how the >> notes fit in the underlying pulse. Most cadenzas are simpler (Chopin image >> attached). >> >> The examples for \cadenzaOn in NR 1.2.3 show notes that are autobeamed, which >> implies that users can expect autobeaming to work. >> >> Autobeaming _tries_ to work: if the notes are beam-able, at least some of >> them are auto-beamed according to the time signature in effect before >> \cadenzaOn. >> >> >> Reasons we should not expect auto-beaming to work: > No, i can agree that autobeaming should (or "would be great to") work in > cadenzas; but i can not imagine how to describe expected behavior. > > _How_ this should work? > > This can be a valid issue report (most probably enhancement/feature request); > please, could you modify your initial "minimal example" -- include some > explicit autobeaming rule[1] and describe what you expected to have. > (I hardly can imagine which autobeaming defaults should be in cadenzas.) > > Thanks! I think that autobeaming in cadenzas should beam according to baseMoment, i.e. all beats should be grouped together in baseMoment units. Thanks, Carl _______________________________________________ bug-lilypond mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-lilypond
