<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<!-- header_tag -->
<html lang="en">
<head>
<title>Automatic part combining - GNU LilyPond Notation Reference</title>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="description" content="GNU LilyPond Notation Reference">
<meta name="generator" content="makeinfo 4.11">
<link title="Top" rel="start" href="index.de.html#Top">
<link rel="up" href="Multiple-voices.de.html#Multiple-voices" title="Multiple voices">
<link rel="prev" href="Collision-resolution.de.html#Collision-resolution" title="Collision resolution">
<link rel="next" href="Writing-music-in-parallel.de.html#Writing-music-in-parallel" title="Writing music in parallel">
<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
<!--
Copyright (C) 1999--2007 by the authors
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License,
Version 1.1 or any later version published by the Free Software
Foundation; with no Invariant Sections. A copy of the license is
included in the section entitled ``GNU Free Documentation
License''.
-->
<meta http-equiv="Content-Style-Type" content="text/css">
<style type="text/css"><!--
pre.display { font-family:inherit }
pre.format { font-family:inherit }
pre.smalldisplay { font-family:inherit; font-size:smaller }
pre.smallformat { font-family:inherit; font-size:smaller }
pre.smallexample { font-size:smaller }
pre.smalllisp { font-size:smaller }
span.sc { font-variant:small-caps }
span.roman { font-family:serif; font-weight:normal; }
span.sansserif { font-family:sans-serif; font-weight:normal; }
hr { border:0; height:1; color: #000000; background-color: #000000; }
/* hr {
border: none;
height: 1px;
color: #666666;
background-color: #666666;
}
body {
border-left: 1px solid #666666;
border-right: 1px solid #666666;
color: #332d28;
margin-right: auto;
margin-left: auto;
width: 60em;
list-style-type: square;
font-family: Arial,Helvetica,sans-serif;
padding-right: 1em;
padding-left: 1em;
}
a {
border-bottom: 1px dashed #344242;
text-decoration: none;
color: #344242;
}
a:link {
text-decoration: none;
}
a:visited {
border-bottom: 1px dashed #666666;
color: #666666;
}
a:active {
border-bottom: 1px solid #00cccc;
color: #00cccc;
}
a:hover {
border-bottom: 1px solid #1d7b85;
color: #1d7b85;
}
blockquote {
border: 1px solid #cccccc;
padding: 3px;
width: 40em;
}
.node {
border-left: 1px solid #666666;
margin: -0.5em 0px 1em;
padding: 2px 1px 0px;
font-style: italic;
}
.node a {
border: none;
text-decoration: underline;
font-style: normal;
font-weight: bold;
}
.verbatim {
font-family: "Courier New",Courier,monospace;
}
.unnumberedsubsubsec {
font-size: large;
color: #1d7b85;
}
.subsubheading {
font-size: large;
color: #3b220d;
}
.contents {
border: 1px dashed #339999;
margin: 3px 2em;
list-style-type: square;
padding-right: 1em;
width: 40em;
background-color: #fcfff9;
}
.contents a {
border-bottom: 1px dashed #423d34;
text-decoration: none;
color: #423d34;
}
.contents a:visited {
border-bottom: 1px dashed #666666;
color: #666666;
}
.contents a:active {
border-bottom: 1px solid #f0d86d;
color: #f0d86d;
}
.contents a:hover {
border-bottom: 1px solid #3b220d;
color: #3b220d;
}
.menu {
border-left: 1px dashed #339999;
margin: 3px 2em 1em;
list-style-type: square;
padding-left: 1.4em;
width: 40em;
}
.unnumbered {
}
h2 {
font-size: x-large;
color: #1d7b85;
}
*/
--></style>
</head>
<BODY BGCOLOR=WHITE TEXT=BLACK>
<div class="node">
<p>
<a name="Automatic-part-combining"></a>
Next: <a rel="next" accesskey="n" href="Writing-music-in-parallel.de.html#Writing-music-in-parallel">Writing music in parallel</a>,
Previous: <a rel="previous" accesskey="p" href="Collision-resolution.de.html#Collision-resolution">Collision resolution</a>,
Up: <a rel="up" accesskey="u" href="Multiple-voices.de.html#Multiple-voices">Multiple voices</a>
<hr>
</div>
<h5 class="unnumberedsubsubsec">Automatic part combining</h5>
<p><a name="index-automatic-part-combining-1301"></a><a name="index-part-combiner-1302"></a><a name="index-combining-parts-1303"></a><a name="index-g_t_005cpartcombine-1304"></a><a name="index-g_t_005cpartcombine-1305"></a>
<p>Automatic part combining is used to merge two parts of music onto
a staff. It is aimed at typesetting orchestral scores. When the
two parts are identical for a period of time, only one is shown.
In places where the two parts differ, they are typeset as separate
voices, and stem directions are set automatically. Also, solo and
<var>a due</var> parts are identified and marked by default.
<p>The syntax for part combining is:
<pre class="example">\partcombine <var>musicexpr1</var> <var>musicexpr2</var>
</pre>
<p>The following example demonstrates the basic functionality of the
part combiner: putting parts on one staff and setting stem
directions and polyphony. The same variables are used for the
independent parts and the combined staff.
<blockquote>
<pre class="verbatim">
instrumentOne = \relative c' {
c4 d e f
R1
d'4 c b a
b4 g2 f4
e1
}
instrumentTwo = \relative g' {
R1
g4 a b c
d c b a
g f( e) d
e1
}
<<
\new Staff \instrumentOne
\new Staff \instrumentTwo
\new Staff \partcombine \instrumentOne \instrumentTwo
>>
</pre>
<p>
<a href="../a3/lily-643791bc.ly">
<img align="middle"
border="0" src="../a3/lily-643791bc.png" alt="[image of music]">
</a>
</p>
</blockquote>
<p>The notes in the third measure appear only once, although they
were specified in both parts. Stem, slur, and tie directions are
set automatically, depending whether there is a solo or unison.
When needed in polyphony situations, the first part (with context
called <code>one</code>) always gets up stems, while the second (called
<code>two</code>) always gets down stems. In solo situations, the parts
get marked with ‘Solo’ and ‘Solo II’, respectively. The
unisono (<var>a due</var>) parts are marked by default with the
text “a2”.
<p>Both arguments to <code>\partcombine</code> will be interpreted as
<code>Voice</code> contexts. If using relative octaves,
<code>\relative</code> should be specified for both music expressions,
i.e.,
<pre class="example">\partcombine
\relative ... <var>musicexpr1</var>
\relative ... <var>musicexpr2</var>
</pre>
<p class="noindent">A <code>\relative</code> section that is outside of <code>\partcombine</code>
has no effect on the pitches of <var>musicexpr1</var> and
<var>musicexpr2</var>.
<p class="noindent">
<h5 class="subsubheading">Selected Snippets</h5>
<p><em>Combining two parts on the same staff</em>
<p>The part combiner tool ( <code>\partcombine</code> command ) allows the
combination of several different parts on the same staff. Text
directions such as "solo" or "a2" are added by default; to remove
them, simply set the property <code>printPartCombineTexts</code> to
"false". For vocal scores (hymns), there is no need to add
"solo"/"a2" texts, so they should be switched off. However, it
might be better not to use it if there are any solos, as they won't be
indicated. In such cases, standard polyphonic notation may be
preferable.
<p>This snippet presents the three ways two parts can be printed on a same
staff: standard polyphony, <code>\partcombine</code> without texts, and
<code>\partcombine</code> with texts.
<blockquote>
<pre class="verbatim">
musicUp = \relative c'' {
\time 4/4
a4 c4.( g8) a4 |
g4 e' g,( a8 b) |
c b a2.
}
musicDown = \relative c'' {
g4 e4.( d8) c4 |
r2 g'4( f8 e) |
d2 \stemDown a
}
\score {
<<
<<
\new Staff {
\set Staff.instrumentName = "Standard polyphony "
<< \musicUp \\ \musicDown >>
}
\new Staff \with { printPartCombineTexts = ##f } {
\set Staff.instrumentName = "PartCombine without texts "
\partcombine \musicUp \musicDown
}
\new Staff {
\set Staff.instrumentName = "PartCombine with texts "
\partcombine \musicUp \musicDown
}
>>
>>
\layout {
indent = 6.0\cm
\context {
\Score
\override SystemStartBar #'collapse-height = #30
}
}
}
</pre>
<p>
<a href="../a0/lily-46374218.ly">
<img align="middle"
border="0" src="../a0/lily-46374218.png" alt="[image of music]">
</a>
</p>
</blockquote>
<p><em>Changing partcombine texts</em>
<p>When using the automatic part combining feature, the printed text for
the solo and unison sections may be changed:
<blockquote>
<pre class="verbatim">
\new Staff <<
\set Staff.soloText = #"girl"
\set Staff.soloIIText = #"boy"
\set Staff.aDueText = #"together"
\partcombine
\relative c'' {
g4 g r r
a2 g
}
\relative c'' {
r4 r a( b)
a2 g
}
>>
</pre>
<p>
<a href="../a0/lily-b9c2cb19.ly">
<img align="middle"
border="0" src="../a0/lily-b9c2cb19.png" alt="[image of music]">
</a>
</p>
</blockquote>
<p class="noindent">
<h5 class="subsubheading">See also</h5>
<p class="indent">
<p>Music Glossary:
<a name="index-a-due-1306"></a><a href="../music-glossary/a-due.de.html#a-due">a due</a>,
<a name="index-part-1307"></a><a href="../music-glossary/part.de.html#part">part</a>.
<p>Notation Reference:
<a href="Writing-parts.de.html#Writing-parts">Writing parts</a>.
<p>Snippets:
<a href="../../../input/lsr/lilypond-snippets/Simultaneous-notes.html#Simultaneous-notes">Simultaneous notes</a>.
<p>Internals Reference:
<a name="index-PartCombineMusic-1308"></a><a href="../lilypond-internals/PartCombineMusic.de.html#PartCombineMusic">PartCombineMusic</a>,
<a name="index-Voice-1309"></a><a href="../lilypond-internals/Voice.de.html#Voice">Voice</a>.
<p class="noindent">
<h5 class="subsubheading">Known issues and warnings</h5>
<p>When <code>printPartCombineTexts</code> is set, if the two voices play
the same notes on and off, the part combiner may typeset <code>a2</code>
more than once in a measure.
<p><code>\partcombine</code> cannot be inside <code>\times</code>.
<p><code>\partcombine</code> cannot be inside <code>\relative</code>.
<p>Internally, the <code>\partcombine</code> interprets both arguments as
<code>Voice</code>s named <code>one</code> and <code>two</code>, and then decides
when the parts can be combined. Consequently, if the arguments
switch to differently named <a name="index-Voice-1310"></a><a href="../lilypond-internals/Voice.de.html#Voice">Voice</a> contexts, the
events in those will be ignored.
<!-- IIRC in users list someone pointed out more issues. TODO: lookup FV -->
<!-- footer_tag --><br><hr>
<div class="node">
<p>
Next: <a rel="next" accesskey="n" href="Writing-music-in-parallel.de.html#Writing-music-in-parallel">Writing music in parallel</a>,
Previous: <a rel="previous" accesskey="p" href="Collision-resolution.de.html#Collision-resolution">Collision resolution</a>,
Up: <a rel="up" accesskey="u" href="Multiple-voices.de.html#Multiple-voices">Multiple voices</a>
</div>
<div style="background-color: #e8ffe8; padding: 2; border: #c0ffc0 1px solid;">
<p>
<font size="-1">
Diese Seite ist für LilyPond-2.11.57 (Entwicklungszweig).
<br>
<address>
Fehler bitte an <a href="http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.bugs">http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.bugs</a> melden. </address>
<br>
Ihre <a href="http://lilypond.org/web/devel/participating/documentation-adding">Vorschläge für die Dokumentation</a> sind willkommen.
</font>
</p>
</div>
<P>
Andere Sprachen: <a href="Automatic-part-combining.fr.html">français</a>, <a href="Automatic-part-combining.es.html">español</a>.
<BR>
</P>
</BODY></html>
