you can control anything that is listed as a parameter for any single algorithm (double algorithms currently do not support i2c control) using the following ops:
EX.PARAM param value (alias EX.P)
this will set the specified parameter to the exact value provided. you can also get the current value for a parameter with this op.
EX.PV param value
is similar to the above, but it expects value to be in the 0…16384 range and it will scale it automatically to the range available for the specified parameter. this is handy to use if you’re mapping the knob or the CV input (or faderbank values), so you could do something like EX.PV param IN.
EX.CTRL controller value
this ops sets the specified i2c “controller” value - this is useful if instead of controlling parameters directly you want to use i2c to parameter mappings, especially if you already have i2c mappings set up for faderbank.
some parameters act as switches with actions triggered when a parameter changes from 0 to 1 (like augustus loop tap tempo, for instance). for this parameters you’ll want to do something like EX.P .. 1; EX.P .. 0
there are also algorithm specific parameters - they are either for things not available as parameters (like augustus loop pitch) or for things that would likely be used often, like looper ops. looper ops also can give you the current state for the mode / reverse / octave down, which are not available as parameters.
i definitely think there are some pretty amazing things possible with teletype integration!
