Being USB2.0, class compliant...would it also function with the plethora of USB based controllers out there?
No, this is a USB client providing dual MIDI ports, not a Host...
This is basically to pass through messages from an iOS app to CL....it wont enable learning of iOS parameters or USB controller functionality...that needs to be embedded in the sources operating system I'd guess using the SDK.
Indeed, it is only providing a MIDI connection through physical network. But this is by design compatible with the numerous MIDI applications without needing to modify them to be CopperLan compliant. Still the MIDI limitations, but very low latency compared to WIFI, and long distance capability (thanks to Ethernet) compared to usual wired MIDI.
I would have though the CL route would be make it easier to support more third parties with less work overall..but then again I could be on the wrong track.
You are right, using CopperLan simplifies a lot the controller<->target relationship and ensures interoperability between gears whatever their brand. Several manufacturers are moving this way, they've understood their interest on this business. But the market is doing MIDI for so long, they just don't understand what CopperLan is. What we do is science-fiction for them. It's a very long process to make them thinking all of this is possible and very easy to set up
Nevertheless we're working on a new Smart Controller app for iOS, quite basic but it's an universal and auto-configurable controller for any CopperLan target. The CopperPlug is extended with a MIDI out bridge in addition to the VST/AU support. All of these would be released before the NAMM Show in January.
I just like to mention CP so they have a look and maybe consider the possibilities...especially the stand alone apps which miss out on the CP wrapper.
Thanks a lot for your support!
