RESOLVED: Bug in gestureCHOP output

Found this strange behaviour in build 19160.

I was playing around with using the gestureCHOP to record and loop playback input from a midi controller on the fly.

If you have a midi controller hooked up to the inputs of a gesture CHOP and you hit button and you toggle listen to input to 1 and make a change to the source input at roughly the same time, make some more changes to the source input and then toggle listen input to 0, the gesture playback looks like it has a kind of feedback problem and will recursively subtract from it’s output.

I’ve attached a quick tox that demonstrates the problem. Thanks!

base_gesture_bug.tox (2.8 KB)

Hi Sorry for the delay.
I wasn’t able to see any unusual activity.
You have the Step parameter set to 1, which automatically steps the beginning up or down to match the output. If you set it back to 0, you’ll see the original captured gestures again.

I’ve clarified the behavior a bit more in the docs:

Thanks,
Rob.

Aha! Always happy to discover that it’s my own mistake and not a bug. Thanks Rob!