Here are the three tickets I've submitted regarding Key Hold:
-1-
Key Hold On state not saved with patch if Sequencer is On
If Sequencer is on and Key Hold is on and the patch is saved, then when recalling the patch Key Hold is off. I.e. the Key Hold On state is not saved in this case.
(Could be the case if Arpeggiator is on too, since it affects other behavioural aspects of Key Hold just like Sequencer does - I didn’t test that and have just switched off my rig, so I’ll have to do that later)
Edit: It is possible to get the Key Hold on state saved, but it requires a certain sequence of pressing the Sequencer and Key Hold button. I’m not 100% sure about the pattern yet, but starting from an init patch, recording some notes, pressing Key Hold, then pressing Sequencer, then pressing Key Hold again and finally saving the sound seems to retain the Key Hold on state. Most other sequences of Sequencer and Key Hold presses will cause the Key Hold on state to not be saved. I.e. you need this/a clean and controlled sequence of presses that’s not likely to happen in a real life situation where buttons are pressed several times in random’ish sequences while making the sequence/patch, hence in most cases I’ve tried the on state isn’t saved.
BTW, I also found that so far it does not happen with the Arpeggiator.
Additional info:
I just discovered the following in of the test patches that I saved while testing for this bug, where the Key Hold is saved in the On state and with sequencer enabled and containing a few notes - this happens when the patch is selected and I go straight to pressing a key:
1 - The sequence starts playing with the Gate time is at its maximum, 99%, even though the patch was saved with a shorter gate (probably the default 50%). When turning the Gate knob, the gate time remains locked at its maximum.
2 - If I then press Play to stop the sequencer, the last played note will be held. If I switch Key Hold off, the note is still held. If I then switch Sequencer off, the Key Hold gets switched On “by itself” and the note is still held. Finally, if I now switch Key Hold off, the sound stops.
3 - After going through the sequence of actions in point 2, everything works as it should again. Key hold will function as expected and the Gate time is 50% and can be changed.
It seems like the Gate locked at maximum bug is related to, or part of, the saved Key Hold bug.
-2-
Velocity capture for key hold and arpeggiator
(forum thread:
https://forum.arturia.com/index.php?topic=90436.msg139628)
Capture of new velocities when Key Hold is on. Currently the first velocity captured is used for all subsequent notes.
Capture of velocity for each key when using the arpeggiator. Currently the first velocity captured is used for all keys, unlike my other synths.
Lack of velocity capture for last/individual notes is a bug - Arturia's description of intended functionality:
"The key hold keeps the last note played properties:
- Note
- Velocity
..."
-3-
When the sequencer is running, pressing key hold will immediately transpose the sequence to whichever key was last pressed - this can be quite unexpected and 'random'
The expected behaviour for this type of feature is to capture the first key pressed after it has been switched on.
