Re: Multiple slurs between chords

2016-07-08 Thread Stephen MacNeil
Ok thanks for the clarification

Stephen
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: Multiple slurs between chords

2016-07-07 Thread David Kastrup
Stephen MacNeil  writes:

> Hi David
>
> I notice both
>
> ^(_(d)
>
>
> and
>
> ^(_(d))
>
>
> work. The last with ))
>
>
> is one way "more" correct?

Slurs don't nest.  The current implementation does not complain about
spurious slur starts/ends.  It's only when the directions on slur starts
are straightforwardly incompatible that it sets double slurs (which
allows you to tweak the slurs from double slurs independently).

So pick the version you like better.  2.14 or so is a bit unpredictable
in its complaints (and will typeset only one slur anyway).

There is ongoing work for allowing multiple parallel spanners in other
ways.  I don't know whether this will change this behavior.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: Multiple slurs between chords

2016-07-07 Thread Stephen MacNeil
Hi David

I notice both

^(_(d)


and

^(_(d))


work. The last with ))


is one way "more" correct?


Stephen
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: Multiple slurs between chords

2016-07-07 Thread David Kastrup
Stephen MacNeil  writes:

> \set doubleSlurs = ##t
>
>  (d)

Or just ^(_( d) since two slurs with explicit direction will both
be kept around.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: Multiple slurs between chords

2016-07-07 Thread Joel C. Salomon
An hour ago, I wrote:
> (In the [attached] larger file, I was able to put an explicit \oneVoice
> overriding \voiceTwo and imitate the printed version, but this only
> worked for the upper staff, and not in my excerpt.)
> 
> Can anyone suggest the correct way forward?

I figured something out; whether it’s the Right Thing to Do™ or an awful
kluge I leave for others to judge:

I split the chord between voices, but included an explicit \voiceOne or
\voiceTwo override to get the stem directions the same.

\version "2.19"
\language "english"

upperOne = \relative c' {
\voiceOne
e4.(d4) %…
\oneVoice   r8  |

\voiceOne
% file continues
}

upperTwo = \relative c' {
\voiceOne
cs4._(   d4) s8  |

\voiceTwo
% file continues
}

lowerOne = \relative c' {
\voiceTwo
g4.^(   fs4)%…
\oneVoice   r8   |

\voiceOne
% file continues
}

lowerTwo = \relative c' {
\voiceTwo
a,4.(   d4) s8  |

\voiceTwo
% file continues
}

\score {
\new PianoStaff <<
\new Staff = "upper" <<
\clef treble\key d \major   \time 6/8
\upperOne
\new Voice \upperTwo
>>
\new Staff = "lower" <<
\clef bass  \key d \major   \time 6/8
\lowerOne
\new Voice \lowerTwo
>>
>>
\layout {}
\midi {}
}

—Joel C. Salomon

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user