by CopperPhil » 09 Sep 2013, 15:33
Well.... I mean that with CopperLan you can bind any available MIDI ports on the network. The "MIDI source" can be for example:
- a USB MIDI in interface: in this case you have to use the CopperLan Manager (Edit tab, MIDI, MIDI to CP interface) to activate port managing by CopperLan, so the port related to your controller appears on the network
- a VMIDI port: useful if you want to send MIDI from a sequencer or a MIDI software controller
And the "MIDI target" can be for example:
- a USB MIDI out interface: in this case you have to use the CopperLan Manager (Edit tab, MIDI, CP to MIDI interface) to activate port managing by CopperLan, so the port related to your interface appears on the network
- a VMIDI port: useful if you want to send MIDI to a MIDI software
"MIDI source" and "MIDI target" can be located on different computers on the same LAN network! CopperLan is a LAN technology, not world wide web.
Finally CopperLan is able to manage any MIDI port present on the system, and offers virtual MIDI ports to allow existing MIDI software to send/receive MIDI data to/from any other port on the network.
So I don't know NodeJS, we have no experience in managing MIDI from such web technology. But if NodeJS is able to talk with standard MIDI ports (i.e. USB MIDI Controller or synth), it should be able to use the CopperLan's VMIDI ports too.