@hypnosapien, a fantastic idea, thank you!! that’s sorta like how the rené handles these types of patterns, which seems like a good standard for snake movement 
@swhic – sorry to hear about the trouble!! yes, i’ve seen some very random times where this happens. it just seems that the clock in charge of one of the arps quits out. it’s not something i can reproduce reliably (and is only something i’ve run into a handful of times), so i added a manual reset under params > arp (grid only!) > arp reset (k3). if you ever run into trouble where arp pads are unresponsive, please try this function?
i honestly don’t know what to make of the other issue re: patterns clearing and then pads not being responsive…if anybody can create a reliable repro case, that’d be super helpful
. maybe i’ll just add a total pattern reboot option to the params, the same as the arp. if it happens again, this will provide good information:
- do you have any meta patterns running?
- is this on distro or free? if distro, how many bars?
- do you have quantization turned on in the params?
- does the bank’s pattern screen show any indication that a new pattern was playing or being recorded?
- does k1+k3 on the first line of the bank’s pattern screen clear things when the grid gesture doesn’t?
also, maybe this it: you can get into weird zones if you try to record a pattern while playing arps at the same time. this is because the script won’t take your arps into consideration when it plays back the recorded pattern, so it has a little bit of logic to cancel conflicting processes. i was able to make some weirdness happen if i tried to arp while pattern recording + vise versa, so this might be what’s happening – it’d actually fully explain @SPIKE’s issue the other day, because the cancellation process changes the distro amount, because it’s stopping the recording (and cheat codes assumes the recording being stopped means that should be the new length rather than the originally entered value because rules are meant to be broken). hmmmmm. this is a wild case! 
sounds like you got the overdub bit sorted! and you’re right that local alt + focus doesn’t do what global ALT + focus does – this was a choice, for some reason, but i’ll examine it next coding session! thank you!!