factory modules do not react to midi, with the exception of the MIDI module.
the MIDI module is a MIDI → CV module, as you would have in eurorack.
indeed there is no visual feedback
yes, each MIDI module instance has its own state, so you can include many for more CC etc.
note: MIDI will pick up (only) the first USB midi device it finds if you have multiple connected.
for v/oct and gate, IF they are on the same midi channel then each MIDI module will look after a ‘voice’ - thats how polyphony can be implemented.
however, all of my modules support midi learn, completely separate from MIDI module.
this is implemented via a ‘window’ behind the main module window, accessed via LS+RS pressed together.
(Ive done videos on this, and I think Ive got information on the wiki)
the main advantage of using my midi learn is:
- simplicity, no extra patching
- multiple midi controller support
- visual feedback, parameters change as they receive midi (as you’d expect)
- bi-directional midi, for controllers that support it.
- range control ( * ), so 0…127 can be used over partial parameter range.
( * ) hmm, can’t remember if this is released yet 
ofc, main downside is… its only on my modules, not factory.
as I said, my midi learn is separate from MIDI module, as its internal to the module.
(e.g. its like having a eurorack module that natively supports midi)
ofc, you can use in conjunction…as MIDI sends CV out, so you can send to the CV input of my modules, as you would factory modules. - this can be useful if you want to modify the CV signal e.g. use MIDI CV + sequencer CV.
also my ATTN module can kind of be used the other way, e.g. you can use midi learn to assign midi CC to it, and then use its CV output in a similar way you might use the MIDI module.
ofc… thats the great thing about modular, simple mechanics can be used very creatively 
