Difference between revisions of "Zynthian file formats"
| Line 28: | Line 28: | ||
In combination with the “Single Layer” feature, it turns Zynthian in a “Stage-Beast”. You can prepare a snapshot for the full performance, and use zs3 for fast changing from a song to another, or inside the same song. | In combination with the “Single Layer” feature, it turns Zynthian in a “Stage-Beast”. You can prepare a snapshot for the full performance, and use zs3 for fast changing from a song to another, or inside the same song. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Revision as of 19:15, 10 February 2024
1 Zynthian File Formats
1.1 zss Snapshot File
This is the basic file format of the zynthian, termed the Snapshot. It holds an entire state of all chains of the machine that can be restored entirely. It will load all chains settings and more importantly load up the Engines, the sequencer, Audio Files and their status, so for instance, if a snapshot is stored containing a playing audio file it will restart playing when the snapshot is loaded and this includes starting up from Power off.. .
They are mostly textual but sequencer details are stored in a data forma. I did mention this once and got bitten so I've left the subject. There are facilities to load specific components of a snapshot
1.2 zs3 Sub Snapshot File
Sub-snapshots:
From Jofe's original post
I use “zs3”, that means “Zynthian Sub SnapShot”. The idea behind this feature is to have a fast preset-change mechanism, easily mapable to MIDI Program Change events.
Every zs3 includes:
Layer ID Bank Preset Controller values As you can see, it has sense in a SnapShot context, where a set of layers are defined. Zs3 changing is very fast, as no engine must be started.
In combination with the “Single Layer” feature, it turns Zynthian in a “Stage-Beast”. You can prepare a snapshot for the full performance, and use zs3 for fast changing from a song to another, or inside the same song.