Line 291: |
Line 291: |
| <br clear=all> | | <br clear=all> |
| | | |
− | ====MIDI Program Change==== | + | ====MIDI Program Change: ZS3 (subsnapshots)==== |
| [[File:Zynthian_ui_midi_zs3_learn.png|400px|right]] | | [[File:Zynthian_ui_midi_zs3_learn.png|400px|right]] |
− | You can map "SubSnapshots" (ZS3) to MIDI programs. The idea behind this feature is to have a fast preset-change mechanism that can be used on stage. 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 between parts inside the same song. | + | A ZS3 (SubSnapShot) saves the state of the active layer. When recalled, this state is restored and the active layer is changed. |
| + | |
| + | Every ZS3 includes: |
| + | |
| + | - Layer ID |
| + | - Bank Name |
| + | - Preset Name |
| + | - Controller Values |
| + | |
| + | When a set of layers are created (i.e. loading a snapshot), ZS3 changing is very fast, as no engine have to be started. It take less than 1 second in most of cases. |
| + | |
| + | You can map "SubSnapShots" (ZS3) to MIDI programs. The idea behind this feature is to have a fast preset-change mechanism that can be used on stage. In combination with the “Single Active 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 between parts inside the same song. |
| | | |
| Learning a SubSnapShot is obscenely easy: | | Learning a SubSnapShot is obscenely easy: |
| | | |
− | '''1.''' From the control screen, you click the snapshot button '''twice'''. You will see the current list of ZS3s and a message: “Waiting for Program Change…” | + | '''1.''' From the Control screen, click the snapshot button '''twice'''. You will see the current list of ZS3s and a message: “Waiting for Program Change…” |
| + | |
| + | '''2.''' Push a “Program Change” button in your keyboard/controller and the ZS3 will be stored in memory, associated with the Program Number you pushed. |
| + | |
| + | After that, you can recall the stored ZS3 by pushing the same Program Change button again. Of course, stored ZS3s will be saved with your snapshot and restored on load. |
| | | |
− | '''2.''' Simply push a “Program Change” button in your keyboard/controller and the ZS3 will be stored in memory, associated with the Program number you send.
| + | You can update and delete stored ZS3s by bold-clicking on the list. An options menu will be shown. |
| | | |
− | After that, you can recall any stored ZS3 by simply pushing the same PC button again. Of course, the memory-stored zs3s will be saved with your snapshot and restored when loaded again.
| |
| | | |
− | Every zs3 includes:
| + | ZS3 bahavior depends of the "Single Active Layer" option: |
| | | |
− | - Layer ID
| + | * '''Single Active Layer Enabled''': ZS3 list shows all the ZS3s stored, no matter the layer. Recalling a ZS3 change the active layer, so the layer associated with the recalled ZS3 will receive the *ALL* the MIDI input. Only 127 ZS3s can be stored. |
− | - Bank
| + | * '''Single Active Layer Disabled''': ZS3 list shows only the ZS3 of the current active layer. Recalling a ZS3 change the active layer, but every layer receives MIDI input for its channel only. You can use several keyboards on different channels and store 127 ZS3s by MIDI channel. |
− | - 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 have to be started.
| |
| <br clear=all> | | <br clear=all> |
| | | |