teletype support: probably not on first iteration, keeping the scope small for now to get the work started. but yeah eventually it should have its own remote ops.
this would be a good candidate for a remote op.
clock:
it does make sense to use one of the trigger inputs as a clock since ES already supports it (i wasn’t sure if clock support was added or not). how does it work with ES.CLOCK right now? does it ignore recorded timing completely, so essentially it just non destructively linearizes the current pattern?
i assume it doesn’t need an internal clock, so when nothing is connected into the clock input it’ll just use recorded timing.
if the first trigger input is used for clock, i think it makes sense to use the 2nd trigger input to trigger pattern play (or restart it if it’s already playing).
this could be something for next version, supporting different direction, with a corresponding button and a remote op.
it’ll round robin through available voices. if all 4 are currently playing it’ll steal the earliest. this will also apply if you’re playing over a recorded pattern. does this make sense?
yeah, something like this would increase the scope significantly, so i’ll leave it for somebody else. re: runes - the functionality they provide is important, but with polyphonic keyboard i’m not sure how would you distinguish between a rune and a chord being played. some functionality could be shifted to module buttons (prev/next pattern) or a modifier button could be used - how about using slew button for this?
