<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<!-- header_tag -->
<html lang="en">
<head>
<title>Creating contexts - GNU LilyPond Learning Manual</title>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="description" content="GNU LilyPond Learning Manual">
<meta name="generator" content="makeinfo 4.11">
<link title="Top" rel="start" href="index.de.html#Top">
<link rel="up" href="Contexts-and-engravers.de.html#Contexts-and-engravers" title="Contexts and engravers">
<link rel="prev" href="Contexts-explained.de.html#Contexts-explained" title="Contexts explained">
<link rel="next" href="Engravers-explained.de.html#Engravers-explained" title="Engravers explained">
<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="Creating-contexts"></a>
Next: <a rel="next" accesskey="n" href="Engravers-explained.de.html#Engravers-explained">Engravers explained</a>,
Previous: <a rel="previous" accesskey="p" href="Contexts-explained.de.html#Contexts-explained">Contexts explained</a>,
Up: <a rel="up" accesskey="u" href="Contexts-and-engravers.de.html#Contexts-and-engravers">Contexts and engravers</a>
<hr>
</div>
<h4 class="subsection">3.3.2 Creating contexts</h4>
<p><a name="index-g_t_005cnew-286"></a><a name="index-g_t_005cnew-287"></a>
<a name="index-new-contexts-288"></a><a name="index-creating-contexts-289"></a><a name="index-contexts_002c-creating-290"></a>
There can be only one top level context: the
<code>Score</code>
context. This is created with the <code>\score</code> command,
or, in simple scores, it is created automatically.
<p>For scores with only one voice and one staff, the
<code>Voice</code> and <code>Staff</code> contexts may be left to be
created automatically, but for more complex scores it is
necessary to create them by hand.
The simplest command that does this is <code>\new</code>.
It is prepended to a music expression, for example
<pre class="example">\new <var>type</var> <var>music-expression</var>
</pre>
<p class="noindent">where <var>type</var> is a context name (like <code>Staff</code> or
<code>Voice</code>). This command creates a new context, and starts
interpreting the <var>music-expression</var> within that context.
<p>Note that there is no <code>\new Score</code> command;
the single top-level <code>Score</code> context is introduced
with <code>\score</code>.
<p>You have seen many practical examples which created new
<code>Staff</code> and <code>Voice</code> contexts in earlier sections, but
to remind you how these commands are used in practice, here's an
annotated real-music example:
<blockquote>
<pre class="verbatim">
\score { % start of single compound music expression
<< % start of simultaneous staves section
\time 2/4
\new Staff { % create RH staff
\key g \minor
\clef "treble"
\new Voice { % create voice for RH notes
\relative c'' { % start of RH notes
d4 ees16 c8. |
d4 ees16 c8. |
} % end of RH notes
} % end of RH voice
} % end of RH staff
\new Staff << % create LH staff; needs two simultaneous voices
\key g \minor
\clef "bass"
\new Voice { % create LH voice one
\voiceOne
\relative g { % start of LH voice one notes
g8 <bes d> ees, <g c> |
g8 <bes d> ees, <g c> |
} % end of LH voice one notes
} % end of LH voice one
\new Voice { % create LH voice two
\voiceTwo
\relative g { % start of LH voice two notes
g4 ees |
g4 ees |
} % end of LH voice two notes
} % end of LH voice two
>> % end of LH staff
>> % end of simultaneous staves section
} % end of single compound music expression
</pre>
<p>
<a href="../df/lily-ac4890dc.ly">
<img align="middle"
border="0" src="../df/lily-ac4890dc.png" alt="[image of music]">
</a>
</p>
</blockquote>
<p>(Note how all the statements which open a block with either a
curly bracket, <code>{</code>, or double angle brackets, <code><<</code>,
are indented by two further spaces, and the corresponding
closing bracket is indented by exactly the same amount. While
this is not required, following this practice will greatly
reduce the number of ‘unmatched bracket’ errors, and is
strongly recommended. It enables the structure of the music to
be seen at a glance, and any unmatched brackets will be obvious.
Note too how the LH staff is created using double angle brackets
because it requires two voices for its music, whereas the RH staff
is created with a single music expression surrounded by curly
brackets because it requires only one voice.)
<p><a name="index-contexts_002c-naming-291"></a><a name="index-naming-contexts-292"></a>
The <code>\new</code> command may also give a identifying name to the
context to distinguish it from other contexts of the same type,
<pre class="example">\new <var>type</var> = <var>id</var> <var>music-expression</var>
</pre>
<p>Note the distinction between the name of the context type,
<code>Staff</code>, <code>Voice</code>, etc, and the identifying name of a
particular instance of that type, which can be any sequence of letters
and digits invented by the user. The identifying name is used to
refer back to that particular instance of a context. We saw this in
use in the section on lyrics, see <a href="Voices-and-vocals.de.html#Voices-and-vocals">Voices and vocals</a>.
<p class="noindent">
<h5 class="subsubheading">See also</h5>
<p class="indent">
<p>Notation Reference: <a name="index-Creating-contexts-293"></a><a href="../lilypond/Creating-contexts.de.html#Creating-contexts">Creating contexts</a>.
<!-- footer_tag --><br><hr>
<div class="node">
<p>
Next: <a rel="next" accesskey="n" href="Engravers-explained.de.html#Engravers-explained">Engravers explained</a>,
Previous: <a rel="previous" accesskey="p" href="Contexts-explained.de.html#Contexts-explained">Contexts explained</a>,
Up: <a rel="up" accesskey="u" href="Contexts-and-engravers.de.html#Contexts-and-engravers">Contexts and engravers</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="Creating-contexts.fr.html">français</a>, <a href="Creating-contexts.es.html">español</a>.
<BR>
</P>
</BODY></html>
