Q&A MIDI
How do I include my MIDI setup into a CopperLan network?
The CopperLan Manager installed on a computer is offering a bridge to MIDI applications and existing physical MIDI interfaces. The translation is transparent so that linking MIDI to MIDI via CopperLan works as if it were a direct connection.
For setups without computer, there are two options:
For setups without computer, there are two options:
-
CopperLan equipment may sport MIDI connections, allowing MIDI devices to be handled by the CopperLan network
There might be dedicated CopperLan-MIDI interface boxes, with Ethernet (or USB, Firewire, etc) on one side and one or more sets of MIDI DIN connectors on the other side.
May I still use my MIDI software?
Yes, of course; CopperLan is conceived to communicate with MIDI applications. The CopperLan service installed on a computer gives you a set of four virtual MIDI ports.
-
The data generated by MIDI applications, albeit restricted in resolution and scope, will play just fine on CopperLan target applications and equipment.
Data issued from CopperLan applications will as well play on MIDI applications, however sometimes truncated subject to the boundaries inherent in the MIDI protocol.
When used as a simple bridge, CopperLan allows MIDI applications to communicate amongst them, even when located in different computers.
How do I route MIDI through CopperLan?
In CopperLan, an incoming MIDI flow is split into its 16 channels, plus a 17th flow for clock and clock related messages, and a 18th flow for the remaining non-channel messages.
Each of these 18 MIDI sub-flow becomes a CopperLan flow that can be routed to one or more targets.
Each target can be a CopperLan destination including those that are re-translating the flow in the MIDI format. This MIDI flow ultimately reaches computer-based MIDI applications or physical MIDI connectors (via MIDI interfaces).
It is allowed to send any number of flows to any target, which in the case of MIDI targets implicitly offers a MIDI remapping and merging capability.
Clock flows can similarly be sent anywhere, but in the case of a MIDI target, no more than a single clock flow is accepted for any given output. This MIDI limitation does not apply to CopperLan targets as they are able to sort out multiple clock from multiple sources.
Each of these 18 MIDI sub-flow becomes a CopperLan flow that can be routed to one or more targets.
Each target can be a CopperLan destination including those that are re-translating the flow in the MIDI format. This MIDI flow ultimately reaches computer-based MIDI applications or physical MIDI connectors (via MIDI interfaces).
It is allowed to send any number of flows to any target, which in the case of MIDI targets implicitly offers a MIDI remapping and merging capability.
Clock flows can similarly be sent anywhere, but in the case of a MIDI target, no more than a single clock flow is accepted for any given output. This MIDI limitation does not apply to CopperLan targets as they are able to sort out multiple clock from multiple sources.
Is there any way I can upgrade or retrofit my MIDI equipment to CopperLan?
There is a difference between "talking CopperLan" and "talking with CopperLan".
Unless having its firmware being rewritten specifically for CopperLan, the MIDI equipment cannot talk CopperLan.
To connect MIDI products to the CopperLan network, there are a few options:
Unless having its firmware being rewritten specifically for CopperLan, the MIDI equipment cannot talk CopperLan.
To connect MIDI products to the CopperLan network, there are a few options:
-
existing MIDI/computer interfaces (e.g. MIDI-USB) which, once connected to the CopperLan Service in the computer, offer a complete interaction between CopperLan and MIDI.
dedicated MIDI/CopperLan interfaces - these can be dedicated boxes or retrofit modules with Ethernet or other connectivity.
CopperLan products that integrate a MIDI connectivity for the purpose of easing the integration of existing MIDI products.
Information not found? Send us your question!