@node Simultaneous notes
@section Simultaneous notes
+@lilypondfile[quote,ragged-right,line-width=16\cm,staffsize=16]
+{simultaneous-headword.ly}
+
Polyphony in music refers to having more than one voice occurring
in a piece of music. Polyphony in LilyPond refers to having more
than one voice on the same staff.
@subsection Single voice
@menu
-* Chords::
+* Chorded notes::
* Clusters::
@end menu
-@node Chords
-@unnumberedsubsubsec Chords
+@node Chorded notes
+@subsubsection Chorded notes
@cindex Chords
A chord is formed by a enclosing a set of pitches between @code{<}
and @code{>}. A chord may be followed by a duration, and a set of
-articulations, just like simple notes
+articulations, just like simple notes:
@lilypond[verbatim,ragged-right,fragment,quote,relative=1]
<c e g>4 <c>8
For more information about chords, see @ref{Introducing chord
names}.
+@seealso
+
+Music Glossary: @rglos{chord}.
+
+Notation Reference: @ref{Introducing chord names}.
+
+Snippets: @lsrdir{Simultaneous,Simultaneous-notes}.
+
+@refbugs
+
+Music expressions like @code{<< @{ g8 e8 @} a4 >>} are not printed
+accurately. Use @code{<g a>8 <e a>8} instead.
+
+
@node Clusters
-@unnumberedsubsubsec Clusters
+@subsubsection Clusters
@cindex cluster
@seealso
-Program reference: @internalsref{ClusterSpanner},
+Snippets: @lsrdir{Simultaneous,Simultaneous-notes}.
+
+Internals Reference: @internalsref{ClusterSpanner},
@internalsref{ClusterSpannerBeacon},
@internalsref{Cluster_spanner_engraver}.
-Examples: @lsr{contemporary,cluster@/.ly}.
-
-@refbugs
-
-Music expressions like @code{<< @{ g8 e8 @} a4 >>} are not printed
-accurately. Use @code{<g a>8 <e a>8} instead.
+Examples: @c @lsr{contemporary,cluster@/.ly}.
@subsection Multiple voices
@menu
-* TODO new sec voices::
-* Collision Resolution::
+* Collision resolution::
* Automatic part combining::
* Writing music in parallel::
@end menu
-@node TODO new sec voices
-@unnumberedsubsubsec TODO new sec voices
+@node Collision resolution
+@subsubsection Collision resolution
-In some instances of complex polyphonic music, you may need
-additional voices to avoid collisions between notes. Additional
-voices are added by defining an identifier, as shown below:
-
-@lilypond[quote,verbatim,ragged-right,relative=2]
-voiceFive = #(context-spec-music (make-voice-props-set 4) 'Voice)
-
-\relative c''' <<
- { \voiceOne g4 ~ \stemDown g32[ f( es d c b a b64 )g] } \\
- { \voiceThree b4} \\
- { \voiceFive d,} \\
- { \voiceTwo g,}
->>
-@end lilypond
-
-
-@node Collision Resolution
-@unnumberedsubsubsec Collision Resolution
+@cindex merging notes
+@cindex note collisions
Normally, note heads with a different number of dots are not
merged, but when the object property
@noindent
@code{merge-differently-headed} and
@code{merge-differently-dotted} only apply to opposing stem
-directions (ie. Voice 1 & 2).
+directions (i.e. Voice 1 & 2).
LilyPond also vertically shifts rests that are opposite of a stem,
for example
\new Voice << c''4 \\ r4 >>
@end lilypond
+@cindex shift note
+
If three or more notes line up in the same column,
@code{merge-differently-headed} cannot successfully complete the
merge of the two notes that should be merged. To allow the merge
>>
@end lilypond
+@cindex multiple voices
+@cindex polyphonic music
+@cindex shifting voices
+
+In some instances of complex polyphonic music, you may need
+additional voices to avoid collisions between notes. Additional
+voices are added by defining an variable, as shown below:
+
+@lilypond[quote,verbatim,ragged-right,relative=2]
+voiceFive = #(context-spec-music (make-voice-props-set 4) 'Voice)
+
+\relative c''' <<
+ { \voiceOne g4 ~ \stemDown g32[ f( es d c b a b64 )g] } \\
+ { \voiceThree b4} \\
+ { \voiceFive d,} \\
+ { \voiceTwo g,}
+>>
+@end lilypond
+
+
@refcommands
@funindex \voiceFour
@code{\voiceFour}.
+@funindex \voiceNeutralStyle
+@funindex \voiceOneStyle
+@funindex \voiceTwoStyle
+@funindex \voiceThreeStyle
+@funindex \voiceFourStyle
+@example
+\voiceNeutralStyle
+\voiceOneStyle
+\voiceTwoStyle
+\voiceThreeStyle
+\voiceFourStyle
+@end example
+
@funindex \shiftOn
@code{\shiftOn},
@funindex \shiftOnn
@seealso
-Program reference: the objects responsible for resolving
+Snippets: @lsrdir{Simultaneous,Simultaneous-notes}.
+
+Internals Reference: the objects responsible for resolving
collisions are @internalsref{NoteCollision} and
@internalsref{RestCollision}.
@node Automatic part combining
-@unnumberedsubsubsec Automatic part combining
+@subsubsection Automatic part combining
@cindex automatic part combining
@cindex part combiner
+@cindex combining parts
Automatic part combining is used to merge two parts of music onto
a staff. It is aimed at typesetting orchestral scores. When the
The following example demonstrates the basic functionality of the
part combiner: putting parts on one staff, and setting stem
-directions and polyphony
+directions and polyphony.
@lilypond[quote,verbatim,ragged-right,fragment]
\new Staff \partcombine
down stems and @q{Solo II}.
If you just want the merging parts, and not the textual markings,
-you may set the property @code{printPartCombineTexts} to false
+you may set the property @code{printPartCombineTexts} to false.
@lilypond[quote,verbatim,ragged-right,fragment,relative=2]
\new Staff <<
@seealso
-Program reference: @internalsref{PartCombineMusic}.
+Music Glossary: @rglos{a due}.
+
+Snippets: @lsrdir{Simultaneous,Simultaneous-notes}.
+
+Internals Reference: @internalsref{PartCombineMusic}, @internalsref{Voice}.
@refbugs
-When @code{printPartCombineTexts} is set, when the two voices play
+When @code{printPartCombineTexts} is set, if the two voices play
the same notes on and off, the part combiner may typeset @code{a2}
more than once in a measure.
@node Writing music in parallel
-@unnumberedsubsubsec Writing music in parallel
+@subsubsection Writing music in parallel
@cindex Writing music in parallel
@cindex Interleaved music
-Music for multiple parts can be interleaved
+Music for multiple parts can be interleaved:
@lilypond[quote,fragment,verbatim]
\parallelMusic #'(voiceA voiceB) {
>>
@end lilypond
-This works quite well for piano music
+This works quite well for piano music.
@c It would be nice if the first bar fit onto one 66-char line.
@c Maybe simplify the example? -gp
}
@end lilypond
+@seealso
+Snippets: @lsrdir{Simultaneous,Simultaneous-notes}
projects / lilypond.git / blobdiff