Automation possibilities

Hello there !

I m trying to setup my Zynthian for gigs (funk / rock covers), I want to modify the chains, live, a bit like subsnapshot, but specific to a subsnapshot (a kind of sub sub-subsnapshot !)

For instance in one subsnapshot I d want that a switch or a CC alters setBfree drawbars settings, in another subsnapshot, this CC or switch would change the pianoteq preset

I think there is nothing like this but I could make a kind of midi chain that traps control events and change them in various OSC commands.

What do you think ? Do you see something already existing or do I need to start from scratch :sweat_smile:?

It sounds like you are describing zynthian’s ZS3 recall options where you can limit what is recalled for a ZS3. Bold press the ZS3 and select the option to enter this view.

Zs3 snapshot are great but can’t be used live : they stop all engines and can take 10 seconds to load everything.

Sub-snapshot are great ans I use it, quick and allow you to setup a track, but when I’m performing a song, I sometimes need to change a part of a split, or raise some drawbars, etc.

The difference between the two was specifically designed around these two use cases.

Snapshot (ZSS) is designed to load all the engines and components and will as a result always take a length of time. An aproach recognisable to anyone who had a floppy based sampler keyboard like the Ensoniq EPS.

Sub snapshots (ZS3) are designed to allow instant parameter change within an existing snapshot.

They are really fast unlike patch change buttons on some devices that can take a second or two to do their thing.

It’s a mechansism to address the basic hardware limitations of the zynth & by extension the Pi.

I have had some success with engines like fluidsynth that don’t seem to be too worried about several open instances so I had 5 chains of flidsynth in the snapshot(ZSS) and I use subsnapshots (ZS3) to select the sounds by modifying the mixer.
Makes for some rather lovely sound generation.

I can’t remember where the 3 in the file extension came from.

Carefull with your words… ZS3 is SubSnapShot. These are the fast load workflow. Snapshots are the slow loading workflow.

today I have a snapshot with all relevant engines for one gig/band.

I have subsnapshot for each song, but now I need, within a song to adjust the settings. I could do another subsnapshot, of course. But what I would like is to trigger via a CC or a switch a kind of « the next settings for this song » (because it would always be the same CC/switch)