Changes

Jump to navigation Jump to search
2,083 bytes added ,  21:25, 17 February 2021
m
Line 1: Line 1:  +
Use '''ssh''' to remotely access the console (terminal) of the Zynthian from another computer. Use the  '''ssh''' command on Linux/Mac Terminal or use the freely downloadable '''PuTTY''' software for Windows. In most modern computer, using the name "zynthian.local" should work. If it doesn't, you can use the IP address too. See [[Finding your IP address]] for help on this.
 
=SSH/SFTP access:=
 
=SSH/SFTP access:=
   −
login: root
+
login: root
 +
password: raspberry
   −
password: raspberry
+
If you use ssh from the linux/mac terminal, it's so easy as:
   −
User pi doesn't exist any more and ... it's a good idea to change the password :wink:
+
ssh root@zynthian.local
 +
 
 +
* User pi doesn't exist any more
 +
* It's a good idea to change the password, specially if your zynthian is connected to public networks. You can do it easily from the webconf.
    
=Base Directory:=
 
=Base Directory:=
   −
/zynthian
+
/zynthian
 +
 
 +
Most of zynthian stuff is in this directory.
 +
 
 +
=Stopping/Starting the Zynthian UI=
 +
 
 +
You must use systemd-style commands to stop & start any system service. For the zynthian UI you would use:
 +
 
 +
systemctl stop zynthian
 +
systemctl start zynthian
 +
 
 +
If you want to run the Zynthian UI in the console,  you must stop the zynthian service and run the zynthian UI as a normal script using these commands:
 +
 
 +
systemctl stop zynthian
 +
zynthian.sh
 +
 
 +
Running zynthian from the console (terminal) allows you to view the detailed debug messages, which is convenient for solving issues. Posting these to the forum will enable experts to help you. You can also access the UI log messages from the webconf.
 +
 
 +
=Stopping/Starting the Zynthian Webconf=
 +
 
 +
systemctl stop zynthian-webconf
 +
systemctl start zynthian-webconf
 +
 
 +
If you need access the webconf's log messages, you can use:
 +
 
 +
journalctl -u zynthian-webconf
 +
 
 +
=Configuration without WebConf=
 +
If you can't access WebConf with a browser, you may edit this file:
 +
 
 +
/zynthian/config/zynthian_envars.sh
 +
 
 +
and run this command after saving the changes:
 +
 
 +
# zynthian_update_sys.sh
   −
Almost all the zynthian stuff like synth engines, audio plugins, soundfonts, zynthian user interface, setup scripts and other specific software is in this directory.
+
=Viewing the Zynthian graphics display on a computer=
   −
=UI configuration file=
+
If you are using Linux on your PC (or MacOSX with a X window server installed), you can login into your Zynthian box with '''ssh''' using the “-Y” flag:
   −
/zynthian/zynthian-ui/zynthian_gui_config.py
+
  ssh -Y root@zynthian.local
This file contains some configuration parameters for the Zynthian User Interface:
     −
* Logging level
+
this will allow you to run graphic applications in your Zynthian, while displaying the graphics window on your PC/laptop.
* Wiring layout
  −
* Font & Color scheme
  −
* etc.
  −
=Stopping/Starting Zynthian UI=
     −
You must use systemd-style commands to stop & start any system service, that includes the zynthian UI:
+
=Useful zynthian command line commands=
   −
  # systemctl stop zynthian
+
  aconnect -l        list MIDI connections (that ALSA knows about)
  # systemctl start zynthian
+
  aplay -l          lists audio hardware devices (that ALSA knows about)
 +
aplay -L          lists the ALSA device names of all hardware and software devices
 +
alsamixer          graphical mixer program for the ALSA that is used to configure sound settings and adjust the volume
 +
aseqdump          show the events received at an ALSA sequencer port
 +
jack_lsp -c        lists connections to/from each JACK port
 +
lsusb              list known USB devices
 +
lsof              list of all open files and the processes that opened them.
 +
patchage          graphical modular patch bay for audio and MIDI systems based on JACK and ALSA
 +
 +
export DISPLAY=:0  set which display is to be used
   −
If you want to run the zynthian UI in the console (i.e. inspect the logging/debug messages), you must stop the zynthian service and run the zynthian UI as a normal script using:
+
=More detailed info=
   −
# systemctl stop zynthian
+
More info on this page [[Accessing_Zynthian_from_your_computer]]
# /zynthian/zynthian-sys/sbin/zynthian.sh
 
393

edits

Navigation menu