Changes

Jump to navigation Jump to search
Line 4: Line 4:  
[[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 switches).
+
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 knob's 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.
   −
Currently there are two main screen-types (screen-layouts/pages):
+
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
Line 19: Line 19:  
* '''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 hold your finger 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
   −
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.
+
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 the actions depend 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 and 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=
 
=The Status Area=
Line 61: Line 61:     
Finally, the red '''R''' and '''>''' flags show the status of audio capture: recording/playing
 
Finally, the red '''R''' and '''>''' flags show the status of audio 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=
Line 85: Line 100:  
=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.
Line 138: Line 153:  
* '''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.)
 
   
 
   
Line 151: Line 166:     
* 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>

Navigation menu