Simon Bailey-5 wrote
> have you seen:
> http://lilypond.org/doc/v2.18/Documentation/notation/skipping-corrected-music
> ?
Excellent! Highly useful - although it is a bit annoying to see a large
bunch of warnings when the showLastLength is set.
--
View this message in context:
http://lilypond.
Kieren MacMillan wrote
> Having just engraved 25 minutes of large forces music for voices and
> instruments (57 staves, for ~330 performers!), I **HIGHLY** recommend you
> avoid doing things like that in future scores.
Thanks for the advice. I'm only on my 4th "real" score in Lilypond so I'll
take
Kieren MacMillan wrote
>> In regards to tempo markings, it is a different matter, since any change
>> in
>> tempo needs to apply to each and every voice in the system. It makes
>> perfect
>> sense that the \tempo marking always goes to the System - I just don't
>> understand why it is much more dif
Trevor Daniels wrote
> ?
> \tempo "ritardando"
Not a bad idea - but I would then have to abandon the idea of the normal
"rit. _ _ _ _ _ _ _ _ _ al" construct where the text spans the entire
duration of the ritardando.
Think I'll try a feature request for a SystemSpanner
- and perhaps a \startTe
jensgc wrote
> The reason I don't like the idea of a global "structure" definition is
> that I have the individual parts (e.g. the quartet and the choir parts)
> defined in seperate files to be able to test and work with them
> independently. Having the \time and \key de
Simon Bailey-5 wrote
>> If I add the music from the topmost staff to a separate dynamics context
>> (placed above that staff), will dynamics context then be printed twice?
>
> yes, that's correct. the music is suppressed, but the dynamics will be
> shown. this is why i suggested using a global str
Simon Bailey-5 wrote
> this is untested, but what might work would be to set up your score
> with a Dynamics context at the top. Don't be mislead by it being
> called Dynamics, you can put ANYTHING in there, doesn't have to be
> Dynamics (I use one for putting pedal markings in piano staves for
> i
Eluze wrote
> you can define the spanner in its own (dynamic) context and move it
> wherever you want:
thanks for the answer. I am aware of the possibility to have the dynamics in
a separate voice - and it might be the solution here. I am however not fond
of having to enter dynamics in a voice "wi
