If you are running headless and have connected to the Pi via ssh, you can monitor the CPU using the command 'top'. If you are running the the desktop, you can see how much of the CPU is being used by looking at the monitor box in the upper right hand corner of the screen. Starting off one more complicated synthdef requires fewer resources than three simpler synthdefs running at the same time. If you always fire off three synths at the same time, say, each with a different frequency, you may want to combine them into one single synthdef that takes three frequency arguments. Your synthdefs and invocation should be as efficient as possible. The processor, however, does climb to 100% quite easily and this can lead to audio stuttering. I have not experienced any issues with running out of memory. There is less memory on a Pi, which may limit the number of Buffers you can have loaded at one time. Therefore, installation-ready code should run fine on a Pi. SC 3.6 on a Pi runs exactly the same code as SC 3.6 on my laptop. The Pi does not have a lot of processor power and if you're not using the Desktop, you can save some space for installation to run. Otherwise, I would definitely boot to the command line. My only experience thus far is with the desktop, because I am also generating some simple graphics. You can set these options by running sudo raspi-config. Otherwise, you want to boot to a command line. Backing up a Pi system is just duplicating an SD card, so anything weird or dangerous you do is much less risky than it would be on your laptopĪre you planning on attaching a monitor to the Pi? If so, you will want to tell to boot to the desktop.The SC server is started separately from sclang.The Pi has fewer resources and crashes much more often and in more ways.There are a few important differences between running an installation on a laptop and on a Pi. It will not work with other Pi operating systems, such as windows, without substantial modifications, especially to the Bash Script This is written for Raspbian Wheezy but should work with other versions of Raspbian. I have been working with SC3.6 ( see these build instructions), but this should also be applicable to any other versions of SuperCollider. The Pi is much the same, except everything will crash at some point. In that post, I wrote about how anything could crash. ![]() Previously, I covered, how to keep an installation running.
0 Comments
Leave a Reply. |