Re: tie and slur problem

[Rutger Hofman]

The following code works for me. It depends on two voices having the 
same predicate \voiceTwo. Note that you will probably want to tune the 
shape of the voiceTwo slur, it is wider than in your original.

\new Score {
    \new Staff <<
        \new Voice \relative c' {
            \voiceOne
            g'2.( bes4 |
            a4)
        }
        \new Voice \relative c' {
            \voiceTwo
            c1~ |
            c4
        }
        \new Voice \relative c' {
            \voiceTwo
            e1( |
            f4)
        }
    >>
}

On 10/28/2014 02:33 PM, Urs Liska wrote:
> Am 28.10.2014 09:42, schrieb Dr. Bernhard Kleine:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > There should be a tie between the two c and a slur from e to f.  and a slur
> > from g  over b(bes) to a in the right hand. The upper g and b and a are in a 
> > separate voice and no problem.
> > But how to code the tie and the slur in voiceTwo? Between <c e> to < c f>
>
> You can force the slur to be printed upwards through either \slurUp (and
> \slurNeutral afterwards) or the direction operator:
>
> <c' e'>2 ^( ~ <c' f'> )
>
>
> This won't look very good, though, so you will have to tweak the slur
> later, presumably with \shape.
> But it will give you a semantically correct rendering, and I strongly
> suggest to let this untouched as long as possible (i.e. only start
> tweaking when you either can't read the output at all or when you have
> to produce better final output).
>
>
> HTH
> Urs
>
>
> > Schnipsel from Missa in C from Anton Bruckner
> >
> > Bernhard
> >
> >
> > /
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v2.0.22 (MingW32)
> > Comment: Using gpg4o v3.3.26.5094 -http://www.gpg4o.de/
> > Charset: utf-8
> >
> > iQIcBAEBAgAGBQJUT1cLAAoJENCoWyDsDBkPLHEQALYQc9MLBveNvVtyLSVLhnl/
> > jGy9jIhoJDHh3NAo8cGimSJbFVj3NFLZBlHRobwC9/J/cjSgtb13zu6mdYxhyNX1
> > ozJ7YJiX/qvTXaP0uEmK6gaERyWD4cbKKOB0Ot6ZscAf8EiBWwskJNnLzKDMMGpv
> > CpOy4si0jpS6tYrj+ZP83AwYcFgyq0cy/1TeZovNKN6c1U96L/TrFpWSt2vLvi5j
> > UR/8Wu7uft+4LpSjFKdnbuXDPAb45vZLQz7/fYefL7z4+GAsnc7KXM0CfSq7k7Yx
> > eHVeUfquAWcrYKwt3rl8+XOHpZ6BjyXoSNe2p4aUEw6eaRF4ogNKOT4u5X5kFaOI
> > wdYG0Y7Xm+gU+G3K64TYAEutTra8EqgjlGNYaFKTAfbIaVU5wtRovR+kH/G6fgLx
> > T33vr2gJVw7BCMFyr3X9/tMAgF7mL5cdpGBN9bBUWkR7BU9pDiLnaxM6eSTG5hX4
> > 0grUplUiNeO59aQTY6jPv0R2z3M/bC5gZaOWgkEvDeOQCWkm3uVgcO1aqTs8IaGy
> > ftOaGLZDjiTNx2r28ayOz4k3zHcXTOh+NMI9VxEZC2zAjkKp3SAX31T+WCUtwK6j
> > KHsUqWlv8AaaLMS/Fti+jFb9sbDYXwFM7fueFaBBlxMGv5ycf+VRVPAnopyZjKL/
> > mxKUz0OQy5zhMmKmZiCP
> > =KlK5
> > -----END PGP SIGNATURE-----
> >
> >
> > _______________________________________________
> > lilypond-user mailing list
> > address@hidden
> > https://lists.gnu.org/mailman/listinfo/lilypond-user