[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Bad tuplet beam
From: |
Jay Anderson |
Subject: |
Bad tuplet beam |
Date: |
Sun, 4 Feb 2007 17:28:10 -0700 |
I managed to simplify my test file to get a segfault with the following:
=====
\version "2.11.16"
\paper
{
ragged-right = ##t
}
%57 - no segfault
%58 - segfault
spacer = { \repeat unfold 58 R2 }
\score
{
\new PianoStaff
<<
\new Staff = "RH"
{
\time 2/4
\clef treble
\spacer
r4 s |
\spacer
}
\new Staff = "LH"
\relative c'
{
\time 2/4
\clef bass
\spacer
<<
{
\times 2/3 {bes8 bes bes}
\change Staff=RH
\times 2/3 {bes bes bes} |
}
\\
{
s4 \change Staff=LH r4 |
}
>>
\spacer
}
>>
}
=====
I usually got this:
GNU LilyPond 2.11.16
Processing `test.ly'
Parsing...
Interpreting music...
[8][16][24][32][40][48][56][64][72][80][88][96][104][112][117]
Preprocessing graphical objects...Segmentation fault
But without changing the code I also got:
GNU LilyPond 2.11.16
Processing `test.ly'
Parsing...
Interpreting music...
[8][16][24][32][40][48][56][64][72][80][88][96][104][112][117]
Preprocessing graphical objects...ERROR: In procedure
ly:tuplet-bracket::calc-positions:
ERROR: Wrong type (expecting real number): ()
Really odd. I'm not sure what the difference was between the runs.
If you null out the 'spacer' variable you can see the beam for the
first set of triplets is misplaced (attached). Thanks!
-----Jay
test.png
Description: PNG image
- Bad tuplet beam,
Jay Anderson <=