[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: {SPAM 04.0} Re: Strange warnings
From: |
David Sumbler |
Subject: |
Re: {SPAM 04.0} Re: Strange warnings |
Date: |
Fri, 25 May 2018 22:19:42 +0100 |
On Fri, 2018-05-25 at 15:36 -0400, Ben wrote:
> On 5/25/2018 2:58 PM, David Sumbler wrote:
> > I did eventually solve the problem, thanks to an off-list nudge
> > from
> > Joe Davenport. I had some text spanners in a \global variable,
> > which
> > was not a good idea when some of the staves are going to be
> > suppressed!
> >
> > As so often, it is obvious once one has found the answer.
> >
> > David
> >
>
> David,
>
> Just curious but what text spanners were giving you a problem? I use
> the global block for a lot of common-score things but have never run
> into that error yet.
>
> Thanks!
I am using Paul Morris's text-spanner-inner-text-lyric-mode.ly , which
is excellent for markings such as ritardando----al----Lento. I have
used this previously without problems, but that was before I started
structuring things with a global variable containing time signatures,
tempo markings etc.
On this occasion I put the required commands into the global variable,
forgetting that although the output is formatted in MetronomeMark
style, it is actually a TextScript. I realized this when I saw the
output, because of course it appeared on every stave. I made a mental
note that this was something to correct when I had finished the main
input.
It didn't cause any problems at first, but when I had edited things so
that additional staves only appear when necessary, I started to get
these errors. Hardly surprising when you consider that Lilypond was
being asked to put spanners over suppressed staves. When I removed the
markings from the global variable and put them just in the staves they
should appear on, the problems disappeared.
David