[icon]

GNU LilyPond

-- --

What is LilyPond
Home
Examples
Templates
Download
GNU/Linux binaries
Windows binaries
Source code
Documentation
Tutorial
Manual
Glossary
Index

Support
Mailing lists
Search
WikiWiki

External sites
lilypond.org/stable
lilypond.org/development
savannah.gnu.org
ftp.lilypond.org
Mutopia
Other music online

Multi measure rests

Multi measure rests are entered using `R'. It is specifically meant for full bar rests and for entering parts: the rest can expand to fill a score with rests, or it can be printed as a single multimeasure rest This expansion is controlled by the property Score.skipBars. If this is set to true, Lily will not expand empty measures, and the appropriate number is added automatically.

      \time 4/4 r1 | R1 | R1*2
      \property Score.skipBars = ##t R1*17  R1*4
     
[picture of music]

The 1 in R1 is similar to the duration notation used for notes. Hence, for time signatures other than 4/4, you must enter other durations. This can be done with augmentation dots, or with fractions:

      \property Score.skipBars = ##t
      \time 3/4
       R2. | R2.*2
      \time 13/8
      R1*13/8
      R1*13/8*12
     
[picture of music]
Notice that a R spanning a single measure is printed as a whole rest centered in the measure, regardless of the time signature.

[ add note about breves.]

Texts can be added to multi-measure rests by using the note-markup syntax. An identifier is provided for a fermata.

       \time 3/4
       R2._\markup { \roman "Ad lib" }
       R2.^\fermataMarkup
     
[picture of music]
By default, the multi-measure rest uses the number font, which does not contain any letters. This is the reason for the explicit \roman in the above example.

The object for this object is MultiMeasureRest , and MultiMeasureRestNumber .

BUGS

Only one text can be put on a multi-measure rest with note-text syntax, since this is internally converted to setting #'text in MultiMeasureRestNumber . It is not possible to use fingerings (e.g. R1-4) to put numbers over multi-measure rests.

Currently, there is no way to automatically condense multiple rests into a single multimeasure rest. Multi measure rests do not take part in rest collisions.

Go back to index of LilyPond.

Please send GNU LilyPond questions and comments to lilypond-user@gnu.org.

Please send comments on these web pages to (address unknown)

Copyright (c) 1997--2002 Han-Wen Nienhuys and Jan Nieuwenhuizen.

Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved.


This page was built from LilyPond-1.7.14 (development-branch) by

Buchan Milne <(address unknown)>, Thu Mar 6 21:11:35 2003 CET.