From 542e3d65db99d49cde198417fa7818ec95392076 Mon Sep 17 00:00:00 2001 From: Carl Sorensen Date: Fri, 15 Aug 2008 08:26:51 -0600 Subject: [PATCH] Updates to rhythms.itely --- Documentation/user/rhythms.itely | 213 +++++++++++++++++++++---------- 1 file changed, 148 insertions(+), 65 deletions(-) diff --git a/Documentation/user/rhythms.itely b/Documentation/user/rhythms.itely index 1bd07dd5ec..dad96865e0 100644 --- a/Documentation/user/rhythms.itely +++ b/Documentation/user/rhythms.itely @@ -799,15 +799,12 @@ setting, resulting bar-check warnings may not be displayed. @lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle] {positioning-multi--measure-rests.ly} -@c TODO -- convert to snippet +@c TODO -- convert to snippet -- submitted to Neil Markups attached to a multi-measure rest will be centered above or below it. Long markups attached to multi-measure rests do not cause the measure to expand. To expand a multi-measure rest to fit the markup, use a spacer rest with an attached markup before the multi-measure rest: -@c -- music is somewhat compressed vertically. I thought it -@c was good because the emphasis is not on the content -@c of the markup, but on the place the markup was attached -cs @lilypond[quote,ragged-right,verbatim,fragment,relative=2] \compressFullBarRests \textLengthOn @@ -1082,17 +1079,6 @@ Internal Reference: @cindex grace notes, in anacruses -This command does not take into account grace notes at the start -of the music. If the pick-up starts with one or more grace -notes, then the @code{\partial} should follow the grace note(s): - -@lilypond[verbatim,quote,ragged-right,relative,fragment] -\grace f16 -\partial 4 -g4 -a2 g2 -@end lilypond - The @code{\partial} command is intended to be used only at the beginning of a piece. If you use it after the beginning, some odd warnings may occur. @@ -1177,38 +1163,6 @@ to indicate where breaks can occur. Polymetric notation is supported, either explicitly or through clever use of markup features. -@c Each of these examples uses \set or \override, and therefore -@c by policy should be converted to a snippet. -@c Do we want to have a section with a very brief (two-line -@c introduction, and have most of the content be in snippets? - -@strong{Alternating time signatures} - -Regularly alternating double time signatures are not supported -explicitly, but they can be faked. In the next example, the -double time signature is created with markup text, while the -real time signature is set in the usual way with @code{\time}. - -@lilypond[verbatim,ragged-right] -% Create 9/8 split into 2/4 + 5/8 -tsMarkup = \markup { - \override #'(baseline-skip . 2) \number { - \column { "2" "4" } - \vcenter "+" - \bracket \column { "5" "8" } - } -} - -{ - \override Staff.TimeSignature #'stencil = - #ly:text-interface::print - \override Staff.TimeSignature #'text = #tsMarkup - \time 9/8 - c'2 \bar ":" c'4 c'4. - c'2 \bar ":" c'4 c'4. -} -@end lilypond - @strong{Staves with different time signatures, equal measure lengths} This notation can be created by setting a common time signature @@ -1249,9 +1203,6 @@ staff, shown durations are multiplied by 3/5, as 3/5 * 10/8 = 3/4. >> } @end lilypond -@c I guess this example doesn't use \set or \override, and so -@c could stay in the manual. - @strong{Staves with different time signatures, unequal bar lengths} Each staff can be given its own independent time signature by @@ -1295,6 +1246,37 @@ moving the @code{Timing_translator} to the @code{Staff} context. >> @end lilypond +@snippets + +@c TODO -- Convert to snippet. -- Sent to Neil 8/14/08 + +@strong{Alternating time signatures} + +Regularly alternating double time signatures are not supported +explicitly, but they can be faked. In the next example, the +double time signature is created with markup text, while the +real time signature is set in the usual way with @code{\time}. + +@lilypond[verbatim,ragged-right] +% Create 9/8 split into 2/4 + 5/8 +tsMarkup = \markup { + \override #'(baseline-skip . 2) \number { + \column { "2" "4" } + \vcenter "+" + \bracket \column { "5" "8" } + } +} + +{ + \override Staff.TimeSignature #'stencil = + #ly:text-interface::print + \override Staff.TimeSignature #'text = #tsMarkup + \time 9/8 + c'2 \bar ":" c'4 c'4. + c'2 \bar ":" c'4 c'4. +} +@end lilypond + @seealso @@ -1350,13 +1332,6 @@ inserts ties. One of its uses is to debug complex scores: if the measures are not entirely filled, then the ties show exactly how much each measure is off. -To allow line breaking on the bar lines where the -@code{Completion_heads_engraver} has inserted a split note, remove -the @code{Forbid_line_break_engraver} too. - -TODO -- find example that shows the above paragraph. I can't make -the Forbid_line_break_engraver have any effect in my examples (cs). -Does the Forbid_line_break_engraver still have the claimed effect? @seealso Music Glossary: @rglos{tie} @@ -1391,16 +1366,116 @@ Sometimes you might want to show only the rhythm of a melody. This can be done with the rhythmic staff. All pitches of notes on such a staff are squashed, and the staff itself has a single line -@c TODO Devise a more realistic example, perhaps with lyrics -td @lilypond[quote,ragged-right,fragment,relative=1,verbatim] -\new RhythmicStaff { - \time 4/4 - c4 e8 f g2 | r4 g r2 | g1 | r1 | -} +<< + \new RhythmicStaff { + \new Voice = "myRhythm" { + \time 4/4 + c4 e8 f g2 + r4 g g f + g1 + } + } + \new Lyrics { + \lyricsto "myRhythm" { + This is my song + I like to sing + } + } +>> @end lilypond -TODO -- put example in with multiple lines as well (used for strumming -rhythms in guitar) +Guitar chord charts often show the strumming rhythms. This can +be done with the @code{Pitch_squash_engraver} and +@code{\improvisationOn}. + + +@lilypond[quote,verbatim] +<< + \new ChordNames { + \chordmode { + c1 f g c + } + } + + \new Voice \with { + \consists Pitch_squash_engraver + } \relative c'' { + \improvisationOn + c4 c8 c c4 c8 c + f4 f8 f f4 f8 f + g4 g8 g g4 g8 g + c4 c8 c c4 c8 c + } +>> +@end lilypond + +@predefined +@code{\improvisationOn}, +@code{\improvisationOff}. + +@snippets +@c TODO -- Convert to snippet; +@c tag for both Rhythms and Guitar? Move to @seealso? + +For guitar music, it is possible to show strum rhythms, along +with melody notes, chord names, and fret diagrams. + + +@lilypond[quote,verbatim] +\include "predefined-guitar-fretboards.ly" +<< + \new ChordNames { + \chordmode { + c1 f g c + } + } + + \new FretBoards { + \chordmode { + c1 f g c + } + } + + + \new Voice \with { + \consists Pitch_squash_engraver + } \relative c'' { + \improvisationOn + c4 c8 c c4 c8 c + f4 f8 f f4 f8 f + g4 g8 g g4 g8 g + c4 c8 c c4 c8 c + } + + + \new Voice = "melody" { + \relative c'' { + \improvisationOff + c2 e4 e4 + f2. r4 + g2. a4 + e4 c2. + } + } + + \new Lyrics { + \lyricsto "melody" { + This is my song. + I like to sing. + } + } +>> +@end lilypond + +@seealso + +Snippets: +@rlsr{Rhythms}. + +Internals Reference: +@rinternals{RhythmicStaff}, +@rinternals{Pitch_squash_engraver}. @node Beams @subsection Beams @@ -1446,6 +1521,9 @@ c4 c8 c8. c16 c8. c16 c8 @end lilypond +@predefined +@code{\autoBeamOff}, +@code{\autoBeamOn}. @snippets @@ -1527,7 +1605,12 @@ f8 f''8 f8 f''8 @seealso -Notation Reference: @ref{Manual beams}, @ref{Setting automatic beam behavior}. +Notation Reference: +@ref{Manual beams}, +@ref{Setting automatic beam behavior}. + +Installed Files: +@file{scm/auto-beam.scm}. Snippets: @rlsr{Rhythms}. -- 2.39.5