[Top][All Lists]

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

Re: lilypond bug in version 2.6.3

From: Dylan Nicholson
Subject: Re: lilypond bug in version 2.6.3
Date: Tue, 25 Oct 2005 16:34:06 +1000

> tempomarks = {\mark "Allegro" \skip 1*24
>  \mark "Andante" \skip 1*32
>  ...
> }> Then you can do
> \score{
> \new Staff << \tempomarks \flute >>
> \new Staff \oboe ...
> }
> for the full score and
> \score{
> \new Staff << \tempmarks \oboe >>
> }
> for the instrumental parts.

Hmm...fine, if you only have one or two tempo markings in your whole work!

The only way I can think that this could be made to work reasonably is to 
maintain a separate staff that just has tempo markings, and then for the full 
score, merge it with the flute part and violin I part (the usual place above 
which Tempo markings are shown), but then merge it with all the individual 
parts separately.
Still a headache.

If there was a way of specifying *which* staves \mark events would appear above 
(and ideally below also) I would be able to use realistically use lilypond for 
doing large orchestral scores.  And note, you need a reasonable amount of 
control here - there might be some systems that have only, say, a flute staff 
and a violin I staff (all other staves are tacet and hidden), but in this case, 
you don't really need the tempo marking to appear above both.  Typically you 
would only show it if at least 3 or so staves appeared between the top visible 
staff and the violin I staff.  And often in big choral works the tempo markings 
will be shown again above the choir staff (but only when the choir staff is 
present obviously).  Nor is it uncommon to have tempo markings/rehearsal 
numbers etc. etc. appear below the bottom of the score - even if there are only 
two staves in a system.

reply via email to

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