12,301
edits
GMU:Autonomous-Collaborative/patchbox setup (view source)
Revision as of 21:22, 16 August 2019
, 16 August 2019→run config scripts
| (13 intermediate revisions by the same user not shown) | |||
| Line 8: | Line 8: | ||
# open the terminal type <tt>ifconfig</tt> to see the local IP address of the computer. | # open the terminal type <tt>ifconfig</tt> to see the local IP address of the computer. | ||
# type <tt>ping patchbox.local</tt> to see if the Raspberry is running and find its IP address. Tto stop the output press Ctl+Shift+C. | # type <tt>ping patchbox.local</tt> to see if the Raspberry is running and find its IP address. Tto stop the output press Ctl+Shift+C. | ||
# type <tt>ssh -X patch@patchbox.local | # type <tt>ssh -X patch@patchbox.local</tt> to connect to the Raspberry. Default password of the user "patch" is "blokaslabs" | ||
# Follow the setup and change the password. | # Follow the setup and change the password. | ||
# add a fallback static IP if no DHCP server is in the network: Type | # add a fallback static IP if no DHCP server is in the network: Type | ||
| Line 18: | Line 18: | ||
sudo apt-get upgrade | sudo apt-get upgrade | ||
sudo apt-get dist-upgrade | sudo apt-get dist-upgrade | ||
sudo apt install -y patchbox-cli | |||
== run config scripts == | == run config scripts == | ||
| Line 23: | Line 24: | ||
allows to set the password and the default soundcard | allows to set the password and the default soundcard | ||
sudo raspi-config | sudo raspi-config | ||
lets you autologin to the console | lets you autologin to the console [https://maker-tutorials.com/raspberry-pi-benutzer-automatisch-anmelden-booten/#variante-raspi-config Source (German)]. | ||
Alternatively in the desktop go to menu -> Preferences -> Raspberry Pi Configuration -> System : Set Auto Login to true. | |||
== | == Copy your files onto the RaspberryPi == | ||
to exit the ssh connection and return to the shell of your computer use the command | to exit the ssh connection and return to the shell of your computer use the command | ||
exit | exit | ||
| Line 32: | Line 34: | ||
scp to copy the pd files to the RaspberryPi. ([http://www.hypexr.org/linux_scp_help.php Source]) | scp to copy the pd files to the RaspberryPi. ([http://www.hypexr.org/linux_scp_help.php Source]) | ||
scp startupPatch.pd patch@patchbox.local:/Pd/ | scp startupPatch.pd patch@patchbox.local:/Pd/ | ||
For testing purposes our file is called startup.pd and looks like this: | |||
[[File:startup-pd.png]] | |||
==Make a startup script== | ==Make a startup script== | ||
Note: There is an easier method through patchbox-config: select module puredata then selecting a patch in the directory <tt>/usr/local/puredata-patches/{your_name}/main.pd</tt> [https://community.blokas.io/t/script-for-launching-pd-patch-with-midi-without-aconnect/1010/19 see here]. It works, but the method below has the advantage that you can define the pd startup flags yourself. | |||
Start the text editor "nano" ([https://tutorials-raspberrypi.com/raspberry-pi-autostart-start-program-automatically/ Source]) | |||
sudo nano /etc/init.d/startPdPatch | |||
Paste the following: | Paste the following: | ||
#! /bin/sh | #! /bin/sh | ||
| Line 73: | Line 79: | ||
To make the script executable, type: | To make the script executable, type: | ||
sudo chmod 755 /etc/init.d/startPdPatch | |||
== Test and make persistent == | == Test and make persistent == | ||
| Line 81: | Line 85: | ||
sudo /etc/init.d/startPdPatch start | sudo /etc/init.d/startPdPatch start | ||
Ctl-c to abort | Ctl-c to abort | ||
sudo update-rc.d startPdPatch defaults | |||
Will schedule the script to be run at startup. | |||