How to control patches of 2 keyboards independently

No need for this! You can save a single chain as snapshot:

It also works in Oram.

And you can use the load-merge snapshot option to load the chains from a snapshot (also single-chain snapshots) on top of the current chains:

And this is also available in Oram. Both options are old ones.

Regards,

1 Like

Thanks for the reminder of the export as snapshot feature!

But in this thread we are mixing very different subjects:

  • Saving / loading a chain to/from a snapshot

vs.

  • Saving / recalling ZS3s, restoring a single chain

These 2 subjects have little in common and serve very different purposes.
I fear mixing both discussions in the same thread will create confusion only.

If someone think these 2 subjects are related, or in some way, serve to common purposes, please read carefully the docs.

Regards

1 Like

Yes, of course Merge load and replace ChainS works.
But neither of them is the function I was looking for. It either replaces ALL chainS or just adds the chain to the existing project. → Resulting in Two Chains playing the same incoming Midi. This is not exacly what you want hapening in front of an audience. And Yes, the default Answer to that was: You don’t need to change Instruments chains live. Because thats not how we think you should make music. Ok.

As I explained a month ago, none of the loading options work for replacing a single chain.

…come-on.

These functions (loadi merge snapshots) are not thought for performance .ZS3s are.

Your snapshots should be ready to use when you are in stage. You want to focus in performance and no in creating chains.

You could use several snapshots in a gig, but they should be prepared before.

Loading snapshots will “cut” the sound, so this can’t be done in a continous session unless you use 2 zynthians.

For performing a continous session with a single zynthian , you should have everything prepared in a single snapshot and use ZS3 for fast changing presets and other adjustments.

Perhaps your workflow doesn’t fit this approach? We are open to improve :wink:

But i still don’t know what is the issue. Use the ZS3 restore options.

We will add config options for the defaults, but this is not a stopper. All the functionality is already there.

Regards

You seem to have missunderstanded the answer.
Of course you need to change instruments while performing. But you shouldn’t be creating/replacing or configuring chains. You should have all your chains and processors in place, ready to use, and then use the ZS3 mechanism for fast changes

Regards

can you explain a bit more about how each preset can send 5 program change messages? I’m assuming the dont send every message simultaneously? do they just send each PC message one after the other?

The FCB1010 (with original firmware) can be configured to send several MIDI messages when each pedal is pressed and/or released. It can send a salvo of Note on/off, (up to 2) CC & (up to 5) PC. I cannot imagine a scenario where 5 PC messages would be benficial to zynthian.

A single PC can trigger zynthian to select a ZS3. The ZS3 can be configured to recall the full state or part of the state of when it was saved. So you could change all the chain presets, parameter customisations, etc. by recalling ZS3-1 and you could recall just the preset for a single processor in ZS3-2.

So, despite the FCB1010 having the ability to stack up to 5 program change commands on a single pedal, if used for zynthian, you probably only to use one PC to select the desired ZS3 to change just the bits you want, from one processor in one chain, all the way to all processors in all chains. Ultra flexible recall of state changes with no discernable impact on audio. ZS3 are the friend of the performing musician.

1 Like

Yes, I must say I have not yet tested if multiple Program Changes would work. To answer your question, they are sent in succession, as defined from PG1…PG5.

It could indeed very well be that such rapid succession would lead to race conditions on the receiving device (Zynthian). Just wanted to point out that if you’d e.g. had a nice Rhodes on chain 1 in zs3#1, and a nice Dexed on chain 2 in zs3#2, but not both in the same, in theory, you could fire two Program Changes after another.

Of course, having a single zs3 with both is faster, and perfectly doable.