for the middle tuplet won't be printed
\relative c' {
\times 2/3 {r8 c4} \times 2/3 {r8 c'4} \times 2/3 {r8 c c}
}
Kind regards,
Tuukka Verho
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Every time a slur and a DynamicLineSpanner begin from the same note, a
following warning is printed:
GNU LilyPond 2.11.15
Processing `testi.ly'
Parsing...
Interpreting music...
testi.ly:5:11: warning: Ignoring grob for slur: DynamicLineSpanner.
avoid-slur not set?
c4(
\
c c} c4 c c
c4 c c c
}
On Tue, 30 Jan 2007, Graham Percival wrote:
Sorry, I cannot duplicate this in 2.11.14. Are you certain that you used
this version? (not 2.11.4 or 2.10.14 ?)
Cheers,
- Graham
Tuukka Verho wrote:
In 2.11.14, if one enters a tuplet shorter than tupletSpannerDuration
In 2.11.14, if one enters a tuplet shorter than tupletSpannerDuration,
the bracket won't be terminated correctly. The bug didn't occur in
2.10.0.
A minimal example:
\version 2.11.0
\paper {ragged-right = ##t}
\relative c' {
\set tupletSpannerDuration = #(ly:make-moment 1 8)
}
IMO the trill should be at least twice as long as it is in the example.
Notice also the weird placement of the second trill.
You can also see the problem in the trill spanner regression test.
http://lilypond.org/doc/v2.9/input/regression/collated-files.html
Tuukka Verho wrote:
Version
as it should (like with \trill).
However, even with these problems I see this as an improvement to the
previous behaviour -- the tendency to extend the trill line over the
next note was very annoying in earlier versions. Thanks to the
developers for fixing that!
Tuukka Verho
Printing page numbers seem to be disabled by default in 2.8. You can
enable it by setting print-page-number = ##t in \paper block.
http://lilypond.org/doc/v2.8/Documentation/user/lilypond/Page-formatting.html#Page-formatting
I wonder why the default setting has been changed?
Tuukka Verho
Another way is setting the 'avoid-slur property for the script. I don't
know if there is an easy way to override invidual script settings, this is
kind of a hack:
#(define set-script-property (lambda (script property value)
(append! (cdr (assoc script default-script-alist))
(list
Broken ties starting from an eight note that is on a staff line are
barely visible in 2.8.1. I wonder if this is intentional...
\paper {
ragged-right = ##t
}
\relative f''
{
f2( f4. f8~ \break%% this looks bad
f2) e4.( e8~ \break %% this is ok
e1)
}
- Tuukka
I find the default spacing in Lilypond too tight for most purposes, so I
usually add \override Score.SpacingSpanner #'shortest-duration-space = #3 to
my parts. I noticed, however, that when there is a time signature or key
change at the end of a system, the last note is set too close to the
The following code causes a segmentation fault:
\version 2.8.0
{
\set tupletSpannerDuration = #(ly:make-moment 1 4)
\times 2/3 {c' c' c'}
}
The compiler output:
GNU LilyPond 2.8.0
Processing `testi.ly'
Parsing...
Interpreting music... [1]
Preprocessing graphical
In 2.7.39 the bar number placement behavior is rather odd. When there is no
key signature, bar numbers are typeset in the left hand side of the clef as in
previous versions, but otherwise they are placed next to the key signature.
The following code demonstrates the issue:
\version 2.7.39
This code:
\book {
\score {
\header {piece = piece}
\new Staff {
c'4 c' c' c'
}
}
}
gives the following error:
GNU LilyPond 2.7.38
Processing `testi.ly'
Parsing...
testi.ly:3:16: error: syntax error, unexpected \\header
13 matches
Mail list logo
