]> git.donarmstrong.com Git - lilypond.git/commitdiff
Issue 3202: changes.tely: deal with \transposition and instrumentTransposition changes
authorDavid Kastrup <dak@gnu.org>
Sun, 24 Feb 2013 12:20:31 +0000 (13:20 +0100)
committerDavid Kastrup <dak@gnu.org>
Wed, 27 Feb 2013 18:13:44 +0000 (19:13 +0100)
Those were introduced by issue 754 and issue 3168, respectively.

Documentation/changes.tely

index d3eb33d83b09a258b0ede114ae0ded72b4034eef..dab40a311297339e0686d820f7704877dd16d10d 100644 (file)
@@ -61,6 +61,29 @@ which scares away people.
 
 @end ignore
 
+@item
+The meaning of @code{instrumentTransposition} has been reversed.
+After
+@example
+\set instrumentTransposition = #@{ b #@}
+@end example
+a written @code{c'} now sounds like @code{b}.  Previously, this
+would have been the other way round.  This and the following change
+should make dealing with transposing instruments more
+straightforward.
+
+@item
+The music generated by @code{\set} and @code{\override} commands
+is no longer affected by @code{\transpose}.  The main consequence
+is that @code{\transpose} will transpose audible/@/concert pitch and
+printed pitch by the same amount even when the transposed music
+contains @code{\transposition}.  Previously,
+@example
+\transpose c' f' \transposition bes'
+@end example
+was equivalent to @code{\transposition f'}.  Now it stays
+equivalent to @code{\transposition bes'}.
+
 @item
 Tuplets are now created with the @code{\tuplet} command, which
 takes a fraction @code{@var{t}/@var{n}} to specify that @var{t}