2,705
edits
Changes
Jump to navigation
Jump to search
Line 1:
Line 1: + − [[File:zynthian_ui_workflow_1.png|400px|thumb]] − [[File:zynthian_ui_workflow_2.png|400px|thumb]] − + − + − Currently there are two main screen-types (screen-layouts):+ − + − + − + − + − + − + − + − Actions for each knob and click-type are context dependent. Generally, the SELECT knob is used to navigate and a short click on it will select an item on a "Selector Screen". Inside a "Controller Screen", short clicks can be used to rotate between layers (LAYER knob) or between controller pages (SELECT knob). "Bold-clicks" are intended as shortcuts for jumping to some specific screens. Clicking the BACK knob generally jumps to the previous screen in the workflow sequence.+ − + − + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + − + − + + + + + + + + − + − + − + + + Line 49:
Line 110: − + Line 62:
Line 123: − + Line 95:
Line 156: − + Line 102:
Line 163: − + − + Line 115:
Line 176: − + − + Line 167:
Line 228: − + − + + + − + − + − + − + − + Line 189:
Line 252: + Line 205:
Line 269: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Line 223:
Line 331: − + − + + − + − + − + Line 238:
Line 347: − + + + − + − + − + − + − + − + − + − + Line 276:
Line 387: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Zynthian UI User Guide (oldstable-2109) (view source)
Revision as of 11:43, 17 July 2019
, 11:43, 17 July 2019no edit summary
=General Concepts=
=General Concepts=
[[File:zynthian_controllers.png|430px|right]]
[[File:zynthian_controllers.png|430px|right]]
The Zynthian UI is displayed on a touch display and controlled by 4 rotary-encoders with switches (push).
The Zynthian UI is displayed on a touch display and controlled by 4 knobs (rotary-encoders with push-switches).
The encoders/switch knobs are used to navigate between the different screens/menus, select options and change the instrument parameters, acting as MIDI/OSC controllers. You can emulate the knobs behaviour using the touch-display, but it's sub-optimal and accessing some features could be tricky.
The knobs are used to navigate between the different screens/menus, select options and change the instrument parameters, acting as MIDI/OSC controllers. You can emulate the knob's behaviour using the touch-display, but it's sub-optimal and accessing some features could be tricky.
There are two main screen layout types:
* '''Selector Screen''': a list of items that you can scroll and select with the SELECT (4) knob
* '''Selector Screen''': a list of items that you can scroll and select with the SELECT (4) knob
* '''Controller Screen''': In the corners, 4 control widgets (one for each knob), with label and value indicator (graphic and numeric). In the middle, a list of controller maps which you can use to change or rotate using the SELECT (4) knob.
* '''Controller Screen''': In the corners, 4 control widgets (one for each knob), with label and value indicator (graphic and numeric). In the middle, a list of controller maps which you can use to change or rotate using the SELECT (4) knob.
Almost every Zynthian UI screen fits in one of these 2 types, however, other screen-types does exist:
Almost every Zynthian UI screen is one of these 2 types, however, other screen-types do exist:
* '''Confirmation Screen''': It will ask you to confirm some operation.
* '''Confirmation Screen''': It will ask you to confirm some operation.
* '''XY Controller Screen''': It allows to modify 2 parameters at once using the touch interface.
* '''XY Controller Screen''': It allows to modify 2 parameters at once using the touch interface.
* '''Info Screen''': It display info about some operation, like "Update Software", or "Network Info"
* '''Info Screen''': It displays info about an operation, like "Update Software", or "Network Info"
* '''Sequencer''': It's a planned feature not implemented yet ;-)
* '''Sequencer''': It's a planned feature, not implemented yet ;-)
There are 3 types of clicks (push) that can be performed, depending on how long you hold down the knob (or push on the touch-display):
There are 3 types of clicks (push-switch actions) that can be performed, depending on how long you hold down the knob (or hold your finger on the touch-display):
* '''short:''' less than 0.3 seconds
* '''short click:''' less than 0.3 seconds
* '''bold:''' between 0.3 and 2 seconds
* '''bold click:''' between 0.3 and 2 seconds
* '''long:''' more than 2 seconds
* '''long click:''' more than 2 seconds
Click actions for each knob are context dependent. Generally, the SELECT knob is used to navigate and a short click on it will select an item on a "Selector Screen". Inside a "Controller Screen", short clicks can be used to rotate between layers (LAYER knob) or between controller pages (SELECT knob). "Bold-clicks" are intended as shortcuts for jumping to some specific screens. Clicking the BACK knob generally jumps to the previous screen in the workflow sequence.
Most of actions depends on context (the current screen), but there are some actions that are global and will work from any screen:
Most of the actions depend of context (current screen), but there are some actions that are global and will work from any screen:
* '''long-back''': go to the admin menu
* '''long-back''': go to the admin menu
* '''long-select''': power off
* '''long-select''': power off
Snapshot actions are also global an will work from any point in the workflow. If you click SNAPSHOT (3) once, you get the Load Snapshot menu, another click and you will be in the Save Snapshot menu. If you bold-click SNAPSHOT then you will go directly to the Save Snapshot screen. The Snapshot screen have 2 levels: bank selection (directory) and snapshot (file). These actions are better explained below.
Snapshot actions are almost global and will work from any point of the workflow. If you short-click SNAPSHOT (3) once, you get the Load Snapshot menu, another short-click and you will be in the Save Snapshot menu. If you bold-click SNAPSHOT then you will go directly to the Save Snapshot screen. When accessing snapshots from Control-Screen context, bold-clicks must be used instead of short clicks and direct access to Save Snapshot menu is not available. These actions are better explained below.
=The Status Area=
<br clear=all>
[[File:zynthian_status_area.png|400px|right]]
On the top-right corner there is a small area where some useful information is displayed in real time:
* Audio Peak-meter or CPU-load => 1 or 2 small horizontal bars on the top right.
* MIDI-IN => Blue '''M''' flag
* Xrun => Red '''warning''' flag
* Under-voltage => Red '''ray''' flag
* Over-temperature => Red '''thermometer''' flag
* Recording Audio => Red '''circle''' flag
* Playing Audio => Green '''play''' flag
By default, Audio Peak-meter is shown. The meter covers the range -50dBFS to 0dBFS, i.e. maximum permissible level at full scale (far right) down to 50dB below that at far left:
* The green segment covers the range -50dBFS to -10dBFS.
* The yellow segment covers the range -10dBFS to -3dBFS.
* The red segment covers the range -3dBFS to 0dBFS.
There are independent meters for left and right channels which monitor the system output, i.e. the mix of audio that feeds the Zynthian output. Level decays with a logarithmic rule, taking one second to decay to -200dBFS so will decay to -50dBFS (the displayed range) in about quarter of a second. Peaks are displayed instantly, i.e. the attack of the meter is immediate(*). The peak hold bar remains for two seconds or until a higher peak is reached.
(*) Meter is updated 5 times per second so there could be 200 ms delay in peak being displayed.
Alternately, CPU-load bar can be enabled from webconf, replacing the Audio Peak-meter. The CPU-load bar shows the CPU usage as calculated by the Jack Audio Server:
This is a running average of the time it takes to execute a full process cycle for all clients as a percentage of the real time available per cycle determined by the buffer size and sample rate.
The blue M flag is shown when MIDI messages pass thru the MIDI router. Not all messages are detected. Only CC, Program Change and Note On/Off.
The red "warning" flag is shown when there are Xruns. You should hear clicks and pops too ;-)
When the red "ray" or "thermometer" flag is shown, your zynthian is working in a degraded state, with the CPU frequency capped to 600-800 MHz, trying to stabilize the system and avoid a system crash. You shouldn't see any of them and if you do so, you should consider looking for a better power source (under-voltage) or using a heat sink (over-temperature).
Finally, the red '''circle''' and '''play''' flags show the status of audio/MIDI capture: recording / playing
=Layers=
Layers are a key concept on Zynthian-UI: the first thing you do when you power-on your zynthian is create a layer ;-)
A layer is an '''Audio Processing Chain''', normally assigned to a MIDI channel, that can be composed of one or several Audio Processing Units. This units are chained by default, although you can customize the audio routing. The first unit in a layer is the '''root''' and determines the layer's type:
* '''Synth Layer''' => Receives MIDI note-events and generate audio output.
* '''FX Layer''' => Receives audio-input and generates audio-output.
* '''Generator Layer''' => Auto-generate audio output using some algorithm.
* '''Special Layer''' => MOD-UI pedalboard, Pure Data patch, etc.
The rest of units in a layer normally are FX units that process the audio coming-out from the first unit (root).
All units in a layer receive all the MIDI events coming from the assigned channel. Special layers don't have an assigned MIDI channel and receive all MIDI channels.
=The Zynthian UI Workflow=
=The Zynthian UI Workflow=
The next flowcharts show the different "screens" or "menus" and the way to reach each one using the 4 switches.
The following flowcharts show the different "screens" or "menus" and how to reach each one using the 4 switches.
It could be a good idea to print these 2 flowcharts and keep it near of your Zynthian Box until you memorize the workflow and the spirit of Zynthian UI got inside you ;-)
It would be a good idea to print these flowcharts and keep them near your Zynthian Box until you memorize the workflow and the spirit of the Zynthian UI gets inside you ;-)
<gallery mode="slideshow" widths="240" heights="320">
Image:zynthian_ui_workflow__main.svg|''[[commons:Main Sequence|Main Sequence]]''
Image:zynthian_ui_workflow__layer_options.svg|''[[commons:Layer Options|Layer Options]]''
Image:zynthian_ui_workflow__snapshots.svg|''[[commons:Snapshots|Snapshots]]''
Image:zynthian_ui_workflow__midi_learning.svg|''[[commons:MIDI Learning|MIDI Learning]]''
</gallery>
If you want to contribute improving these flowcharts, you can edit using the Google Documents Tools:
If you want to contribute to improving these flowcharts, you can edit them using the Google Documents Tools:
- [https://docs.google.com/drawings/d/1jmt3zrJjPkbqj3hpzCIwRgFIKxiX2UptebBA_GN8e5I/edit?usp=sharing Main sequence: zynthian_ui_workflow_1]
- [https://docs.google.com/drawings/d/1jmt3zrJjPkbqj3hpzCIwRgFIKxiX2UptebBA_GN8e5I Main sequence: zynthian_ui_workflow_main]
- [https://docs.google.com/drawings/d/1Um1HVCvvb4gZF_X-vcIN9cTxYIBRCtZ5oxniUdSTB3c/edit?usp=sharing Aux. Sequences: zynthian_ui_workflow_2]
- [https://docs.google.com/drawings/d/1C8kfovwXxuabl1u-UlrnHY8xzFFNiqiQWt1mmD5UXak Layer Options: zynthian_ui_workflow_layer_options]
- [https://docs.google.com/drawings/d/1Um1HVCvvb4gZF_X-vcIN9cTxYIBRCtZ5oxniUdSTB3c Snapshots: zynthian_ui_workflow_snapshots]
- [https://docs.google.com/drawings/d/1I0ArYVr3zGtzcSgOy19fHlIh8VF15rmsll9wZi-aXaI MIDI Learning: zynthian_ui_workflow_midi_learning]
<br clear=all>
<br clear=all>
=The UI Screens=
=The UI Screens=
==Layers==
==Layer List==
[[File:Zynthian_ui_new_layer.png|400px|right]]
[[File:Zynthian_ui_new_layer.png|400px|right]]
This is the first screen you should see when you power on your zynthian and no ''snapshots'' have been stored yet. Select '''New Synth Layer''' to get started.
This is the first screen you should see when you power on your zynthian and no ''snapshots'' have been stored yet. Select '''New Synth Layer''' to get started.
* '''PANIC! All Notes/Sounds Off''' => All notes and sounds are stopped abruptly by sending CC#123 and CC#120 to all channels.
* '''PANIC! All Notes/Sounds Off''' => All notes and sounds are stopped abruptly by sending CC#123 and CC#120 to all channels.
The last option, ''All Notes/Sounds Off'', can be triggered by bold clicking CTRL-1 (layer) from the layer screen (contextual action). You can trigger this actions from any point in the workflow by simply bold-clicking twice CTRL-1. Also, you can add a ''panic-button'' to your zynthian using the extra pins from the AllInOne circuit. You can [https://discourse.zynthian.org/t/extra-switches-sustain-pedal-panic-button-etc/1843 read more about this subject in the forum].
The last option, ''All Notes/Sounds Off'', can be triggered by bold clicking CTRL-1 (layer) from the layer screen (contextual action). You can trigger this actions from any point in the workflow by simply bold-clicking twice CTRL-1. Also, you can add a ''panic-button'' to your zynthian using the extra pins from the AllInOne circuit. [[Adding Extra Switches|Read this for a detailed explanation about how to add a panic button to your Zynthian]].
<br clear=all>
<br clear=all>
==Engine Selection==
==Engine Selection==
[[File:Zynthian_ui_engine_list.png|400px|right]]
[[File:Zynthian_ui_engine_list.png|400px|right]]
When you create a new layer, you are asked about which engine/plugin you want to use for it. A list of engines to choose from is displayed. They can be synthesizers, effects, generators or special engines, depending on the type of layer you are creating. When you clik on the list,
When you create a new layer, you are asked about which engine/plugin you want to use for it. A list of engines to choose from is displayed. They can be synthesizers, effects, generators or special engines, depending on the type of layer you are creating. When you click on the list,
the zynthian logo on the top-right will be animated while the engine is being started.
the zynthian logo on the top-right will be animated while the engine is being started.
* '''setBfree''': This engine can create 1, 2 or 3 layers assigned to the several MIDI channels starting at selected channel, each one corresponding to the upper, lower and pedals sections of the Hammond B3 emulation.
* '''setBfree''': This engine can create 1, 2 or 3 layers assigned to the several MIDI channels starting at selected channel, each one corresponding to the upper, lower and pedals sections of the Hammond B3 emulation.
* '''Pianoteq''': Only one layer is allowed to be created, assigned to the MIDI channel you choose.
* '''Pianoteq''': Only one layer is allowed to be created, assigned to the MIDI channel you choose.
* '''Aeolus''': NORMALLY 4 layers are created, assigned to different MIDI channels (1,2,3 & 4), each one corresponding to the 3 manuals + 1 pedal of the Aeolus default instrument definition. You can change the MIDI channel assignments from the Aeolus native UI. If you want to use a different instrument definition, you will have to tweak the engine's code a little bit. Ask in the forum ;-)
* '''Aeolus''': By default, 4 layers are created, assigned to different MIDI channels (1,2,3 & 4), each one corresponding to the 3 manuals + 1 pedal of the Aeolus default instrument definition. You can change the MIDI channel assignments from the Aeolus native UI. If you want to use a different instrument definition, you will have to tweak the engine's code a little bit. Ask in the forum ;-)
* '''MOD_UI''': Only one layer is allowed to be created and it's assigned to ALL MIDI channels. If you want to filter the messages by channel, you can do it within the MOD-UI patch. (There are plans for improving this behavior.)
* '''MOD-UI''': Only one layer is allowed to be created and it's assigned to ALL MIDI channels. If you want to filter the messages by channel, you can do it within the MOD-UI patch. (There are plans for improving this behavior.)
* '''PureData''': Only one layer is allowed to be created and it's assigned to ALL MIDI channels. If you want to filter the messages by channel, you can do it within the PD patch. (There are plans for improving this behavior.)
* '''PureData''': Only one layer is allowed to be created and it's assigned to ALL MIDI channels. If you want to filter the messages by channel, you can do it within the PD patch. (There are plans for improving this behavior.)
* After you have selected the engine for a new layer. Only free channels are listed.
* After you have selected the engine for a new layer. Only free channels are listed.
* When you change the assigned MIDI channel from the Layer Options.
* When you change the assigned MIDI channel from the Layer Options. Only free channels are listed.
* When you clone a layer from the Layer Options
* When you clone a layer from the Layer Options.
<br clear=all>
<br clear=all>
<br clear=all>
<br clear=all>
==Load/Save Snapshot==
==Snapshots==
[[File:Zynthian_ui_snapshot_load.png|400px|right]]
[[File:Zynthian_ui_snapshot_load.png|400px|right]]
[[File:Zynthian_ui_snapshot_save.png|400px|right]]
[[File:Zynthian_ui_snapshot_save.png|400px|right]]
You can enter the ''Load Snapshot'' screen by clicking the snapshot switch (from control screen you have to use bold-click!). Another click and you will be in the ''Save Snapshot'' screen. You can also use bold-click to go directly to the Save Snapshot screen.
Snapshots are used for saving/restoring the status of Zynthian. A snapshot includes the full state, including layers, effects, parameter values, MIDI-learning, etc.
You can enter the ''Load Snapshot'' screen by clicking the snapshot switch. From control screen you have to use bold-click. A second click and you will be in the ''Save Snapshot'' screen. You can also use bold-click to go directly to the Save Snapshot screen (not from control screen!).
Obviously, before loading any snapshot, you should save one, and for save a snapshot, you should create some layer. Zynthian UI will use numbers for naming the banks and snapshots. Later, using the webconf tool you can rename the snapshots to something more explicit.
Obviously, before loading any snapshot, you should save one, and for saving a snapshot, you should create some layers, etc. Zynthian UI will use numbers for naming the banks and snapshots. Later, using the webconf tool you can rename the snapshots to something more explicit.
====Snapshot Banks====
====Snapshot Banks====
By default, snapshots are stored as a single list and bank-stuff is not shown by Zynthian-UI. If you want to use banks for organizing your snapshots, you simply create a second bank using the webconf tool and the hidden bank functionality will be enabled.
By default, snapshots are stored as a single list and bank-related stuff is not shown by Zynthian-UI. If you want to use banks for organizing your snapshots, you simply create a second bank using the webconf tool and the hidden bank functionality will be enabled.
When using snapshot banks, if you want to go up one level, from snapshots to banks, you should use the ".." entry in the list. The Back button won't work here.
When using snapshot banks, if you want to go up one level (from snapshot list to bank list), you must use the ".." entry. The back button will close the snapshot screen.
====Default Snapshot====
====Default Snapshot====
You can save the status as "Default Snapshot". This "Default Snapshot" will be loaded automatically at startup. To delete it, you can use the webconf tool or do it from command line.
You can save the status as "Default Snapshot". This "Default Snapshot" will be loaded automatically at startup. To delete it, you can use the webconf tool or the command line.
====Restore Last State====
====Restore Last State====
If "Restore last state on startup" option is enabled on webconf, then state will be saved when poweroff (using long-click select or from Admin Menu) and restored on next boot. This option has priority over the "Default Snapshot".
If "Restore last state on startup" option is enabled on webconf (and it's enabled by default!), then state will be saved when poweroff (using long-click select or from Admin Menu) and restored on next boot. This option has priority over the "Default Snapshot".
<br clear=all>
<br clear=all>
==Admin Menu==
==Admin Menu==
[[File:Zynthian_ui_admin.png|400px|right]]
[[File:Zynthian_ui_admin.png|400px|right]]
[[File:Zynthian_ui_admin_02.png|400px|right]]
Pressing the Back knob, when you are in the Layer List screen, brings you to the Admin menu.
Pressing the Back knob, when you are in the Layer List screen, brings you to the Admin menu.
* Reboot
* Reboot
* Power Off
* Power Off
<br clear=all>
==Audio & MIDI Recording==
[[File:zynthian_audio_recorder_01.png|400px|right]]
[[File:zynthian_audio_recorder_02.png|400px|right]]
[[File:zynthian_audio_recorder_03.png|400px|right]]
[[File:zynthian_audio_recorder_04.png|400px|right]]
From the Admin menu you can access to the Audio & MIDI recording tools. These 2 simple tools allows you to record Audio & MIDI tracks easily, using the internal SD-card or an USB memory stick for storing the files.
'''WARNING!''' Using the internal SD card for storing the captured files increase the risk of corruption. You should avoid it by simply plugging an USB memory stick instead.
===Recording===
1. Press "Start Recording" for starting a new capture.
2. The red circle should appear in the top-right status area, indicating that a recording is going on.
3. Press "Stop Recording" for finishing the capture. The red circle will disappear and the recorded file will be added to the list. The filename is generated automatically and should be something like "jack_capture_01". The prefix "SDC" or "USB" indicates where the file is stored.
===Playing===
You can play files by simply selecting and clicking the file. The "play" symbol will be displayed in the UI status area.
For looping the file, turn on the "Loop Play" switch before playing.
'''NOTE:''' You can play a file in any moment. Recording and playing can take place simultaneously.
===Deleting===
A bold press will delete the selected file, but you will be asked to confirm the action.
===Managing recordings from your computer===
Audio & MIDI recordings can be managed from your computer by accessing the webconf's captures section. From this section you can:
* rename recordings
* delete recordings
* downloading recordings to your computer
* reproduce the audio recordings in your browser, if it supports wav file playing.
It is a good idea to rename your recordings so that they can be easily identified.
[[File:Zynthian_webconf_captures_01.png|600px|border|left]]
<br clear=all>
<br clear=all>
====MIDI CC====
====MIDI CC====
[[File:Zynthian_ui_midi_cc_learn_01.png|400px|right]]
You can map any parameter in the Zynthian UI to a CC knob/slider on your external MIDI controller. ''(I intend to extend this feature to other MIDI messages, but currently only CC messages are supported. Until then, MIDI-filter rules can be used instead.)''
[[File:Zynthian_ui_midi_cc_learn_02.png|400px|right]]
You can map any parameter in the Zynthian UI to a CC knob/slider on your external MIDI controller. I intend to extend this feature to other MIDI messages, but currently only CC messages are supported. Until then, MIDI-filter rules can be used instead.
Learning a MIDI-CC is quite easy:
Learning a MIDI-CC is quite easy:
1. From the control screen, you click the snapshot button. You will be in CC MIDI-learn screen. It’s identical to the Control screen except that all the controllers have a tiny yellow “???” in the bottom.
'''1.''' From the control screen, you click the snapshot button. You will be in CC MIDI-learn screen. It’s identical to the Control screen except that all the controllers have a tiny yellow “???” in the bottom.
2. Move a zynthian controller. Its tiny “???” will change to green while the other 3 will go back to normal state.
'''2.''' Move a zynthian controller. Its tiny “???” will change to green while the other 3 will go back to normal state.
3. Finally, move a knob/fader in your MIDI keyboard/controller and the binding is done. The new CC number should appear in the bottom of the learned controller, replacing the tiny "???".
'''3.''' Finally, move a knob/fader in your MIDI keyboard/controller and the binding is done. The new CC number should appear in the bottom of the learned controller, replacing the tiny "???".
Of course, MIDI-learning configuration, including CC mappings, is stored and restored with snapshots.
Of course, MIDI-learning configuration, including CC mappings, is stored and restored with snapshots.
'''Technical Note:''' MIDI-CC learning works with all the engines. It uses the engine’s native MIDI-learning capabilities when available. Zynthian’s MIDI-filter mappings are used for the rest. To be more explicit, native MIDI-learning is used for MOD-UI and ZynAddSubFX OSC parameters. All the other parameters are managed by Zynthian’s MIDI-filter mapping.
'''Technical Note:''' MIDI-CC learning works with all the engines. It uses the engine’s native MIDI-learning capabilities when available. Zynthian’s MIDI-filter mappings are used for the rest. To be more explicit, native MIDI-learning is used for MOD-UI and ZynAddSubFX OSC parameters. All the other parameters are managed by Zynthian’s MIDI-filter mapping.
====MIDI Program Change====obscenely
<br clear=all>
====MIDI Program Change====
[[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.
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.
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, you click the snapshot button '''twice'''. You will see the current list of ZS3s and a message: “Waiting for Program Change…”
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.
'''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.
After that, you can recall any stored ZS3 by simply pushing the same PC button again. The memory-stored zs3s will be saved with your snapshot and restored when it’s loaded again.
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:
Every zs3 includes:
Layer ID
- Layer ID
Bank
- Bank
Preset
- Preset
Controller values
- 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.
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.
<br clear=all>
====MIDI-CC Learning with touch interface====
====MIDI-CC Learning with touch interface====
2. In the parameter/controller area, slide with your fingernail from '''right to left'''. The tiny number, indicating the current CC assignment, should disappear or change. If the parameter is an engine-specific controlled engine, the number will disappear. If the parameter is a hardcoded MIDI-mapped parameter, then the number will change.
2. In the parameter/controller area, slide with your fingernail from '''right to left'''. The tiny number, indicating the current CC assignment, should disappear or change. If the parameter is an engine-specific controlled engine, the number will disappear. If the parameter is a hardcoded MIDI-mapped parameter, then the number will change.
<br clear=all>
<br clear=all>
=CUIA: Callable UI Actions=
The Zynthian UI can be controlled remotely using a set of commands called CUIA: Callable UI Actions. These CUIA are available on several interfaces: Key Bindings, MIDI, OSC, etc.
==Key Bindings: Controlling the UI with a computer keyboard==
The user interface may be driven using a USB keyboard, e.g. QWERTY, Dvorak, etc.
{| class="wikitable"
|-
!Key
!Modifier
!Function
|-
|Enter||None||SELECT
|-
|Enter||Shift||Bold SELECT
|-
|Enter||Ctrl||Long SELECT
|-
|Backspace||None||BACK
|-
|Backspace||Shift||Bold BACK
|-
|Backspace||Ctrl||Long BACK
|-
|Escape||None||BACK
|-
|Escape||Shift||Bold BACK
|-
|Escape||Ctrl||Long BACK
|-
|L||None||LAYER
|-
|L||Shift||Bold LAYER
|-
|L||Ctrl||Long LAYER
|-
|S||None||SNAPSHOT
|-
|S||Shift||Bold SNAPSHOT
|-
|S||Ctrl||Long SNAPSHOT
|-
|R||None||Start audio Record
|-
|R||Shift||Stop audio Record
|-
|M||None||Start MIDI Record
|-
|M||Shift||Stop MIDI Record
|-
|M||Ctrl||Reload MIDI Config
|-
|Space||None||All Notes Off
|-
|Space||Shift||All Sounds Off
|-
|Space||Ctrl||All off
|-
|Insert||None||Restart UI
|-
|Insert||Shift||Reboot
|-
|Insert||Ctrl||Power Off
|-
|Up||None||Listbox Up
|-
|Down||None||Listbox Down
|-
|Left||None||BACK
|-
|Right||None||SELECT
|}
==Controlling the UI with MIDI messages==
These actions are available using MIDI messages on the Master Channel (default 16, but configurable with the webconf tool), specifically, note-on messages (0x9) are used so you can use a MIDI keyboard for controlling the Zynthian UI. For instance, to Power Off the zynthian, you send this message:
0x9F ( Channel 16 Note ON)
0x00 ( Note code for POWER_OFF as below )
0x00 (Velocity/parameter)
or play the A-3 key, if your keyboard have it ;-)
This is the full list:
"0": "POWER_OFF",
"1": "REBOOT",
"2": "RESTART_UI",
"3": "RELOAD_MIDI_CONFIG",
"10": "ALL_NOTES_OFF",
"11": "ALL_SOUNDS_OFF",
"12": "ALL_OFF",
"51": "SELECT", D#3/Eb3
"52": "SELECT_DOWN", E3
"53": "SELECT_UP", F3
"64": "SWITCH_BACK_SHORT", E4
"63": "SWITCH_BACK_BOLD", D#4/Eb4
"62": "SWITCH_BACK_LONG", D4
"65": "SWITCH_SELECT_SHORT", F4
"66": "SWITCH_SELECT_BOLD", F#4/Gb4
"67": "SWITCH_SELECT_LONG", G4
"60": "SWITCH_LAYER_SHORT", C4
"61": "SWITCH_LAYER_BOLD", C#4/Db4
"59": "SWITCH_LAYER_LONG", B4
"71": "SWITCH_SNAPSHOT_SHORT", B5
"72": "SWITCH_SNAPSHOT_BOLD", C5
"73": "SWITCH_SNAPSHOT_LONG" C#5/Db5
[[File:2Oct_Keyboard_CUIA.png|600px|Keyboard]]