When restarting Scaler 3.2 in subsequent Logic Pro session, the Current Scale (Section B) plays the chords an octave lower without user command, even though the Octave display retains original Octave number. Workaround is to drag Oct up-and-down-again to reset correct octave. Moving chords to Main Track (Section C) appears to de-couple the bug from Section B.
Referring to the User Guide, is the Oct setting in Section B (5) intended to be an absolute value or a relative shift in value?
Hi @beport And welcome to the forum.
I just tried:
Thanks, Davide. Yes, I was able to reproduce your workflow - no problem with normal triads.
The bug appears with voicings in Section B. In this example I have chosen Voicing 2 for the instrument Noire in Komplete Kontrol.
In the first screenshot, I have selected “Oct 3” and you see the key positions of chord Eb Maj are actually registering in the 4th octave.
When I save and restart my project in Logic, the same chord is registering an octave lower in the 3rd octave. Scaler’s Section B display, however, is showing “Oct 3” in both instances.
Are you able to reproduce this workflow?
Ahh got it. It seems on further testing Variations and Inversions octaves are note retained in Colors Page and Section B on Browse Page.
Thanks for pointing that out. We will get this looked at.
Thank you for taking the time to look at this, Davide.
Would it be possible to add a lock to Section B of the Browse Page?
I agree with Christian in his post Chord set lock to current scale that once you have started working, the Current Scale in Section B should have no lower priority (in both key and octave) than the Chord Set in Section A.
I would also expect a lock to hold its own properties rather to impart properties on another element.
If this makes sense, would you agree? Happy Christmas wherever you are!
