X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=Documentation%2Fnotation%2Fsimultaneous.itely;h=4ded8656e032fd3c70dbebe2e335158d66857305;hb=17270930d34bbbc9a837585fcc84d6eabda67010;hp=00740cdfcef9e5a83f42c0ec261c384877f8f139;hpb=689382813a007255352a32847ab884ed67192fcc;p=lilypond.git
diff --git a/Documentation/notation/simultaneous.itely b/Documentation/notation/simultaneous.itely
index 00740cdfce..4ded8656e0 100644
--- a/Documentation/notation/simultaneous.itely
+++ b/Documentation/notation/simultaneous.itely
@@ -78,6 +78,22 @@ they will not print.
1 \f ( ) \< \!
@end lilypond
+@cindex chords, empty
+@cindex placeholder events
+
+A chord acts merely as a container for its notes, its articulations and
+other attached elements. Consequently, a chord without notes inside
+does not actually have a duration. Any attached articulations will
+happen at the same musical time as the next following note or chord and
+be combined with them (for more complex possibilities of combining such
+elements, see @ref{Simultaneous expressions}):
+
+@lilypond[verbatim,quote,relative=2]
+\grace { g8[( a b] }
+<> ) \p \< -. -\markup \italic "sempre staccato"
+\repeat unfold 4 { c4 e } c1\f
+@end lilypond
+
@cindex relative pitch, chords
@cindex chords, relative pitch
@@ -130,6 +146,7 @@ enharmonic transcription of one or more pitches,
@end itemize
+
@node Chord repetition
@unnumberedsubsubsec Chord repetition
@@ -243,8 +260,17 @@ a << { a4 b g } { d4 g c, } >>
@end lilypond
This can be useful if the simultaneous sections have identical
-rhythms, but attempts to attach notes with different durations
-to the same stem will cause errors.
+rhythms, but attempts to attach notes with different durations to
+the same stem will cause errors. Notes, articulations, and property
+changes in a @emph{single} @samp{Voice} are collected and engraved in
+musical order:
+
+@lilypond[quote,verbatim,relative=2]
+4-. <>-. << c a >> << { c-. } { a s-. } >>
+@end lilypond
+
+Multiple stems or beams or different note durations or properties at
+the same musical time require the use of multiple voices.
The following example shows how simultaneous expressions can
generate multiple staves implicitly:
@@ -254,7 +280,8 @@ generate multiple staves implicitly:
<< { a4 b g2 } { d4 g2 c,4 } >>
@end lilypond
-Here different rhythms cause no problems.
+Here different rhythms cause no problems because they are
+interpreted in different voices.
@cindex collisions, clashing note columns
@cindex collisions, ignoring
@@ -301,7 +328,6 @@ Ordinary notes and clusters can be put together in the same staff,
even simultaneously. In such a case no attempt is made to
automatically avoid collisions between ordinary notes and clusters.
-
@seealso
Music Glossary:
@rglos{cluster}.
@@ -314,9 +340,7 @@ Internals Reference:
@rinternals{ClusterSpannerBeacon},
@rinternals{Cluster_spanner_engraver}.
-
@knownissues
-
Clusters look good only if they span at least two chords; otherwise
they appear too narrow.
@@ -327,6 +351,7 @@ separating rest between them.
Clusters do not produce MIDI output.
+
@node Multiple voices
@subsection Multiple voices
@@ -538,9 +563,6 @@ music do not have the same rhythm.
@code{\oneVoice}.
@endpredefined
-Snippets:
-@rlsr{Simultaneous notes}.
-
@seealso
Learning Manual:
@rlearning{Voices contain music},
@@ -551,6 +573,9 @@ Notation Reference:
@ref{Invisible rests},
@ref{Stems}.
+Snippets:
+@rlsr{Simultaneous notes}.
+
@node Voice styles
@unnumberedsubsubsec Voice styles
@@ -591,7 +616,6 @@ standard presentation.
@code{\voiceNeutralStyle}.
@endpredefined
-
@seealso
Learning Manual:
@rlearning{I'm hearing Voices},
@@ -835,6 +859,7 @@ The requirements for successfully merging different note heads that
are at the same time differently dotted are not clear.
@end ignore
+
@node Automatic part combining
@unnumberedsubsubsec Automatic part combining
@@ -1001,7 +1026,6 @@ instrumentTwo = \relative c' {
@lilypondfile[verbatim,quote,texidoc,doctitle]
{changing-partcombine-texts.ly}
-
@seealso
Music Glossary:
@rglos{a due},
@@ -1018,7 +1042,6 @@ Internals Reference:
@rinternals{Voice}.
@knownissues
-
All @code{\partcombine...} functions can only accept two voices and are
not designed to work with lyrics; such that when one of the voices is
explicitly named in order to attach lyrics to it, the partcombiner will
@@ -1163,7 +1186,6 @@ global = {
}
@end lilypond
-
@seealso
Learning Manual:
@rlearning{Organizing pieces with variables}.