Hi,
Actually I don't know exactly what to answer since I'm not sure to understand your concern...
- Existing MIDI software (DAW, VST) is... MIDI... not CopperLan.
- CopperLan is able to bridge physical MIDI ports to the network
- It creates also a set of Virtual MIDI ports to allow legacy MIDI applications to get access to the network
- Since most of these MIDI applications do not create MIDI ports, they do not appear on the network... But if you are running Numerology on a Mac, it creates virtual MIDI ports that you can bridge to CopperLan.
So, from Ableton, you can send/receive MIDI to/from VMIDI1 port and patch each channel to anywhere on the network using the CopperLan Manager.
The CopperPlug wrapper is aimed to add CopperLan connectivity to existing VST plugins. A new version is currently under test. Plugins natively CopperLan would be available soon, hardware CopperLan controllers too.
About the "modules" in the CopperLan Manager, the Connect and Editor views are hierarchical, so you can't move blocks. On these views you can enter into a CopperLan application tree to perform some operation (making connection or edit parameters), and the logic of the workflow is going from left to right.
There is no MIDI feedback protection managed by CopperLan (impossible since CopperLan does far more than "just" sending MIDI from A to B, actually it can't guess the user's MIDI intents).