Press the Trigger parameter button a second time to switch over to the ratcheting screen… you can set the ratchets (repeats) to be 1 (none), 2, 3 or 4. I tried with higher ratchets, but unless your master clock is running pretty slow, it seems a little too fast for Ansible to keep up with so I set the max to 4 (much like the ratchets on the Mother-32 that you hear in the video above).
Haven’t yet adapted the Teletype Ops to work with the ratcheting parameter, but will soon…
oops yea that makes sense. i have a separate branch on my github for the ratcheting feature and i didn’t merge it back into the master. i’ll update it when i am back home again.
This is great! Should adding trigs work in the ratcheting screen? The grid lights up as though you are, but the gate outputs don’t update until you add them in the “main” view.
hmm i don’t think so? it’s more like it’s own parameter like the original four. it has its own loop points, clock divider, probability, etc so it’s not really linked to any particular steps on the trigger screen.
Oh wow, I didn’t realize that it had it’s own loop points! This could lend itself to some really cool patterns. I guess i wasn’t considering the full breadth of the feature !
yes… it has everything the official Ansible firmware has, but with additional features I have added to Kria. The other features are outlined here: https://github.com/monome/ansible/pull/30
p.s. @Justmat i updated the .hex file with the fixes for the Arc apps.
I so want to update but can’t afford to lose my presets - i have complete songs in presets that i do gigs with. Ratcheting is a killer feature that i always wanted also…
yea i thought ratcheting might be the feature that would push some people over the edge. i’ve got a few more features in the works though…
hopefully we’ll get preset import/export one of these days… unfortunately serialization and i/o aren’t really something i’d be comfortable touching in C
!
womp womp womp lol