2,706
edits
Changes
Jump to navigation
Jump to search
Line 50:
Line 50: + + + + + + Line 80:
Line 86: + + − − [[File:zynthian_webconf_software_plugins.png|center]] Line 111:
Line 117: + + + + + + + + + Line 130:
Line 145: + + − + + + + + + + + + + + + + + + + +
→Plugins
Audio is probably the setting that most affects the behaviour. Get it wrong and the GUI probably won’t start (You'll see an error display). Luckily the webconf allows you to set the device up in spite of a non start of the GUI and the generic USB will generally work. If it doesn’t you will need to play around with the USB alsa settings. Understanding of the jackd start up settings is probably what’s required. It’s normally the hw: setting.
Audio is probably the setting that most affects the behaviour. Get it wrong and the GUI probably won’t start (You'll see an error display). Luckily the webconf allows you to set the device up in spite of a non start of the GUI and the generic USB will generally work. If it doesn’t you will need to play around with the USB alsa settings. Understanding of the jackd start up settings is probably what’s required. It’s normally the hw: setting.
The audio settings for USB are really just passed to jackd (the audio server) and if they don’t match then jackd won’t start hence no audio. The GUI logging in the webconf will tell you if this is happening. A very good starting point if it’s not working is by logging onto the Zynthian with SSH and giving the command: 'aplay -L'
This will tell you about ALSA settings (the audio hardware handler) and these settings will contain details that will be useful configuring the Jack settings.
More info: https://discourse.zynthian.org/t/audio-setup/2647
<br clear=all>
<br clear=all>
===Plugins===
===Plugins===
[[File:zynthian_webconf_software_plugins.png|right]]
Manage the installed plugins.
Manage the installed plugins.
<br clear=all>
<br clear=all>
[[File:MIDILog.png|right]]
[[File:MIDILog.png|right]]
Displays all received MIDI messages. Useful for debugging MIDI connection and configuration.
Displays all received MIDI messages. Useful for debugging MIDI connection and configuration.
====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 pushbutton 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>
===WIFI===
===WIFI===
[[File:zynthian_webconf_wifi.png|right]]
This page allows your to connect to WiFi networks, as well as manage stored connections.
This page allows your to connect to WiFi networks, as well as manage stored connections.
[[File:zynthian_webconf_wifi.png|right]]
To enable wifi access follow these steps:
1. In the Web config on the WIFI page you need to click '''Add Network'''
2. On the next screen choose your SSID from the dropdown menu and enter the passord.
3. Click the '''Add''' button
4. Enable wifi from the zynthian screen or in the Web Config set mode to '''On'''
<br clear=all>
===Security / Access===
[[File:Security-access.png|right]]
Allows you to change the password & set the hostname of the zynthian ( don't forget to select advanced to get hostname)
<br clear=all>
<br clear=all>