228
edits
Changes
Jump to navigation
Jump to search
m
no edit summary
Line 104:
Line 104:
Use this screen to assign midi note values to control the Zynthian UI.+
+<br clear=all>+===VNC-UI===+This link opens a tab with the Zynthian UI, same as you would see with a directly connected display.
−===VNC-Engines===
−This link opens a tab with a desktop style GUI for and loaded engines (synths, effects etc.) that have a built-in UI.
−===Terminal===
−Access a terminal window for the OS directly from Webconf to debug, troubleshoot etc.
====Using MIDI controllers instead of Encoders====
−Using midi driven encoders instead of encoders bult-in to the Zynthian is a little bit confusing, and that’s conceptual rather than technical. A MIDI controller is normally a pot or an encoder pretending to be a potentiometer. Its value varies from 0 to 127. The problem with that is the Zynthian encoders work as proper encoders using up and down signals. To produce something that could control a list properly when you move to a specific screen after you’ve come from another page is rather complicated because most pots will simply send the maximum value but not repeatedly send if further turns are made.
−The next issue is handling the push button functions of the encoder and bold presses and long presses.+You can send CUIA commands to drive the GUI and that would allow you to drive the whole device from push buttons but it might be a lot of switches. +And you really can do an awful lot with a mouse! Really easy if you get a wireless(not Bluetooth) one it’s really intuitive once you learn the trick to do the back button.
−<br clear=all>
===Pianoteq===
===Pianoteq===
−Configure the Pianoteq plugin. Enable license, add instrument packs, etc.
+Pianoteq is a proprietary softsynth that uses physical modelling to simulate real (mainly stringed) instruments. Configure the Pianoteq plugin. Enable license, add instrument packs, etc.
Line 173:
Line 173:
Make fine tuning adjustments
Make fine tuning adjustments
<br clear=all>
<br clear=all>
+
====Midi Devices====
====Midi Devices====
−[[File:zynthian_webconf_midi_ports.png|600px|right]]
+[[File:Midi devices page webconf oram.png|600px|right]]
−This is an "advanced" option that allows to configure your hardware MIDI ports as INPUT/OUTPUT or for receiving MIDI feedback on controllers that support this feature (i.e. motorized faders).
+This page now provides a summary of your connected hardware MIDI INPUT/OUTPUT ports. For midi configuration refer to the admin menu of the Zynthian UI.
<br clear=all>
<br clear=all>
+
====Configure MIDI Filter/Router====
====Configure MIDI Filter/Router====
[[File:zynthian_webconf_midi_router.png|600px|right]]
[[File:zynthian_webconf_midi_router.png|600px|right]]
Line 182:
Line 184:
[[Configure_MIDI_Filter/Router|Read the MIDI Filter Rule Language documentation.]]
[[Configure_MIDI_Filter/Router|Read the MIDI Filter Rule Language documentation.]]
<br clear=all>
<br clear=all>
+
====Master Channel====
====Master Channel====
Allows setting a master midi channel to allow program change and bank change messages and master key actions.
Allows setting a master midi channel to allow program change and bank change messages and master key actions.
====Master Key Action====
====Master Key Action====
+Use this screen to assign midi note values to control the Zynthian UI.
−<br clear=all>
+====Using MIDI controllers instead of Encoders====
+Using midi driven encoders instead of encoders built-in to the Zynthian is a little bit confusing, and that’s conceptual rather than technical. A MIDI controller is normally a pot or an encoder pretending to be a potentiometer. Its value varies from 0 to 127. The problem with that is the Zynthian encoders work as proper encoders using up and down signals. To produce something that could control a list properly when you move to a specific screen after you’ve come from another page is rather complicated because most pots will simply send the maximum value but not repeatedly send if further turns are made.
+The next issue is handling the push button functions of the encoder and bold presses and long presses.
−You can send CUIA commands to drive the GUI and that would allow you to drive the whole device from push buttons but it might be a lot of switches.
−And you really can do an awful lot with a mouse! Really easy if you get a wireless(not Bluetooth) one it’s really intuitive once you learn the trick to do the back button.
−<br clear=all>
<br clear=all>
===MIDI Log===
===MIDI Log===
−[[File:MIDILog.png|600px|right]]
+[[File:Midi log webconf oram.png|600px|right|none]]
Displays all received MIDI messages. This page now provides a filter selection to focus messages on the various midi inputs & outputs in Zynthian. Useful for debugging MIDI connection and configuration.
Displays all received MIDI messages. This page now provides a filter selection to focus messages on the various midi inputs & outputs in Zynthian. Useful for debugging MIDI connection and configuration.
<br clear=all>
<br clear=all>
−===VNC-UI===
+This link opens a tab with the Zynthian UI, same as you would see with a directly connected display.
+===VNC-Engines===
+This link opens a tab with a desktop style GUI for and loaded engines (synths, effects etc.) that have a built-in UI.
+===Terminal===
+Access a terminal window for the OS directly from Webconf to debug, troubleshoot etc.
−<br clear=all>
−==System==
==System==
+In addition to the below you can reboot, shut down and logout from webconf here.
===WIFI===
===WIFI===