I’m glad to receive your feedback, thank you very much for your reply, I don’t want to interfere with your own view, you’re the creator of the app 
For the outputs available, maybe some kind of checklist (on/off) In the params would give the user the ability to check the output(s) wanted, I don’t know.
For the snapshots triggered via midi, it’s just that the sequence I was trying to record earlier today became so complex in terms of polyrhythms and randomness that it was hard to trigger the snapshots In time on the grid and play some synths on top of it at the same time, that’s why I wanted to automate that a little bit. To be honest, I haven’t played with patterns yet, Only snapshots with various transposition but it might be what I was looking for. Regarding the snapshot chains I was thinking about one alt key on the grid + n press on a snapshot key (alt + 3 press on snapshot one and two press on another snapshot for example) by I totally forgot the patterns and I should use this option maybe 
Yes, this is very interesting. Somehow like the Tapographic Delay switches and morphs between maps, basically each time it receives a trigger it switches to the next sequence or selects a random one if it’s not empty. But will the second input of Crow ever be available or will they add some kind of reset input for the new clock system ?
About the momentary gates, it would rely on the new clock system but yeah it’s hard to implement while keeping the grid interface as clear as possible. The Animator is already great like it is, it’s just that I was looking for a way to stop it at the end of my recording haha. The transport should stop if Crow doesn’t receive a clock after N seconds but at the moment it does not, but that’s not related with Animator.
About the transposition page: well it’s really not absolutely needed, I can set the global transpose to a higher setting or set the basis frequency of the oscillators on the 301 to a higher level. I was just thinking about an immediate way to switch between octaves, musically speaking it’s quite interesting too, I’ve done that in a sequencer but it was not sequenced. But now that you speak about sequencing it… haha no let’s not over complicate things, since it’s going to the modular, this can be done on this side too 
Anyway, I’ll post the PR tomorrow for the 301 after some new tests. And if I find any other thing useful, I’ll share them. I’ve tried to respect your clean way of coding /general code structure/ as much as possible 