Thank-you to Leo Correia de Verdier for excellent instructions. I'm pleased
with the results. I see later in the documentation there is a snippet on
how to merge voices, so that's next on my list.

[image: image.png]

 <<
     {s8 s16^"ossia" s16 a16(g f e)| g16(f e d) s4|}
  \\
     {f16(e f g) a(f c a)| g16(a bf g) c(bf a g)|}
  >>

On Tue, Aug 30, 2022 at 12:37 PM Leo Correia de Verdier <
[email protected]> wrote:

> The easiest way would be to use \voiceOne and \voiceTwo instead of \stemUp
> and \stemDown (recommended anyway in most cases). Otherwise _( and ^( works
> too.
>
> HTH
> /Leo
>
> 30 aug. 2022 kl. 19:30 skrev Greg Lindstrom <[email protected]>:
>
> 
> I am finishing up engraving my first full score. It's a piece for brass
> band where we could not find a score anywhere and the one we've ordered has
> been backordered for 6 months! I took it upon myself to pull all the parts
> and engrave away. Eventually, I will hook up a midi keyboard to enter stuff
> like this, but I'm as quick, if not quicker, typing it in and
> controlling just about everything the first time through.
>
> Lilypond is an impressive system and I use it over the 2 "big" commercial
> engraving packages because I think the final product just looks better.
>
> But, to my question...
>
> I have a very short Ossia that I would like to add to a chart I'm
> engraving. I'd rather not break it out onto its own staff (just to save
> space in the score) so I'm adding it as a CueVoice. The problem is the slur
> marks on the main line are above and the slurs on the ossia are below (see
> snippet). Is there a way to control where the slur marks appear, in the
> same spirit as stems up and down? Is it preferred to break the ossia out in
> its own staff:?
>
> Thanks!
> --greg
>
> [image: image.png]
>
> And the code to generate it
>
>   <<{f16(e f g\!) a(f c a)|
>      \stemDown{g16(a bf g)\> c(bf a g\!}|
>     }
>     {
>       \new CueVoice{
>         \stemUp s16 s8^\markup\small{ossia} s16 a'16(g f e)|
>                 g16(f e d) s4|
>       }
>     }
>   >>
>
>

Reply via email to