I’m running into a bug when changing voicing using the V9 buttons in the B sections of both the Browse and Create pages:
Using the A minor scale as an example, when I initially select the scale and have Octave set to 2 I get a set of chords rooted at A2, B2, C3, D3, E3, F3 and G3. However if I change the voicing to a different one, the new set of chords are rooted at A2, B2, C2, D2, E2, F2 and G2. So in the A minor example, my iii through VII chords in the new voicing are rooted lower than my i and ii chords. The voicing change logic is applying the Octave value of 2 to all the root notes.
It does not seem to matter what the original and new voicings are, changing the voicing always drops all of the chords rooted at C and above down an octave for any non-C scale. There is a workaround to get back to a set of correctly rooted chords in the new voicing by switching Current Scale to a different scale and then back to the desired one but it would be nice not to have to do the extra step.
If you go in the Circle of 5’s tab of the creation page and check the value of the “octave settings” for each chords am I correct to assume that the value for the A2 and B2 chords are set to 0 and that the value for the C2, D2, E2, F2 and G2 is set to 1 ?
By the way I’ve just try what you did and I have exactly the same results as you described.
Yes, in the correct chord sequence (A minor chords going from A2 to G3), the A2 and B2 chords have the Octaves field set to 0 and the rest all have it set to 1 in the Create->Circle of Fifths->Octaves setting. After changing the voicing (which results in C3 through G3 rooted chords dropping down to C2 through G2) all the chords have Octaves set to 0.
Hi @GrapefruitDream, thanks for the feedback here. Yes the issue of certain scale’s chords jumping in octaves after voicing adjustments is one we are aware of and do have planned to address in the upcoming Scaler 3.1.1 update.