Motion Strum Bug

I am trying out the motion slow strum feature but I cant figure why when I trigger from my external midi keyboard the chords just abruptly cut off but when using the built in playback the chords play and ring out nicely. Is there a setting somewhere I am missing?

Cheers

Hmm. I’ll go and test your issue. I have possibly related issue (#3 in):

1 Like

your problem clearly related to:

1 Like

@fridayeve thank you for your help !

I can grab a protocol trace on my system if I get a bit more detail what is your arrangement (on scaler). I’m not sure if what I checked already is valid, therefore not saying anything yet from my results.

@fridayeve I am not really doing anything special just was testing out chords in standalone mode on Mac with my Key Step 37 connected by usb midi

ah. Now I think I understand. I was pressing a chord and leaving it down for a long time. If I actually play stuff, things get quickly weird. ā€œChopped audioā€ would be also my way to express the result.

I tried if different settings make any difference (perform->retrigger/follow, play quantize, motion on bound chords only).I could not hear much change.
EDIT: retrigger seems to work a bit better than follow. When using retrigger, must be quite careful to fully lift all keys before pressing next chord. (at least if using this in ā€œlive playā€).
When using follow and playing something, plays easily twice the same note and then gradually there are many notes which do not produce any output anymore. (waiting for a while, pressing C4, nothing comes out, but D4 could play for example).

I guess I’ll read the manual next if I’m doing something wrong, but then I guess I’m not alone.

I am having the same issue with the strums cutting off even though I am holding the key down.

All on our list and getting fixed soon!