Comment #1 on issue 1098 by percival.music.ca: Unable to print long scores
http://code.google.com/p/lilypond/issues/detail?id=1098
You could try making distinct \bookpart{}s, or tweaking the memory settings
(see the
Usage manual). Also, do you have an example you could send (privately) to a
Comment #3 on issue 687 by dranidis: Enhancement: inequal MIDI quantization
of equal durations (swing, rubato)
http://code.google.com/p/lilypond/issues/detail?id=687
This is indeed an excellent idea. I am transcribing plenty of Jazz solos
(Charlie
Parker) with lilypond and exact midi
I don't speak English very well, in any case here:
http://lilypond.org/doc/v2.13/Documentation/notation/creating-midi-files#Creating-MIDI-files
[...]
When notation is needed too, a \layout block must *be* also *be* present.
[...]
it seems a typo.
Regards,
Carlo
2010/5/24 Stemby carlo.stember...@gmail.com:
I don't speak English very well, in any case here:
http://lilypond.org/doc/v2.13/Documentation/notation/creating-midi-files#Creating-MIDI-files
[...]
When notation is needed too, a \layout block must *be* also *be* present.
[...]
it seems a
Comment #7 on issue 1031 by pnorcks: constantly-changing
input/regression/rest-collision-beam-note.ly
http://code.google.com/p/lilypond/issues/detail?id=1031
Thank you for the helpful suggestions, Han-Wen.
Your intuition is correct: the problem is with the sorting vectors of
pointers to
Hello all,
In the third line of this snippet, all whitespace (word spacing) is removed --
is this expected behaviour?
\version 2.13.21
\markup { \line { in a line } }
\markup { \concat { pre in a line post } }
\markup { \concat { pre \line { in a line } post } }
Thanks,
Kieren.
Comment #8 on issue 1031 by pnorcks: constantly-changing
input/regression/rest-collision-beam-note.ly
http://code.google.com/p/lilypond/issues/detail?id=1031
Hmm... in this case, I guess we are not actually sorting by pointer
address, so the
problem might be elsewhere.
Comment #9 on issue 1031 by pnorcks: constantly-changing
input/regression/rest-collision-beam-note.ly
http://code.google.com/p/lilypond/issues/detail?id=1031
(Ignore my last comment.)
There are certain cases where pointer addresses are compared in
staff_priority_less.
If I comment out
Comment #10 on issue 1031 by hanwenn: constantly-changing
input/regression/rest-collision-beam-note.ly
http://code.google.com/p/lilypond/issues/detail?id=1031
We should try to remove all of these comparisons for the sake of
reproducibility. It
does not fix the actual problem though, since
