Store presets?

[Palli]

Hi everybody.

Is it possible to store and load diffent midi setups as presets?
And would it be possible to make those presets available to
all connected clients?

Thanks.

[CopperPhil]

Hello,

Well, you are asking if it is possible to recall a snapshot like a program change, do you?

The CopperLan Snapshot feature is aimed to store the settings of every CopperLan application on the network in addition to the connections. Storing and loading a Snapshot is done from the CopperLan Manager application... for the moment, because there is no other CopperLan application doing that yet. To role of the CopperLan Manager is to manage the network, making connections, changing parameters, handling snapshots... all of these manually, it was not designed to be automated.

So no, actually it is not possible to trig a Snapshot loading from elsewhere on the network. In order to do that, we should modify the application to expose the snapshot list over the network allowing other application to initiate a snapshot recall. Technically it is not so hard to implement in a CopperLan way. Any CopperLan application or hardware would be able to enumerate existing snapshot, store or recall it, even remotely change its name. But if you want to be able to to that from any MIDI source (keyboard/app...), it will be only possible through a blind Program Change! Easy to make MIDI things CopperLan, but the opposite is often impossible...

Finally, yes we can update the CopperLan Manager's Snapshot module to respond to "Program Change" coming from MIDI stuff, just to trig something like "load Snapshot number x", but:
- the MIDI device/software must be initially connected to the CopperLan Manager. So you need to establish a connection before being able to recall Snapshots restoring connections
- is it safe to recall a Snapshot from its index in the list? what if the list changes due to a new snapshot? a "Program Change" number might point to another Snapshot file than the former one (depending also on the list sort)...

So as you can see it is not so obvious because CopperLan was made to facilitate the user experience, using named things instead of numbers and providing full bidirectional remote control MIDI can't do...

But ok I will have a discussion about that with the development team. Meanwhile if other users around here are interested by this feature, let me know!

[Luc Henrion]

isn't this feature kind of dangerous? You could make a a snapshot calling a snapshot calling a snapshot... ad infinitum.

[Copperhead]

isn't this feature kind of dangerous? You could make a a snapshot calling a snapshot calling a snapshot... ad infinitum.

Such chaining is not inherent to CopperLan. The same could be done with any system where recalling a setup may itself recall a setup.
It never was a problem with MIDI since 1983; there's no reason why it would be different with CopperLan.

[xpander]

The Opcode Studio 5LX, the Axxess Mapper, the Sycologic Switcher..Vangelis probably went through them all. We need a device that can control a giant setup of VSTs and midi hardware (and hopefully CopperLan hardware) that is bulletproof and rock solid and not likely to become hopelessly obsolete because there will be no drivers for the next operating system. Alyseum AL-88 with memories, .. like a replicant?

A LOT of guys are very serious about getting a hold of something like that!...

Obsolete connectors, obsolete OS, no drivers, no source code.....