It seems to work well here in Bitwig but we will have a look in detail during the week.
The Keys-Lock feature can mute/redirect notes. If there is MIDI content playing on Scaler’s track, it might affect the output notes differently than what you expect. It will combine the notes from the track and the ones you play on your controller and both might trigger changes in Scaler.
You are right. Those lock modes are not reactive to chord so it has never been needed or asked as far as I know. I see how it can be counter-intuitive, we will have a chat with the team about this.
There is no controller being used, just a midi clip. The problem appears to be the way Bitwig handles 2 note on events that occur at the same time - shifting the non-chord triggers to be a fraction later makes it work as expected, so it would appear to be something Bitwig needs to fix.
I’ve had a reply from Bitwig regarding the notes not playing correctly and they say it is to do with the way the plugin is handling the timing. The reply is quoted below:
This seems to be a timing issue in the plugin. The reason could be that In contrast to other DAWs, Bitwig Studio stores and plays midi notes with the same timing precision as the audio engine runs, not the typically more coarse midi resolution used in other hosts.
I bought Scaler today, and it seems I just ran into this issue.
I can reproduce it easily: If I setup keylock with chord notes and set chord mute to “muted,” if I press a “chord note” and hold it, as soon as press a “chord key”, it cuts off the “chord note” I was holding.
As someone else stated earlier in the thread, this does not happen with the first three keylock modes.
Is this a bug, or is it working as intended? If it is intended, it seems to limit its usefulness, as your notes get cutoff every time you play a chord.