deep glens@sean_ae @bobbyrethwish @Kama11
oh right duh that's way easier lol
@sean_ae @bobbyrethwish @Kama11
yeah [hover] is great.
tangent but:
i use it for a large portion of parameter automation via [mtr]. i think we were talking about this during a soundcheck in oct but i didn't quite explain it right.
basically: hover mouse over any UI object. hit R on the keyboard, record controller input on that param, hit R again, starts playback as looping. mtr -> dict saves it with pattr.
i sort of think of it like having an eno style tape loop system but for params.
Kama@trainvids @sean_ae @bobbyrethwish this sounds top. Gone silent but still following the thread. Any chance you’d share some more info on how you’re sending the modulation around? Gotta check out [hover], never used that before. Being able to just select a UI object and sort of record the automation for it seems like a really nice approach
@Kama11 @sean_ae @bobbyrethwish
@Kama11 for this specific case it's just really simple: an MTR abstraction that records UI input and then plays it back. so u can hook literally any UI thing up to it and make loops on the fly that are not looking at any "grid" or anything like that. that's on purpose for me, so that things drift and phase and make new combos. especially when you are not doing something like "filter cutoff" and something more like a seq transposition probability or etc...
@trainvids @sean_ae @bobbyrethwish thanks for the info! The recorded mod not being tied to a grid/downbeat seems powerful for creating intersections at points which would usually sync and having hands on control like that l feel lets you define those possible intersections quite accurately. So instead of shifting from say page 1 to page 2 in case of my sequencers, the switch could create a state between the pages depending on how the mod is set up. Cheers man!