Issue 282 in project lilypond
Issue 282: tuplet bracket printed over the wrong staff http://code.google.com/p/lilypond/issues/detail?id=282 Comment #4 by hanwenn: Can we have a separate issue with new image for this problem? closing since tuplet now works. Issue attribute updates: Status: Fixed -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 160 in project lilypond
Issue 160: keep-inside-line fails with \markup
http://code.google.com/p/lilypond/issues/detail?id=160
Comment #4 by hanwenn:
\new Score \with {
\override PaperColumn #'keep-inside-line = ##t
}
\relative {
c4^\markup { \italic "sempre non legato" } c c c
}
--
note that PaperColumn overrides always happen a timestep late.
Issue attribute updates:
Status: Invalid
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 137 in project lilypond
Issue 137: ties in cords sometimes collide with notes http://code.google.com/p/lilypond/issues/detail?id=137 Comment #2 by hanwenn: This has been fixed, probably a long time ago now. Issue attribute updates: Status: Fixed -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 51 in project lilypond
Issue 51: collision dot and notehead http://code.google.com/p/lilypond/issues/detail?id=51 Comment #1 by hanwenn: (No comment was entered for this change.) Issue attribute updates: Status: Fixed Labels: fixed_2_11_22 -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 281 in project lilypond
Issue 281: manually placed staccato dot centered on stem, not notehead http://code.google.com/p/lilypond/issues/detail?id=281 Comment #1 by hanwenn: (No comment was entered for this change.) Issue attribute updates: Status: Fixed Labels: fixed_2_10_22 fixed_2_11_22 -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
cross staff/voice arpeggio error
The example below produces garbled output. If you add \arpeggio to the
first c2 in the top staff no errors are produced (except I don't want
the arpeggio to extend up there :). Here's the error:
GNU LilyPond 2.11.21
Processing `test3.ly'
Parsing...
Interpreting music...
Preprocessing graphical objects...
warning: vertical alignment called before line-breaking.
Only do cross-staff spanners with PianoStaff.
Layout output to `test3.ps'...
Converting to `test3.pdf'...
\version "2.11.21"
\layout
{
ragged-right = ##t
}
\new PianoStaff
<<
\set PianoStaff.connectArpeggios = ##t
\new Staff
\relative c''
{
c2 c2\arpeggio
}
\new Staff
\relative c''
{
<<
{
c2\arpeggio c2\arpeggio
}
\\
{
g4\arpeggio a g4\arpeggio a
}
>>
}
-Jay Anderson
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: artificial harmonics notation
As you have noticed, \harmonic only works within a chord. I'm not sure why the program is designed this way, since it's perfectly valid notation practice to notate a harmonic with a single diamond shaped note head, i.e. with only a single note in the chord. You have exactly the same problems with fingerings if you want to specify a fingering to the left or right of a note head, then \set fingeringOrientations = #'(left) c'-3 doesn't work, whereas \set fingeringOrientations = #'(left) gives the desired output. This may seem to be completely unrelated but it turns out that the same engraver handles both fingerings and harmonics in the current implementation. I can easily add a few lines to the manual, clarifying that \harmonic only works within a chord, but I think that it would be better to fix the implementation. /Mats Jon Alvarez wrote: Hi, It happens that, when I wnat to write an harmonic pitch, it doesn't work just with: a4\harmonic Instead, if I write it as an "one-note chord": It works. Is the program suposed to work like that? I'm a 2.6.0 version user. Perhaps you fixed it in later versions. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond -- = Mats Bengtsson Signal Processing Signals, Sensors and Systems Royal Institute of Technology SE-100 44 STOCKHOLM Sweden Phone: (+46) 8 790 8463 Fax: (+46) 8 790 7260 Email: [EMAIL PROTECTED] WWW: http://www.s3.kth.se/~mabe = ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
