1,185
edits
Changes
Jump to navigation
Jump to search
Line 120:
Line 120: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Zynthian UI User's Guide Appendix - Vangelis (view source)
Revision as of 12:30, 19 May 2026
, 19 Mayno edit summary
Each processor has parameters that may be controlled with zynthian knobs or mapped to MIDI CC messages. Processors may have presets that may be arranged in banks.
Each processor has parameters that may be controlled with zynthian knobs or mapped to MIDI CC messages. Processors may have presets that may be arranged in banks.
<br clear=all>
===Snapshots===
[[File:snapshot_structure.png|400px|right]]
A snapshot is the captured state of zynthian at the time of saving the snapshot. Snapshots are saved in a JSON file with ''.zss'' extension and can be loaded at any time, which effectively restores the state of the zynthian device when the snapshot was saved. Snapshots include:
* '''chains layout:''' configuration of each chain including its processors and how they are arranged and connected
* '''audio levels:''' (optional) physical audio interface settings
* '''sequencer:''' patterns & sequences
* '''MIDI settings:''' global MIDI settings, USB MIDI port names, etc.!!
* '''multitrack record settings:''' mixer strips armed for multitrack recording
* '''UI state:''' some user interface configuration relevant to the snapshot (most UI is configured globally)
* '''sub-snapshots (ZS3s):''' most other configuration ([[#Sub-snapshots: ZS3|see ZS3]])
Each time you overwrite an existing snapshot file, a backup copy is created. Backups can also be restored at any time, which can avoid much suffering. When you feel the panic, remember that zynthian stores the full ''save history'' for '''all''' snapshots!
<br clear=all>
{{NoteBox|Many zynthian users like to see snapshots as "zynthian project" files and it's not a a bad approach.}}
====Last state snapshot====
When zynthian starts, it always tries to restore the last state saved as this snapshot. It always tries to save the current state before performing some operations, like:
* power-off
* restart
* update
* clean all
* etc.
For convenience, the last state snapshot can also be saved or restored manually.
===Sub-snapshots: ZS3===
ZS3 means '''Z'''ynthian '''S'''ub-'''S'''nap'''S'''hot. A ZS3 is a partial state that is stored in memory and can be recalled very fast. ZS3s can easily be associated (learned) to MIDI Programs (program change events). Of course, all ZS3s are saved and restored with snapshots, including the default state of the snapshot when first loaded (ZS3-0).
Please bear in mind that in the case of USB-connected MIDI devices there are two settings configured in admin under "MIDI-USB mapped by port" that affect this functionality.
With mapped to port set the learnt settings will apply only to the specific USB Configuration in place at the time of learning. So if you add a USB hub to the rig the ZS3 sub-snapshots won't act.
Turning this off will allow control simply by the MIDI message only.
When in the ZS3 screen, you can save the current (sub)state to ZS3 by sending a Program Change from any MIDI controller.
BUT In order to be able to change ZS3 by Program Change, you have to tick the box at
'''Interface->MIDI-options->Program Change ZS3 (Program Change for SubSnapShots)'''
ZS3s include:
* '''chains configuration:''' for each chain, MIDI channel, note-range, transpose, etc.
* '''processors state:''' for each processor, bank, preset & parameter values
* '''mixer settings:''' for each mixer strip, fader, balance, mute, solo, etc.
* '''MIDI devices configuration:''' active / multitimbral mode, etc.
* '''MIDI & Audio routing:''' connections between chains
* '''MIDI learning:''' MIDI bindings to processor and mixer parameters
* '''global settings:''' some global settings that can be changed by ZS3, e.g. MIDI transpose (most global settings are not available to ZS3)
* '''active chain''': chain that was active when the ZS3 was saved
The key concept to understand how ZS3s work is noting that the '''chains layout is not stored in ZS3s'''. In other words, the chains layout is not modified when restoring ZS3s. You can't add/remove chains or processors by restoring ZS3s because this is a slow operation and ZS3s need to be restored very fast.
When loading a snapshot that contains ZS3s, all the chains and processors are created. Later, when recalling the ZS3s, the chains layout will remain the same. Although ZS3s can modify routing, splits, banks, presets, etc., the quantity of chains and processors will be unchanged.
{{NoteBox|For instance, if you are keyboardist that plays with several bands, you could have a snapshot for each band with ZS3s for each song.}}
<br clear=all>
<br clear=all>
<br clear=all>