Scaler 3 erroneously sends release messages to notes when changing chords with Keys Lock - Chord notes

Scaler 3 Support Bug Reports
,
1

Reposted this, as I just realized I placed it in the Bug Reports section for Scaler 2

Steps to reproduce:

  • Insert an instance of Scaler 3, and lock keys to some set of chords (the yellow notes)
  • Set Keys Lock to “Chord Notes”
  • In preferences, set “Keys Lock Chord Mute” to On
  • On a keyboard, hold one of the yellow Chord notes while playing the upper register “Locked Keys” notes in blue. Alternate between yellow notes (chords) while playing the same upper register notes.

Expected behavior:

  • Holding down the (blue) keys should always sustain the note of the held key, regardless of whether the lower (yellow) chord notes are being triggered

Observed behavior:

  • As you can see in the video, some combination of playing the yellow and blue keys can trigger a premature release for some or all notes. This means that, while holding down the blue notes, the notes will sound for only a split second and released, even if my right hand is holding down those notes. This results in unexpected behavior, where (with this workflow) it’s hard to predict whether the notes I’m holding down will sound fully, or be released immediately.

I’ve uploaded a video to demonstrate this behavior– release messages Scalar.mov - Google Drive

1 Like
2

Hi @colorthought welcome to the forum. Thanks for your findings here. We are looking into reports of this behaviour such as this thread however they can be difficult to reproduce. Do you find this is happening often in regular use?

This kind of behaviour can happen with keys lock chord mute disabled however it should not be happening when mute is enabled.

We are working to improve some aspects of keys lock including the reaction speed to chord triggers so hopefully we can address this also.