[Top][All Lists]

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

Re: Partial Bars

From: Simon Albrecht
Subject: Re: Partial Bars
Date: Fri, 03 Jul 2015 10:53:01 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0

Very good example. However, I have two major points to make here:
– As Lily correctly handles it, both alternatives always start at the same bar number (at least in this convention counting repeats only once). Thus, the close of the minuet would have bar 16a for the first, 16b for the second alternative and (16b) for the partial measure opening the trio. (The other convention to which I’m alluding would have 24, 32, and (32) respectively, but that isn’t yet supported by Lily.)
– The second alternatives closing both Minuet and Trio need a \set Timing.measurePosition = #(ly:make-moment 0) at the beginning. With your score, I get two failing bar checks. This workaround is documented AFAIK.
– And a small, unrelated remark: the upbeat for the Trio should read r8 r4, not the other way round :-)

Correct version attached.
Yours, Simon

Am 03.07.2015 um 09:06 schrieb David Kastrup:
Pierre Perol-Schneider <address@hidden> writes:

Oops! here again.
Try the following example:

Your problem was that you declared partial bars at the end of each
movement to be "complete" and gave them bar checks and whole-bar rests.

That's not going to fly with LilyPond.  It _is_ actually possible to
make LilyPond treat them like that, but then you have to declare the
length of the bar at its _start_ by using \partial on it.  Here is how
to do that:

The latter version lets you use a "full-bar rest" at its end (but I
think that is a rather bad idea since the reader will have a hard time
figuring out its actual length) and will result in more measures since
then the partial bar at the start of the second movement gets its own
measure number.  I'm not convinced that is a good idea either but then
it's probably a question of what was written in the original.

lilypond-user mailing list

Description: Text Data

reply via email to

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