If you run that score with the current development version it will not crash but produce the attached result (for your reference).
But the log shows that you have errors in it (you can ignore the
warnings about strange time signatures but look for warning:
mid-measure time signature without \partial). Obviously LilyPond
2.18 didn't gracefully handle the faulty input.
Starting lilypond 2.19.50 [Untitled]...
Processing `/tmp/frescobaldi-GQAw3f/tmp5ji_kp/document.ly'
Parsing...
Interpreting music...
/tmp/frescobaldi-GQAw3f/tmp5ji_kp/document.ly:53:20: warning: strange time signature found: 2885/403
\time 2885/403
/tmp/frescobaldi-GQAw3f/tmp5ji_kp/document.ly:89:20: warning: strange time signature found: 7706/693
\time 7706/693
/tmp/frescobaldi-GQAw3f/tmp5ji_kp/document.ly:63:22: warning: strange time signature found: 4285/631
\time 4285/631
/tmp/frescobaldi-GQAw3f/tmp5ji_kp/document.ly:63:22: warning: mid-measure time signature without \partial
\time 4285/631
/tmp/frescobaldi-GQAw3f/tmp5ji_kp/document.ly:93:20: warning: strange time signature found: 4127/393
\time 4127/393
/tmp/frescobaldi-GQAw3f/tmp5ji_kp/document.ly:93:20: warning: mid-measure time signature without \partial
\time 4127/393
/tmp/frescobaldi-GQAw3f/tmp5ji_kp/document.ly:71:22: warning: strange time signature found: 1071/115
\time 1071/115
/tmp/frescobaldi-GQAw3f/tmp5ji_kp/document.ly:71:22: warning: mid-measure time signature without \partial
\time 1071/115
Preprocessing graphical objects...
Finding the ideal number of pages...
Fitting music on 1 page...
Drawing systems...
Layout output to `/tmp/lilypond-QRomN1'...
Converting to `document.pdf'...
Deleting `/tmp/lilypond-QRomN1'...
Success: compilation successfully completed
Completed successfully in 1.1".
Am 04.11.2016 um 04:27 schrieb mclaren:
Now we get to the interesting Lilypond scores, the ones that cause Lilypond
to crash or produce error messages.
This simple score makes Lilypond die and stop engraving after a couple of
measures with the error message "Programming error: bounds of this piece
aren't breakable." Lilypond gives lots of "continuing -- crossing fingers"
and ultimately fails to engrave the score. Yet Lilypond claims "Completed
successfully"!
This simple score is broken up into measures of tuplets each of which has a
large time signature. Because these time signatures would make Lilypond
crash (LILYPOND HAS STOPPED WORKING is the error message), I have had to
approximate the time signatures with smaller rational fraction
approximations in each case. This is a workaround, but it seems to work in
other Lilypond scores without trouble.
For example, the time signature 21632/3135 had to be approximated by the
smaller time signature 2285/403. The smaller time signature is accurate to
within a couple of parts per million, though, so it works out okay.
That's not the issue. The issue is that Lilypond just can't seem to handle a
score in which every note is a broken tuplet, and in which large time
signatures are used.
Notice that by the time we reach the dotted quarter note tuplet 14 in the
time of 11 B in the top measure, Lilypond has given up the ghost. Lilypond
doesn't even print the tuplet. It has freaked out. Lilypond is no longer
working properly.
Clearly, this score makes Lilypond blow its stack. What I'd like to know is:
is there any workaround? Any suggestions for getting Lilypond to actually
engrave what I've entered?
Lilhypond gives the message "Completed successfully" but clearly Lilypond
isn't completing anything successfully. It gives up and stops engraving the
score after the first two and a half measures.
Here's the Lilypond score:
\version "2.18.2"
\header {
tagline = "" % removed
}
#(set-default-paper-size "a4" 'landscape)
\layout {
% \paper {}
indent=0
% Create time signature context
% Source: http://lsr.di.unimi.it/LSR/Snippet?id=272
% (modified)
\context {
\type Engraver_group
% Add elements that _can_ be printed
\consists "Timing_translator"
\consists "Time_signature_engraver"
\consists "Axis_group_engraver"
\name "TimeLine"
\alias "Staff"
% Align time signatures on barlines
\override TimeSignature.X-offset =
#ly:self-alignment-interface::x-aligned-on-self
\override TimeSignature.self-alignment-X = #CENTER
}
\context {
\Score
\accepts "TimeLine"
\override TupletNumber.text = #tuplet-number::calc-fraction-text
}
\context {
\Staff
\consists "Timing_translator"
\consists "Default_bar_line_engraver"
}
}
{
<<
\new Staff { \clef "treble"
\relative c''
{
\override Staff.TimeSignature #'stencil = ##f
%\time 86772/12121
\time 2885/403
{ \tuplet 17/15 {c4}
\tweak direction #up
\tuplet 23/19 {d8[ f]} \tuplet 31/29{e b4 c8}}
%\time 21632/3135
\bar "|"
{
\time 4285/631
\tuplet 11/9{d4.}
\tweak direction #up
\tuplet 15/13{f8} \tuplet 19/17{e2}}
\bar "|"
{
\time 1071/115
\tuplet 14/11{b4.} \tuplet 23/17{c8} \tuplet 1/15{d8[ f e b]} \tuplet
17/13{c2}
\bar "|"
}
}
}
\new Staff { \clef "treble"
\relative c''
{
\override Staff.TimeSignature #'stencil = ##f
\time 7706/693
{ \tuplet 17/15{c8[ d f e]} \tuplet 11/7{b2.} \tweak direction #down \tuplet
5/3{r4} \tuplet 7/6 {c16[ d16]} \tuplet 9/8 {f4} }
\bar "|"
\time 4127/393
{\tuplet 13/10{r4.} \tuplet 3/4{e8} \tuplet 7/5{b[ c d]} \tuplet 8/5{d8 f4
e8} \tuplet 23/17{b4.}}
\bar "|"
e8 b] c[ d16 f e8 b c16 d f8 e b c] d[ f e b16 c d8 f e b16 c d8]
}
}
}
--
View this message in context: http://lilypond.1069038.n5.nabble.com/Lilypon-error-message-Programming-error-bounds-of-the-piece-aren-t-breakable-tp196123.html
Sent from the User mailing list archive at Nabble.com.
_______________________________________________
lilypond-user mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/lilypond-user
document.png