lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Strange warnings


From: David Sumbler
Subject: Strange warnings
Date: Fri, 25 May 2018 16:42:18 +0100

I have hesitated before sending this message: I know it will annoy
people because it is so vague and I cannot replicate the problem in a
brief piece of code.

But I just wonder if somebody else has come across a similar problem
and can suggest what might be causing it, or whether it relates to some
known bug.

The problem is this: in a 44-bar piece for strings and a singer, every
time I compile the score I get 2 warnings, each of which reads:

warning: overlap(s) found on line 1; redistribute manually
programming error: Improbable offset for stencil: inf staff space
Setting to zero.
continuing, cross fingers
programming error: Improbable offset for stencil: inf staff space
Setting to zero.
continuing, cross fingers

There are always 2 identical programming errors as shown above for each
warning.  Occasionally line 2 gets a mention as well as line 1, but
never any other.

The actual output file is fine: it has no obvious overlaps or other
flaws of that sort, even though it still needs a bit of tidying up.

I have spent hours trying to narrow the problem down to particular
bar(s) or instruments, but with little success.  It doesn't seem to be
related to line 1 of the music, because if I truncate all of the input
to the first few bars the warnings disappear.

The only thing I have managed to establish is that it seems to be
related to the 1st violins and cellos, which have staves arranged thus:
          <<
            \new Staff
            \ScoreThreeCelloA
            \new Staff \with { \RemoveAllEmptyStaves }
            \ScoreThreeCelloB
          >>

If I comment out one or both of the cello staves, or the 1st fiddle
staves, one or both warnings disappear.  However the 2nd violins and
the violas have staves arranged similarly, yet don't seem to be causing
any problems.

Has anyone any suggestions as to what might be going on here?

David






reply via email to

[Prev in Thread] Current Thread [Next in Thread]