From 8f2f4d6f0af1626a333050d367211a7d73437082 Mon Sep 17 00:00:00 2001 From: Trevor Daniels Date: Sun, 19 Apr 2015 23:03:12 +0100 Subject: [PATCH] Doc: Issue 4349: Clarify where changes to beatStructure should be placed Make it clear that changes to beatStructure and baseMoment apply only to the time signature currently in force, and hence that those changes must come immediately after a new \time command, not before it. --- Documentation/notation/rhythms.itely | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/Documentation/notation/rhythms.itely b/Documentation/notation/rhythms.itely index f14e0dbd99..db4109af9c 100644 --- a/Documentation/notation/rhythms.itely +++ b/Documentation/notation/rhythms.itely @@ -2095,6 +2095,14 @@ units of @code{baseMoment}. By default, @code{baseMoment} is one over the denominator of the time signature. By default, each unit of length @code{baseMoment} is a single beat. +Note that there are separate @code{beatStructure} and @code{baseMoment} +values for each time signature. Changes to these variables apply only +to the time signature that is currently in force, hence those changes +must be placed after the @code{\time} command which starts a new time +signature section, not before it. New values given to a particular +time signature are retained and reinstated whenever that time signature +is re-established. + @lilypond[quote,relative=2,verbatim] \time 5/16 c16^"default" c c c c | -- 2.39.2