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?
[ ... ]
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);
On Wed, 29 Sep 2010 08:46:46 -0700, Carl Sorensen <[email protected]> wrote:
I think that autobeaming in cadenzas should beam according to baseMoment,
i.e. all beats should be grouped together in baseMoment units.
Yes, this could be a simple feature request, but I do not request this feature.
Looking at how \cadenzaOn is used in practice (by google \cadenzaOn
site:www.mutopiaproject.org) it seems that manual beams (or using \bar""
instead of \cadenzaOn) are clean solutions.
Also, \cadenzaOn is a simple LilyPond definition in property-init.ly, so users
like me can reasonably adapt that definition (probably implementing the rule
that Carl suggested) and submit a feature _suggestion_ if our own definition
works well.
The reason I raised this issue is that while creating scores I _thought_
autobeaming worked in cadenzas (along the lines Carl suggests) and version
2.12.3 did so for the length of a couple cadenzas. LilyPond's irregular
behavior could frustrate users, but that can be solved with:
@knownissues Automatic beaming rules are unlikely to produce the desired beams
in cadenzas longer than one or two beats, so it is best to specify beams
manually with @code{[} and @code{]}.
--
Keith
_______________________________________________
bug-lilypond mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-lilypond
