music. Switching to using
melismas and toggling autobeaming helped quite a bit, and adding a
macro to simplify that made the vocal parts as easy to enter as the
instrumental parts.
- Russ
On Apr 3, 2005 10:34 PM, Erlend Aasland <[EMAIL PROTECTED]> wrote:
> On Apr 3, 2005 6:55 PM, Rus
ot;, and it is
pretty common in vocal music.
Thanks,
Russ
On Mar 30, 2005 10:25 PM, Russ Ross <[EMAIL PROTECTED]> wrote:
> There seems to be a bug in \autoBeamOff. If it is issued in the
> middle of a sequence of notes that would be beamed together, it
> doesn't take effect unt
There seems to be a bug in \autoBeamOff. If it is issued in the
middle of a sequence of notes that would be beamed together, it
doesn't take effect until after the end of that group. It seems that
the correct behavior should be to stop automatic beaming at the point
where the command is issued.
I tested 2.3.20 and it still crashes on a bunch of scores.
- Russ
On Wed, 29 Sep 2004 21:06:39 +0100, Russ Ross <[EMAIL PROTECTED]> wrote:
> I'm getting segmentation faults now, with those two scores and with
> several other smaller ones. Not sure if its related to the f
s the segfault now.
- Russ
On Wed, 29 Sep 2004 01:37:22 +0200, Erik Sandberg
<[EMAIL PROTECTED]> wrote:
> On Thursday 23 September 2004 18.33, Russ Ross wrote:
> > I just compiled 2.3.18 on a Debian system and got this error:
> >
> > lilypond: ../flower/include/array.hh:149: T
> > Finally, hyphens within words are not always displaying properly.
> > Where before they would be centered between two syllables, now they
> > sometimes stick to the second syllable.
>
> I don't think I have seen this problem. Could you find an example?
Certainly; here's a snippet from a recit
I've just compiled Lilypond 2.3.18 and noticed a couple of differences
in lyrics output:
Before (in 2.2.x) I'd put this in my \paper section to prevent lyrics
overlapping bar lines:
\context \LyricsContext \consists "Bar_engraver"
convert-ly changes \LyricsContext to \Lyrics but this no longer
I just compiled 2.3.18 on a Debian system and got this error:
lilypond: ../flower/include/array.hh:149: T& Array::elem_ref(int)
const [with T = void*]: Assertion `i >=0&&ihttp://lists.gnu.org/mailman/listinfo/lilypond-devel
I've been setting a large choral/orchestral work and noticed one way
in which the default output from LilyPond is suboptimal. I'd like to
request a feature to address this, and I think it fits nicely with the
philosophy of output being correct by default.
When the stem direction of a note or grou
