Changes

Jump to navigation Jump to search
m
Line 116: Line 116:  
==Instrument Control screen==
 
==Instrument Control screen==
 
[[File:Zynthian_ui_instrument_control_01.png|400px|right]]
 
[[File:Zynthian_ui_instrument_control_01.png|400px|right]]
This screen is shown after you have chosen a preset. Your instrument is now playable and you can modify the parameters.
+
This screen is shown after you have chosen a preset. Your instrument is now enabled and playable and you can modify the parameters.
   −
Turning each of the 4 knobs change the values of the synth parameters displayed in the squares at the sides of the screen. You also can use the touch interface for changing the values. See below.
+
Turning any of the 4 knobs changes the values of the synth parameters displayed in the squares at the sides of the screen adjacent to each knob. You also can use the touch interface to change the values. See below.
 
<br clear=all>
 
<br clear=all>
    
[[File:Zynthian_ui_instrument_control_02.png|400px|right]]
 
[[File:Zynthian_ui_instrument_control_02.png|400px|right]]
The central list shows the different pages of parameters. You can navigate the page of parameters by clicking short-select to step one page.
+
The central list shows the different pages of parameters that you may alter. You can navigate the page of parameters by clicking short-Select to step by one page.
 
<br clear=all>
 
<br clear=all>
    
[[File:Zynthian_ui_instrument_control_03.png|400px|right]]
 
[[File:Zynthian_ui_instrument_control_03.png|400px|right]]
If the page list is long, you can "bold click" the select switch for navigating the list using the select knob.
+
If the page list is long, you can "bold click" the Select switch to navigate the list using the Select knob.
 
<br clear=all>
 
<br clear=all>
    
[[File:Zynthian_ui_xy_controller.png|400px|right]]
 
[[File:Zynthian_ui_xy_controller.png|400px|right]]
If you click 2 switches at once, then you will select these 2 parameters for XY-controlling using the touchscreen (ala kaospad).
+
If you click 2 switches at once, then you will select these 2 parameters for XY-control using the touchscreen (ala Kaoss Pad).
 
<br clear=all>
 
<br clear=all>
   −
You can press the layer switch to step over the layer list. If bold-press, the layer list will be shown.
+
You can press the Layer switch to step over the layer list. If you bold-press, the layer list will be shown.
   −
Press the back switch to return to previous screen. If bold-back, then you will go 2 screens backwards.
+
Press the Back switch to return to previous screen. If you press bold-Back, then you will go 2 screens backwards.
 
<br clear=all>
 
<br clear=all>
   Line 141: Line 141:  
[[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]]
Click the snapshot switch for entering the Load Snapshot screen. Another click and you will be in the Save Snapshot screen. You can also use bold-click for going directly to the Save Snapshot screen.
+
Click the Snapshot switch to enter the Load Snapshot screen. 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.
   −
Obviously, before loading any snapshot, you should save one. Snapshot are organized in banks, so if you don't have any bank, you should create one.
+
Obviously, before loading any snapshot, you should save one. Snapshots are organized in banks, so if you don't have any banks, you should create one.
Zynthian UI will use numbers for naming the banks and snapshots. Later, from the webconf tool you can rename the banks and snapshots to something more explicit.
+
Zynthian UI will use numbers for naming the banks and snapshots. Later, using the webconf tool you can rename the banks and snapshots to something more explicit.
   −
If you want to go up one level, from snapshots to banks, you should use the ".." entry in the list. Back button wont work here.
+
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.
    
===Default Snapshot===
 
===Default Snapshot===
You can save a "Default Snapshot". This snapshot will be loaded automatically at startup. For deleting it, you should use the webconf tool.
+
You can save a "Default Snapshot". This snapshot will be loaded automatically at startup. To delete it, you should use the webconf tool.
    
<br clear=all>
 
<br clear=all>
Line 155: Line 155:  
==Admin Menu==
 
==Admin Menu==
 
[[File:Zynthian_ui_admin.png|400px|right]]
 
[[File:Zynthian_ui_admin.png|400px|right]]
Pressing the Back knob, when you are in the Layer List screen, brings you to the Admin menu. The last item is how you safely power off the Zynthian without corrupting data files.
+
Pressing the Back knob, when you are in the Layer List screen, brings you to the Admin menu.  
 +
 
 +
The last item is how you safely power off the Zynthian without corrupting data files.
 +
 
 +
* Network Info - displays the IP address (ifconfig inet addr)
 +
* Start WIFI - Starts or Stops WIFI (toggle)
 +
* Start Audio Recording
 +
* Start TouchOSC bridge
 +
* Start Audio -> MIDI
 +
* Test MIDI - plays the test.mid file
 +
* Test Audio - plays the (long) test.mp3 file
 +
* Update Zynthian Software - downloads and installs the latest software
 +
* Update Zynthian Library - downloads the latest instruments
 +
* Restart GUI
 +
* Reboot
 +
* Power Off
 +
 
 
<br clear=all>
 
<br clear=all>
   Line 162: Line 178:  
You can navigate and control the Zynthian UI without knobs/encoders/switches at all, using only the touchscreen.
 
You can navigate and control the Zynthian UI without knobs/encoders/switches at all, using only the touchscreen.
   −
You can "emulate" the switches by tapping the controller widgets (squares in the 4 corners of a Controller screen). There are short, bold and long actions. Exactly the same workflow as with hardware knobs. The only screen that currently shows the 4 controller is the "Instrument Control" screen, so some features are only accessible from there. When the "back" widget is not available, you can go back by tapping the top bar.
+
You can "emulate" the switches by tapping the controller widgets (squares in the 4 corners of the screen). There are short, bold and long actions -- exactly the same workflow as with hardware knobs. The only screen that currently shows the 4 controllers is the "Instrument Control" screen, so some features are only accessible from there. When the "back" widget is not available, you can go back by tapping the top bar.
   −
You can change the values of the controllers by "sliding" over the widgets. This is the same as turning the knob. If you are using a mouse, the mouse wheel also modifies the parameter.  
+
You can change the values of the controllers by "sliding" over the widgets. (see the green arrow in the figure here) This is the same as turning the knob. If you are using a mouse, the mouse wheel will modify the parameter value.  
   −
When clicking (tapping/touching) the topbar, a "back" event is triggered. It's a quick & dirty fix and probably it will change in the future, but meanwhile it will enable you to fully control Zynthian using the touchscreen if you don't have knobs hardware.
+
When clicking (tapping/touching) the topbar, a "back" event is triggered. It's a quick & dirty fix and probably it will change in the future, but meanwhile it will enable you to fully control Zynthian using the touchscreen if you don't have knob hardware.
 
<br clear=all>
 
<br clear=all>
    
=Global MIDI-learning=
 
=Global MIDI-learning=
   −
It allows to easily bind any parameter from the Zynthian UI to any CC knob/slider from an external MIDI controller. I intend to extend the feature to other MIDI messages, but currently only CC messages are supported. Anyway, MIDI filter rules can handle these special cases, so it’s not an urgent task.
+
This allows you to easily connect any parameter in the Zynthian UI to any CC knob/slider on an external MIDI controller. ''(I intend to extend this feature to other MIDI messages, but currently only CC messages are supported.)'' Anyway, MIDI filter rules can handle any special cases, so it’s not an urgent task.
   −
It works with ALL the engines, using the engine’s native MIDI-learning when available (and convenient) or the Zynthian’s MIDI-learning mechanism, based in the MIDI filter. To be more explicit, native MIDI-learning is used for MOD-UI and for ZynAddSubFX OSC parameters. All the MIDI-mapped parameters are managed by the Zynthian’s MIDI-learning mechanism.
+
This works with ALL the engines, using the engine’s native MIDI-learning capability when available (and convenient) or the Zynthian’s MIDI-learning mechanism, within the MIDI filter. To be more explicit, native MIDI-learning is used for MOD-UI and ZynAddSubFX OSC parameters. All the other MIDI-mapped parameters are managed by the Zynthian’s MIDI-learning mechanism.
   −
You get on-screen feedback during the learning process. When you enable the MIDI-learning for a parameter, a small green text with the string "??" appears on the botton side of the controller/parameter area in the Zynthian UI. When the parameter is bond, the number of the linked CC is shown in the same place.
+
You get on-screen feedback during the learning process. When you enable MIDI-learning for a parameter, a small green text displaying "??" appears at the bottom of the controller/parameter area in the Zynthian UI. When the parameter is connected to a CC, the number of the assigned CC is shown in the same place.
    
The MIDI-learning configuration is stored in the snapshot.
 
The MIDI-learning configuration is stored in the snapshot.
   −
==How it works?==
+
==How to use MIDI Learning==
   −
First, you need a working touch interface in your display. If not, you could use a mouse ...
+
First, you need a working touch interface in your display. If you don't have a touchscreen, you could use a mouse ...
    
[[File:Zynthian_ui_midi_learning.png|400px|right]]
 
[[File:Zynthian_ui_midi_learning.png|400px|right]]
 
'''Learning:'''
 
'''Learning:'''
  1. In the "Instrument Control" screen, navigate the parameter screen list until having the parameter you want to learn.
+
  1. In the "Instrument Control" screen, navigate through the parameter screen list to get to the parameter you want to learn.
  2. On the parameter/controller area, slide with your nail from '''left to right'''. A green "??" should appear in the bottom side.
+
  2. In the parameter/controller area, slide with your fingernail from '''left to right'''. A green "??" should appear at the bottom.
  3. In your MIDI controller, move the desired knob/slider (or a CC-assigned pad).  The green "??" should be replaced by a tiny number, and the parameter should change when you move the knob/slider or push the pad. CC-assigned pads can be very useful for "boolean" parameters (i.e. on/off).   
+
  3. On your MIDI controller, move the desired knob/slider (or a CC-assigned pad).  The green "??" should be replaced by a tiny number, and the parameter should change when you move the knob/slider or push the pad. CC-assigned pads can be very useful for on/off parameters.   
 
<br clear=all>
 
<br clear=all>
    
[[File:Zynthian_ui_midi_unlearning.png|400px|right]]
 
[[File:Zynthian_ui_midi_unlearning.png|400px|right]]
 
'''Unlearning:'''
 
'''Unlearning:'''
  1. In the "Instrument Control" screen, navigate the parameter screen list until having the parameter you want to unlearn.
+
  1. In the "Instrument Control" screen, navigate through the parameter screen list until you get to the parameter you want to unlearn.
  2. On the parameter/controller area, slide with your nail from '''right to left'''. The tiny number, indicating the current CC bond, should disappear or change. If the parameter is an engine-specific controlled engine, the number will disappear. If the parameter is 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>
393

edits

Navigation menu