On Sun, Nov 17, 2013 at 12:15:45AM +0100, David Kastrup wrote:
>
> What is this good for? I'm debugging on this
> <URL:http://code.google.com/p/lilypond/issues/detail?id=3663> and though
> I've gotten the crash under control, my results are not identical to the
> 2.16 results. I have a hard time deciding whether I should even care.
>
> Can you spell out an actual application for this that did something
> useful in 2.16? What would the output look like for such a reasonable
> application?
By itself, I don't know what it's good for, nor do I have an
example of what the minimal example's output "should" be. It's
an element that is intended to be used simultaneously with other
contexts (melodic, chordal, whatever).
I was working on a lead sheet, and looking for a way to separate
the volta structure, \time changes, rehearsal marks, etc., from
the actual notes, because the notes often repeated, but did so in
unusual parts of the arrangement. So I wanted to separate the
form from the melody.
At some point while I was working, the input file got into a
state which caused Lilypond to crash. I arrived at the minimal
example by process of elimination after I discovered that
Lilypond still crashed when the chordal and melodic staves were
commented out or removed, leaving only the \form. I then
winnowed down the \form variable's music to the smallest example
that would trigger the crash.
A larger example created just today works fine if I define a
simultaneous empty (spacers) melodic staff of a sufficient
length.
If the crash has been resolved, I would agree that the expected
output from the minimal example is inconsequential, and it's
probably difficult to say what output is definitively correct or
incorrect, since there are no bar lines for the volta brackets to
align to.
I'm attaching a less-minimal example. Commenting out the sample
melody and using spacer rests, it appears that the crash happens
when the simultaneous music is not long enough to complete the
first ending. Hence s1*15 (and less) crashes, s1*16 (and more)
does not. Perhaps this example will suggest a more specific
"correct" output, but my feeling is that if the crash is fixed,
the issue can probably be closed.
Thank you for taking a look at this.
Regards,
Jim
\version "2.17.95"
form = \new Staff \with {
\remove "Time_signature_engraver"
\remove "Clef_engraver"
\remove "Bar_engraver"
\remove "Staff_symbol_engraver"
\remove "Axis_group_engraver"
} {
\mark \markup \box \bold "Intro"
s1 * 8
\mark \default % A section
\repeat volta 2 {
s1 * 6
} \alternative {
{ % first ending
s1 * 2
}
{ % second ending
s1 * 2
}
} % repeat
\mark \default
s1 * 8 % B section
\mark \default
s1 * 8 % C section
\bar "|."
} % form
melody = \relative c'' {
c,4 c c c
d4 d d d
e4 e e e
f4 f f f
g4 g g g
a4 a a a
b4 b b b
c4 c c c
c,4 c c c
d4 d d d
e4 e e e
f4 f f f
g4 g g g
a4 a a a
% first ending:
b4 b b b
c4 c c c
% second ending:
c,4 c c c
d4 d d d
% B section:
e4 e e e
f4 f f f
g4 g g g
a4 a a a
b4 b b b
c4 c c c
c,4 c c c
d4 d d d
% C section:
e4 e e e
f4 f f f
g4 g g g
a4 a a a
b4 b b b
c4 c c c
c,4 c c c
d4 d d d
} % melody
\score {
<<
\set Score.markFormatter = #format-mark-box-letters
\form
% \melody
% s1*15 % crash
s1*16 % no crash
>>
} % score
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
