General
What are the network implications?
The CopperPlug system relies on CopperLan networking technology. CopperLan uses its own network protocol which is totally harmless to other networking protocols. You can continue using your network for mail, web browsing, printing and file exchange as usual.
Being non-IP based, CopperLan is secure against unwanted access from the Internet. If remote control via Internet is required, CopperLan can be passed through VPN as any other non-IP protocol. The various CopperLan networks connected through VPN will be fused as one.
What are the requirements to use CopperPlug?
- Any networked computer can be used as Host or Remote.
- Install the CopperPlug package (which includes the CopperLan service) on every computer involved.
- Use a 100MegaBaud, or better a 1GigaBaud Ethernet switch to link the computers
What if there is no configuration file available for my plug-ins?
When creating the CopperPlug versions of your plug-ins, the system also automatically creates a default definition file for each plug-in it encounters. The parameter definition is built according to a best-guess exploration of the plug-in capabilities. By default, the parameters will bear the names and ranges that the plug-in exposes. You can tweak the parameter definition with the provided parameter editor, and then upload the resulting file for the benefit of the community.
How to
How to make any standard VST plugin visible on the CopperLan network?
This is done by using a special VST plugin (a wrapper) instead of the original plugin.
This wrapper needs a CopperPlug Definition file (.cpd) in order to get the mapping between VST parameters and CopperLan messages.
- Copy the CopperPlug(CP).dll file at the same location than the plugin
- Rename the CopperPlug(CP).dll file to the name of the plugin with the "(CP)" suffix For example: plugin karnage.dll -> the CopperPlug(CP).dll is renamed karnage(CP).dll
- Copy the CopperPlug Definition file (with extension .cpd) at the same location. This file must have the same name than the original plugin. For example: plugin karnage.dll -> karnage.cpd definition file
- Load the plugin dll having "(CP)" suffix instead of the original plugin
- That's it, the plugin is now editable and controlable from the CopperLan network
How to make a CopperPlug Definition file
- Launch the CopperPlugMapper.exe program
- Go to settings to select your plugins directory
- Edit the automatically created cpd file
- The CopperPlug Definition file is a XML file.
Information not found? Send us your question!