great q’s!
a: unfortunately not at this point but would love to get there in the future. only way to undo is to re-record. there are two ways to cancel out automation for individual items - 1 - touch and hold the automated cloud / param / sound and the automation record button turns into “delete automation” 2 - arm the automation button and tap the item you want to clear. unarm and the automation is gone (any time the system detects less than 1 automation “frames” have been recorded, it clears out the automation frame). oops… i lied. 3 ways - it’s also possible to clear all param automation for a single cloud by opening the cloud for editing (double tap), holding the center of the cloud so the automation button turns into delete, and pressing the delete automation button.
b - no limit! just limited by your system memory. the parameters, however, do instantly start looping as soon as you release. this was a change i made shortly after version 2 because i didn’t like the extra frames added to the automation in the time it took to movefrom param to automation button…
c - yep. totally asynchronous. HOWEVER, if you record a bunch of automation for one cloud, open that cloud for editing, and then double tap on the screen to duplicate the cloud, all of the automation is copied and in phase in the new cloud (including the phase of the ring mod and vibrato, which will remain in sync with the source cloud).
d - not currently, but this is also an area i hope to improve.
all of these q’s get right at a bunch of stuff i hope to work on in the future around more options for fine tuning automation. adjusting automation phase, quantizing and trimming, adding retriggering options like trigger from ADSR or trigger per grain, individual automation speed controls, and “linked” automation - making one param adopt the automation assigned to another, etc… basically an “automation” menu is on the list down the road. at the moment everything is asynchronous and dependent on user timing. useful to a point but not as powerful as it could be.
one more tip - i snuck this in at the last min for this version, but haven’t shared it anywhere yet - if you have a bunch of clouds on screen, you can move through the automation queuing (when things turn white) to start recording all of their position/ ADSR automation (turning red) simultaneously if you hold down the automation button. this is how the Borderlands Presets > “BG - Scale Played” example was created…enabling the same recorded automation duration for all clouds on screen / keeping the chord progression from drifting each loop.