Ok so I scale locked current scale to A# Lydian (minor) and I made a set of 4 chords for a progression. I put the midi into my arrangement and when I checked the key using a 3rd party plugin, it said the key is in D minor..
Tell me what im doing wrong? I had to transpose the midi 4 semitones to be in key…
Hi @jjoomusic there may be some confusion here. The lock button is only used to transpose the pre-made chord sets in section A. It has not effect on chords you have already added to the main track. Or perhaps I’m misunderstanding your question.
Thanks for the response. Definitely confused, would it be possible to make a tutorial for this ?
What im trying to understand is:
I want to make a chord progression in say F# minor Using the Chord set in “Part A”: Chord Set
How would I go about doing this? Do I first choose “F# minor” in Part B “Current Scale”, and once I select that I Lock the section at the top right in section A “Chord Set”
I think the UI can be fixed on this. Correct me if im wrong.
That lock button sure causes a lot of confusion. I wonder if there is a better way…
yes, Hopefully an update, or a tutorial of some sort.
Ive messed around with the lock button but its fidgety and also some Chord set progressions don’t use the scale that’s selected.
That is interesting to hear. The operation is basically a simplified version of the force into scale function from Scaler 2. In Scaler 2 this opened a list of all scales where you could choose a scale to transpose to. This felt redundant given there is already a scale selector in section B, so now the lock button just transposes selected chord sets to your current scale. Note this only happens after selecting a scale. So pressing the lock button will not change anything until a new scale is selected.
There have been requests for a scale lock function which simply retains your current scale selection without transposing anything which we do plan to implement.
I should clarify that the lock button will attempt to transpose chord sets from section A into the selected scale. But this is not always perfect. Some chord sets are quite clearly in a particular key e.g. I V VI IV etc, but sometimes it is ambiguous, even subjective. Scaler’s detection process for example lists detected scales in order of matching notes, but this list won’t necessarily reflect the creative intentions of the composer. The ‘Uncommon Progressions’ for example are generally based around a C major. chord, however their use borrowed chords means Scaler is unlikely to detect C major as the most relevant scale, which is also likely to throw off the scale lock transposition.
Overall this is something we agree has room for improvement, and we are of course appreciative of feedback and suggestions.