Re: Issue 60 in lilypond: beam multiplicity changing on rests

2008/6/4 Joe Neeman <[EMAIL PROTECTED]>: > Thanks Werner and Mats for the comments. I've made some further changes > to give the output that Werner suggested and to fix, in addition, bugs > 489 and 599. > > Is there anyone out there with strong opinions regarding beamlets and a > largish example to

Issue 213 in lilypond: progerror \bendAfter

Issue 213: progerror \bendAfter http://code.google.com/p/lilypond/issues/detail?id=213 Comment #4 by joeneeman: (No comment was entered for this change.) Issue attribute updates: Status: Fixed Labels: fixed_2_11_48 -- You received this message because you are listed in the owne

Issue 630 in lilypond: non-synchronized grace note makes voiceOne go stems down

Issue 630: non-synchronized grace note makes voiceOne go stems down http://code.google.com/p/lilypond/issues/detail?id=630 Comment #2 by hanwenn: I would expect that the real work around is to put \new Staff or \new Voice in the appropriate place. (untested) -- You received this message becau

Issue 68 in lilypond: certain \paper variables put music at the bottom of the page (easy workaround)

Issue 68: certain \paper variables put music at the bottom of the page (easy workaround) http://code.google.com/p/lilypond/issues/detail?id=68 Comment #4 by joeneeman: This is because after-title-space is so much larger than between-system-space in your example. Since both of these spaces are s

Issue 65 in lilypond: \accepts has problems with \with (lyrics should be between staves)

Issue 65: \accepts has problems with \with (lyrics should be between staves) http://code.google.com/p/lilypond/issues/detail?id=65 Comment #2 by joeneeman: (No comment was entered for this change.) Issue attribute updates: Status: Fixed Labels: fixed_2_11_48 -- You received th

Re: Issue 628 in lilypond: Regression: markup \note doesn't work as a TimeSignature stencil

Han-Wen Nienhuys wrote: 2008/5/30 Mats Bengtsson <[EMAIL PROTECTED]>: It cannot be that simple, since there are no font related settings on TimeSignature in scm/define-grobs.scm and the font related settings are done within ly:time-signature::print which ins't used here. There are d

Re: grace note makes voiceOne go stems down

Valentin Villenave wrote: 2008/6/4 Mats Bengtsson <[EMAIL PROTECTED]>: << { \grace b8 c c c c } \\ { \grace s8 g g g g } >> It doesn't work fine here! As far as I can see, it gives \voiceTwo settings in the first voice and \voiceOne settings in the second. Compare the stem di

Issue 630 in lilypond: non-synchronized grace note makes voiceOne go stems down

Issue 630: non-synchronized grace note makes voiceOne go stems down http://code.google.com/p/lilypond/issues/detail?id=630 Comment #1 by v.villenave: ... And that workaround doesn't work as expected! << { \grace b8 c c c c } \\ { \grace s8 g g g g } >> inverts voiceOne and voiceTwo. -- You r

Re: grace note makes voiceOne go stems down

2008/6/4 Mats Bengtsson <[EMAIL PROTECTED]>: >> << { \grace b8 c c c c } \\ { \grace s8 g g g g } >> > It doesn't work fine here! As far as I can see, it gives \voiceTwo settings > in the first voice and > \voiceOne settings in the second. Compare the stem directions to the case > without grace

Issue 34 in lilypond: Grace synchronization

Issue 34: Grace synchronization http://code.google.com/p/lilypond/issues/detail?id=34 Comment #3 by v.villenave: For whoever is going to work on this issue, please also have a look at Issue 630. -- You received this message because you are listed in the owner or CC fields of this issue, or b

Issue 631 in lilypond: Collision piano centered dynamics and cross-staff barlines

Issue 631: Collision piano centered dynamics and cross-staff barlines http://code.google.com/p/lilypond/issues/detail?id=631 New issue report by v.villenave: % When the dynamics have their own Voice, they tend to collide % with barlines. Adding the Bar_engraver doesn't help. \version "2.11.47" u

Re: piano centered dynamics

2008/6/4 Mats Bengtsson <[EMAIL PROTECTED]>: > This is a known problem that has not made it into the bug tracker, as far as > I can see. Now it has: http://code.google.com/p/lilypond/issues/detail?id=631 Cheers, Valentin ___ bug-lilypond mailing list