lilypond-user
[Top][All Lists]
Advanced

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

Re: small notes etc.


From: Robin Bannister
Subject: Re: small notes etc.
Date: Fri, 25 Jul 2008 22:07:07 +0000 (UTC)
User-agent: Loom/3.14 (http://gmane.org/)

David Biddiscombe wrote on the bug list:

> Below is an input file representing small parts of a file for a four-verse 
song. 
> The rhythm of the fourth verse, which differs from that of the other verses, 
is 
> shown in the .pdf file by the small notes above the top staff, except that 
the 
> two small quavers must be (a) beamed, (b) with a slur/tie **above** the beam, 
> and (c) in line with the other three small notes. (The markups are attached 
to 
> the **alto** input to avoid complications over stem directions.) I've tried a 
> number of markup variations, but can't get the necessary output. 
> 
> Also, for some reason, the first alto crotchet f is not offset from the 
soprano 
> g, although in every similar case in the the complete song (as for example in 
> the last chord in this extract) the output is correct. 
> 
> Lastly, is it possible to make bar lines (of all types) thinner? Line 10 of 
the 
> file below is an attempt (but doesn't work). 


Answering in reverse order:
____________________

Barlines belong under Staff and have two specially named thicknesses.
Try
     \override Staff.BarLine #'hair-thickness = #1
____________________

These offsets are normally set up by \voiceOne, \voiceTwo etc. 
which you have done explicitly (inside ChoirStaff).
 
But the  <<  {...}  //  {...}  >> construction implicitly
sets up its own \voiceOne, \voiceTwo etc. 
You can see the effect of this by swapping the order of these {...} 

____________________

I don't know enough about it, but my feeling is that markup is unsuitable for 
this. 
Search LSR for "rhythmMark" to see how complicated it can get. 

You are using separate markups to get the horizontal alignment. 
But to get a single vertical alignment you should have just one markup. 

I would suggest setting up an auxiliary staff having everything but the notes 
blanked out. 
Search LSR for "Engravers one-by-one".
Also, with this approach no local <<  {...}  //  {...}  >> construction is 
needed.

____________________

Cheers,
Robin






reply via email to

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