so something i’ve been thinking about…
i mentioned this idea in a thread a while back, about using the trilogy modules as “smart” teletype expanders, not just used as providing additional inputs/outputs but actually running tt scripts inside, so you use tt to write/edit scripts and then you have the ability to transfer a script into a trilogy module, which can then run it independently (but could still be controlled through tt if needed, perhaps via shared variables or something along those lines). so you could pre-program it and move it to a differnt case even, only connecting it to tt when you need to reprogram its function.
i misread the ansible description initially, thinking that it can switch between different applications from a teletype (which is not the case if i understand correctly) but it reminded me of this idea (and the fact that ansible uses the same processor as tt).
there is the immediately obvious use case for this, of course, being able to reprogram tetrology modules without re-flashing the firmware (and a variation of it, having the tetralogy modules run within the tt ecosystem but doing something that is complementary to what tt itself does, LFOs/envelopes etc but still controllable from tt scripts). but it’s also interesting to consider this if you think of teletype as the control center of your modular.
so not only you can have tt providing the logic for your patch, and serving as a preset manager, possibly initializing other modules (especially the ones that might require specific steps to get into a proper state), but it can also be a meta preset manager where it controls not just the state of other modules, but their function as well. essentially, you could use teletype to change your modular setup. from a script. imagine being able to switch between different applications (say, switching between some simplified version of ww and orca) with a foot controller…