From: D. Michael McIntyre <michael.mcintyre@ro...> - 2007-10-11 00:39:41
I just submitted #1811226, talking about octaves and the auto transpose
In the example, original part is in concert Eb major, user copies the part to
a new track, sets the copy segment transpose to -7, then uses the key
signature dialog to bring about the transposition of the key signature and
the part to suit the target -7 instrument. The result is that the part
sounds correctly, but an octave too low.
I wonder what's the best way to address this, as I see two use cases for this
key signature dialog transpose feature.
Case 1: User is working with a concert pitch part they want to
rearrange/print for a transposing instrument, as in the cited example. In
this case, keeping the same octave as the original is important, and our not
doing that is a bug.
Case 2: User is using the key sig transpose to modulate some existing
notation in the same context as the original. For example, I've written
scale exercises for a Bb instrument at segment transpose -2, and then changed
the key signature, and allowed the automagic transposition from the dialog to
occur in order to modulate my exercise into different keys.
In case 2, I'm not sure preserving the original octave is important, or even
necessarily desireable. Is it ever *wrong*?
In case 1, preserving the original octave is very important, and always
I wonder how to reconcile the two. Maybe code that took segment transpose
into account when making an octave decision might automatically reconcile the
two use cases in the field.
Interesting ground to play with. Suggestions welcome. I'm throwing a copy to
the user list too.
If we get some good concensus in time, I just might be able to go twiddle this
right quick before the next release. It's probably only five lines of code to
effect this change, though finding where to stick them, and what they should
say is always the challenge.
D. Michael McIntyre