Expose I2C/Multi Poly Round Robin as a Mappable Source/Destination

[XORadmin]

Currently, there is a "Midi -> MOD" option on Modular track type.

In projects using only I2C/Multi track type, however, the velocity coming in from MIDI doesn't get routed through to the MOD outputs, but it would be nice to be able to make the Velocity go somewhere appropriate during live performance (as a pass-thru.)

I understand there are two reasons for this not to work:

1. There is no where in the I2C/Multi pattern to store the modulation values for each note.
2. The Destination in the track setup only specifies pitch and gate, for example CVGA, and not CVGA+MOD, so there's no instruction even of where to route a mod value to.

The obvious solution is that this could be handled through Mappings, except there's no way to keep track of where the I2C/Multi Poly round robin is currently pointing.

It seems like if the Round Robin were explicitly exposed in the mapping screen, and there were simply six internal track variables where the Velocity gets stored at the same time when any one of the six Destinations is written to, then a set of Mappings could be used to copy from these variables into the appropriate spots with a mapping like this, for example:

TRCK TRK1 VEL1 ----  >  CV PTCH MOD1
TRCK TRK1 VEL2 ----  >  CV PTCH MOD2
TRCK TRK1 VEL3 ----  >  CV PTCH MOD3
TRCK TKR1 VEL4 ----  >  CV PTCH MOD4

It is critical that VELx only get filled in when that particular destination is written to in round-robin, that way the mapping can send them to the corresponding outputs (whatever they are) that go along with the pitch and gate already set.

It might be helpful to also make TRCK TRK1 RR  expose the number of the last round robin destination, then we could also write to it to reset the round robin back to zero for instance.

Why not using a modular track for it then?
A I2C/Multi track doesn't know any deeper Midi information as every column can only store 1 information which is note on/off only. Midi is just one possible input channel.