yeah, there is something super exciting about seeing Orca respond to a typed command. i only have 2 commands implemented so far (bank and preset select), partially because i tried using TT pattern for bank selection (especially when triggering TT with one of the Orca triggers) and it was so much fun i lost track of time!
so here is what i'm thinking for Orca command set:
ORCA.SCALE - select scale
ORCA.RANDOM - randomize current preset
ORCA.BANK - select bank
ORCA.PRESET - select preset
ORCA.RELOAD - reload preset (value of 8 reloads all presets in the current bank)
ORCA.ROTATES - rotate scales
ORCA.ROTATEW - rotate track weights
ORCA.MUTATE - mutate current preset
ORCA.GRESET - global reset
ORCA.CLOCK - advance specified track counter
then there are commands for individual tracks. instead of repeating each of these 4 times for each track what i'm planning to do is have one command for each parameter which will apply to the currently selected track, and there will be a command to select current track.
ORCA.TRACK - select current track
ORCA.DIVISOR - set the divisor
ORCA.PHASE - set phase
ORCA.RESET - reset the current track
ORCA.WEIGHT - set the weight
ORCA.MUTE - mute or unmute trigger
this does mean you might need to use 2 commands to set a parameter:
II ORCA.TRACK 0
II ORCA.DIVISOR 5
but i actually like this because then you can do interesting things like using trigger scripts to change parameters but have something else select the current track (like M script going through the pattern).
it's worth noting that if you change presets via TT the change takes place immediately to allow for tight sync (when you change presets using grid the change happens on the next clock so you don't have abrupt changes).
one of most interesting things TT/Orca integration brings is individual clocks for each track. this should really open it up in the way that wasn't possible in Orca alone. i thought of how this should integrate with the master clock, one option would be to provide another command to stop track from following the master clock, but then it would be strange if you forget you did that and you can't figure out why some tracks don't move!
so instead tracks will follow BOTH the individual clocks and the master clock. this could actually make for some interesting results as well, especially if they are out of sync. but if you don't want them to follow the master track then just simply insert a dummy cable into the clock input so the master clock stops, and supply individual clocks for each track, and you can share the same clock between different tracks like this, for instance (don't remember if Loops can be used with remote commands?):
L 0 3 : II ORCA.CLOCK I