I'm a bit confused about the use of minimumFret and restrainOpenString.
Maybe adding a warning in the documentation could be a good idea.
The best way I can explain it is pasting this input code (commented).
Problem is in the last measure.
\version 2.17.9
music = \relative c' {
\set
Thomas Morley thomasmorle...@googlemail.com wrote in message
news:CABsfGyWjDQvLcv731XZw+wX_JWb+x3kZU5DTe=obwjs8j-o...@mail.gmail.com...
Hi,
a simple
\transpose c c'
(with changing stem-direction)
can break \crossStaff without printing a warning or error.
%%% example
\version 2.16.1
% The end of the ligature bracket is not printed
\version 2.17.8
{ \[ c'1 \break d'1 \] }
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
% The flat symbol is unreasonably far above the note
\version 2.17.8
{ \set suggestAccidentals = ##t \[ a'2 bes' \] }
(As a workaround, is there any way to make the brackets and
accidentals not try to avoid each other at all? This seems to be the
case with brackets and fermatas and it looks
Federico Bruni fedelogy at gmail.com writes:
I'm a bit confused about the use of minimumFret and restrainOpenString.
Maybe adding a warning in the documentation could be a good idea.
It seems that restrainOpenString = #t causes LilyPond to check if you can
reach a finger to fret zero, within
Hey all,
A colleague of mine got the following error message while running midi2ly on
his MacBook :
macbook:~ vanhovef$ /Applications/LilyPond.app/Contents/Resources/bin/midi2ly
wil
Traceback (most recent call last):
File /Applications/LilyPond.app/Contents/Resources/bin/midi2ly, line 54, in
issue 2990 : lilypond crashes with a stack overflow on Windows (1)
also tested in Linux, also crash
There is infinite loop in calc_skylines function, I don't know yet, what
may cause it.
This is quotes from discussion with Mike Solomon:
I get this backtrace running gdb lilypond with sample
