Re: Tempo marking within a string and object moving

[Mats Bengtsson]

Always use R1 instead of r1 for full measure rests.

The solution you have done is more or less what I would use as well, but
I would use
\mark \markup{ ... }
before the first note instead. Then it will be printed on top of the 
score line and
aligned before the first note, as you wish.

If you wish the corresponding tempo in the MIDI file, you can either use a
\tempo command in the  \midi{...} block (since it's the at the top of 
the score)
or use a \tempo command within the Staff context and make it invisible.

  /Mats

Neil Killeen wrote:

> Hi again
>
> I have the notes under control, so now I want to do the hard part,  
> annotate my music :-)
>
> The very first thing I want to do is proving difficult !
>
> I have a layout like this, with 4 staves.  The music begins with rests 
> for all parts but the cello.
>
>                                     |
>        With determination (o = 100)
> Sop        r1
> Mez        r1
> Alt         r1
> Cello      notes
>
>
> I want to write the expression and tempo marking as indicated above.
> The words need to start before the rest symbols are printed (sop/mez/alt)
>
> I wanted to use the \tempo directive, as I will use that elsewhere in
> the piece, but I failed to get that to embed in the markup.
>
> My solution seems overly  complicated for such a basic (and common) 
> thing. In the
> soprano line I put :
>
>  r1^\markup { \hspace #-3.0 With Determination  ( \raise # 0.5 { \note 
> #"2" #1.0 }=100) }
>
>
> Comments:
>
> 1) the \hspace is to push the text to the left of the first rest
> 2) The \raise is to get the note-head to align so that the bottom of 
> the note
>    aligns with the bottom of the "100" (in the same way as in the 
> \tempo command)
> 3) The note head size is larger than that which comes out with the 
> \tempo command
>
> Is there an easier way to do this ? Can i embed \tempo in the \markup 
> somehow
> so that at least I get consistent note sizes ?
>
>
> -------------------------------------------------------------------------------------------------------------------- 
>
>
>
> I also wanted to explore how to move text around and eventually found the
> padding and extra-offset properties.
>
> The manual gives examples (Sec 4.3)
>
>       \once \override TextScript #'padding = #1.5
>
> and
>
>       \once \override TextScript #'extra-offset = #'( 1.0 . -1.0 )
>
>
> The # syntax appears to be when a command or property takes an argument
> (of any type; string, integer, float etc).
>
> Could someone please explain the syntax involving the ' (comma)  marks 
> ?  Padding has
> one comma  and extra-offset has two.    There are no comma marks in 
> the markup
> commands, why are they in these ones ?  I also find the period in the  
> middle of the ( 1.0 . -1.0) strange and I didn't even see  it at first 
> (and wondered why it wasn't working).
>
> Anyway, using the extra-offset ( I couldn't get padding to work) I 
> rewrote my expression
> above (and added a vertical shift) as :
>
>       \once \override TextScript #'extra-offset = #'( -3.0 . 2.0 )
>       r1^\markup { With Passion ( \raise # 0.5 { \note #"4" #1.0 }=100) }
>
> which is still quite complicated.  Is there  a simpler way to move 
> things about or is this the one true way ?
>
>
>
> cheers
> Neil
>
>
>
>
> _______________________________________________
> lilypond-user mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/lilypond-user


--
=============================================
        Mats Bengtsson
        Signal Processing
        Signals, Sensors and Systems
        Royal Institute of Technology
        SE-100 44  STOCKHOLM
        Sweden
        Phone: (+46) 8 790 8463                         
       Fax:   (+46) 8 790 7260
        Email: address@hidden
        WWW: http://www.s3.kth.se/~mabe
=============================================