Well, I have some comments to post here :-)
mr chombee wrote:Great module. I just wish it also had some CV/gate inputs.
We have prototyped a lot of things related to high resolution capture/rendering, and of course a "CV/Gate to CopperLan" board. We used it to demonstrate a Theremin controlling an analog synth through Ethernet cable (shown at Ircam, Paris). Do not know if Alyseum is planning to make such box, it'll probably depend on the success of its first products ;-)
The product descriptions are bordering on too technical. So can this be used with say Silent Way, or is all it does convert MIDI to CV through some virtual MIDI port? Or is it something else entirely?
MIDI is translated to/from high resolution CopperLan messages. So it is possible to control CopperLan stuff from MIDI, and the opposite. CV devices are natively CopperLan, designed to handle high resolution/speed messages. So, controlling it from MIDI implies a 128 step resolution of course.
poladark wrote:... There doesn't seem to be a public document specifying the protocol - yet they claim that the CopperLAN protocol is "open". Not using IP seems like a serious disadvantage. How are you supposed to use this with existing network infrastructure? Can i use my enterprise class Cisco switches and routers with CopperLAN? What if i want to collaborate with a person downstairs or in a different office? The advantage of using Ethernet with CopperLAN is not so obvious if I'd have to design a physically separate network to use it. ...
The CopperLan protocol is quite complex, far far away from implementing MIDI. It is plug&play, zero config, it provide automatic synchronization between control panels and remote devices, full setup save/restore, human friendly (everything is named), etc... so we offer to developers a complete framework with an important abstraction layer to facilitate CopperLan application programming. All the network management is automatically handled by the framework, developers just have to concentrate on their business without having to understand how it works inside. But, yes, CopperLan is "open" to the manufacturers through a consortium. We have to ensure the perenity of CopperLan, even we disappear. We do not want to lock the market, we are working for a long time to be able to offer a new unified communication solution for MI & pro-audio/sound & lights & everything on the stage. It's a private initiative, we do not depend on big manufacturers but we work with them for years to ensure that we have THE solution for their future needs. CopperLan is based on today's technology and is designed to evoluate, following the technical innovations while offering retrofit compatibility (as we did with MIDI). It is definitively not something to "lock" people with an expensive solution. CopperLan is cheap for manufacturers (and free if you make freeware) and development cost is reduced thanks to the framework doing most of the job.
Not using IP is something we decided a few years ago. CopperLan, it is 10 years of R&D. We tried a lot of things before the current implementation. We tried of course IP communication. But we leave it in order to be able to offer a real plug&play/no config/high performance network. The CopperLan Protocol can coexist with any other protocol on an Ethernet cable (even pro-audio) and do not need specific Ethernet hardware. It is based on MAC address, so yes indeed it can't pass through routers as is. But the target scope of CopperLan is a LAN, not a WAN. However it is possible to pass through VPN connection (after having enabled the protocol), but latency is usually too high for real-time performance (music) while it's ok for command/control/maintenance operations.
So this is my first pack of (long) comments :-) Do not hesitate if you have any question about CopperLan, I'm here to give you answers ;-)