On Wed, 2006-04-19 at 18:57 +0200, Mats Bengtsson wrote:
> What did you expect the example to do?
Nothing--but it came from reducing the following code, which worked in
2.6 and 2.7 (at least up to 2.7.40, I think) for writing a MIDI file
with one channel per voice instead of one channel per staff.
\include "english.ly"
\version "2.8.0"
topRight = \relative c' {
\key a \major
\time 4/4
fs2 \clef bass cs
d b |
\oneVoice d,1\rest \voiceOne
}
\score {
\context Staff {
\context Voice {
\voiceOne \topRight
}
}
}
The manually positioned clef
It certainly looks like a bug, so I forward it there.
/Mats
Jefferson dos Santos Felix wrote:
Another example, to illustrate the problem (I think it's a bug)
\score
{
<<
\override Score.RestCollision #'minimum-distance = #0.75
{g8 a b c' d' e' f' g' a' b' c'' d'' e'' f'' g'' a''} \\
What did you expect the example to do?
Of course, it still shouldn't produce a SIGSEGV.
/Mats
Quoting Anders Kaseorg <[EMAIL PROTECTED]>:
\version "2.8.1"
\score {
c
\midi { \context { \name Voice } }
}
GNU LilyPond 2.8.1
Processing `crash.ly'
Parsing...
Interpreting music...
programming
This is a Gentoo box with Lilypond built from source. Since this bug
did not exist in late versions of Lilypond 2.7.x, this is a
regression. I have not yet gone backwards through the 2.7 branch to
see when the bug was introduced, but I am planning on doing so this week.
Hmm. On further inves
Thies Albrecht wrote:
This results in incorrect beamed stem-lengths as seen the attached
image. If you comment out the Y-extent override, the problem goes
away. If you comment out only the minimum-Y-extent, the output
changes slightly but the problem remains. This has been confirmed in
2.8.
Hi Daniel!
This results in incorrect beamed stem-lengths as seen the attached
image. If you comment out the Y-extent override, the problem goes
away. If you comment out only the minimum-Y-extent, the output changes
slightly but the problem remains. This has been confirmed in 2.8.1 and
2.9.
