Re: \appoggiatura disables autoBeam

If you comment out the \partial 4, then the beaming is normal. Does that solve this issue? Cheers, - Graham Andres wrote: I'm not top posting. %% removing \appoggiatura g16 it works as usual %% with \appoggiatura g16 every note appears alone %% tried new Voice, etc., but it doesn't work. \

Re: Weird lyrics-typesetting-bug

I think this is a duplicate of http://code.google.com/p/lilypond/issues/detail?id=329&can=2&q=two Cheers, - Graham Rune Zedeler wrote: The lyrics "two" and "three" are typeset on top of each other. It worked well in 2.10.10, so this is a regression. \version "2.10.25" \score { << \new Sta

Re: Crescendo text too close to dynamic mark

Kieren MacMillan wrote: Hi, Zoltán: %% I'm not sure whether it's wrong or not, but I think that %% the crescendo text is too close to the preceding dynamic mark. Yes, but I doubt this will be classified as a bug, since the mechanism is not intended to solve the problem you're showing. I be

Re: Changing slur positions doesn't work in dotted rythm

Sorry, I don't understand what you mean. When I view this example on my computer, I see a slur above the notes, with the slur some distance from the staff. Are you sure you want that \slurUp command in your example? Is this bug a problem with the slur direction, or the slur positions? Chee

Re: Beam on wrong staff (2.11.25)

Thanks, added as http://code.google.com/p/lilypond/issues/detail?id=369 Cheers, - Graham Jay Anderson wrote: I am not top-posting (for some reason gmane thinks I'm doing that here) In the first two measures of the following excerpt the beam ends up on the wrong staff. - When I take the sl

Issue 369 in project lilypond

Issue 369: \change Staff=foo affects beam too early http://code.google.com/p/lilypond/issues/detail?id=369 New issue report by gpermus: % the \change Staff=RH moves the final beam in the first bar from % the LH (where the notes are) into the RH. \version "2.11.24" \paper{ragged-right=##t} \new

Re: Ambitus uses lexicographical order instead of pitch height

Thanks, this has been added as http://code.google.com/p/lilypond/issues/detail?id=368 Cheers, - Graham Rune Zedeler wrote: Pitches are lexicographically ordered by octave, pitch, alteration. This means that i.e. even though eis is a higher pitch than fes, it is lexicographically smaller. And

Issue 368 in project lilypond

Issue 368: Ambitus uses lexicographical order instead of pitch height http://code.google.com/p/lilypond/issues/detail?id=368 New issue report by gpermus: %{ Rune Zedeler: Pitches are lexicographically ordered by octave, pitch, alteration. This means that i.e. even though eis is a higher pitch tha

\appoggiatura disables autoBeam

> I'm not top posting. %% removing \appoggiatura g16 it works as usual %% with \appoggiatura g16 every note appears alone %% tried new Voice, etc., but it doesn't work. \version "2.11.22" \score { \new PianoStaff << \relative c'' \new Staff { \key g \minor \partial 4 \appogg

Ambitus uses lexicographical order instead of pitch height

Pitches are lexicographically ordered by octave, pitch, alteration. This means that i.e. even though eis is a higher pitch than fes, it is lexicographically smaller. And because the ambitus engraver uses the lexicographical order to find the ambitus, it would prefer fes over eis as the top of t