Keys Lock is doing strange things. I created a simple chord progression which I used to record the Scaler track and a piano track (input set to Scaler 3) in Studio One v7 using my keyboard. So far so good. I then added a synth track, set its input to Scaler 3, selected Keys Lock with chord mute on and hit record (this is the exact same workflow I have always used in Scaler 2). Without playing anything on the keyboard, the chord placeholder notes from the Scaler track were recorded onto the synth track. See attached screenshot.
1 Like
Not sure if I am understanding correctly. But if I am!:
Try turning on ‘Keys Lock Chord Mute’ in settings. You can also mute the track or Shift Click to mute the chords.
1 Like
I’m only using the main track to provide bindings to trigger from my keyboard, to record onto Studio One tracks. Nothing is played in Scaler. By arming both the Scaler and Piano tracks I record onto them at the same time using the keyboard. Having got those tracks recorded, I use keys lock to improvise a third track. Keys Lock Chord Mute is on. It isn’t recording the chords onto the third track, it’s recording the chord placeholder notes from the scaler track, i.e, just one note as per the screenshot. This all works perfectly in Scaler 2.
I posted the workflow on this forum in answer to a previous post a couple of months ago: Biggest wish for Scaler 3 - #4 by NickC4555
It works in Scaler 2, but not in 3 because of the problem I described, which you can see in the screenshot.
I’ve worked out what the problem is here. With active bind keys set to white, and 4 chords on the main track, record a progression on the Scaler track in the DAW (not Scaler’s arrange page) using the bind keys C2, D2, E2 and F2. Play the track back and Scaler will play the chords from the main track which correspond to each of those placeholder notes.
Turn Keys Lock on set to Chord Notes and the bindings change to the black notes, regardless of active bind keys being set to white in playback preferences. They stay that way even when keys lock is turned off again. I realise this behaviour is by design, but the consequence of it is that if you now play the Scaler track you previously recorded in the DAW, it no longer triggers the chords, but plays the notes C2, D2, E2 and F2. This is why the problem I described in my original post is happening, i.e. it then records those notes onto the improvised track rather than using the chords in the progression to bind the melody to.
So, to use keys lock with recorded DAW Scaler chord tracks, (not Scaler’s arrange page), you must start with your bindings on the black keys, then all is well.
Correct and that’s the trade off of having the whole white notes available to you. Worthwhile I think just takes some remembering! By the way download Scaler 3.0.1 as it fixes the issue of Bind area not reverting to white keys when turning Keys Lock off.
Thanks, Davide. I don’t use the left and right hands at the same time, I record a chord track, then use that for mapping keys lock notes to. Perhaps mine is an unusual workflow, but the issue, before I worked this out, is that the chord track isn’t a chord track any more after the bindings have changed from the white to the black keys. It might be worth mentioning this in the user guide.
I’ve just downloaded 3.0.1, thanks.