Stompbox Lab 0 2013
Lab 0: Making Sound with Satellite CCRMA
Lab write-up due on Tuesday at 10AM
Most instructions by Edgar Berdahl, and lab patches for musical interaction description by Matt Wright and possibly others
For this lab you need your Satellite CCRMA kit, a computer to program it, and some headphones with a mini 1/8" stereo jack.
Please note that we do not expect you to finish this "lab 0." These exercises and considerations are just here to get you warmed up and introduce you to pd. The future lab exercises will be much more specifically oriented.
- 1 The Satellite CCRMA Setup (Before Adding Arduino)
- 2 Powering Up For The First Time
- 3 Connect To Satellite CCRMA
- 4 Avoid Powering Down the Board Without Halting it First!
- 5 Getting Comfortable With Satellite CCRMA
- 6 Starting Audio And Pd
- 7 Dive Into Pd
- 8 The Patches Are Already On The Board
- 9 Short questions
- 10 List Of Objects
- 11 More Sound Synthesizer Patches
- 12 Copying Files To and From Your Kit
- 13 Design a different musical interaction
- 14 The Community
- 15 Appendix: Troubleshooting
The Satellite CCRMA Setup (Before Adding Arduino)
Included in your kit so far you should have
- Raspberry Pi Model B (with 512MB of RAM) - One memory card (it may already be inserted into your Raspberry Pi) - One Ethernet cable for communication with your laptop - One USB micro cable - One USB audio interface with 1/4" connectors
If you are missing something, please go get it before assembling your kit. Make sure you plug the SD memory card is seated all of the way in its slot.
Powering Up For The First Time
- Plug the Ethernet port of the Raspberry Pi into your laptop.
- Plug the USB audio device into the Raspberry Pi.
- Then use the USB micro cable to power up the Raspberry Pi. (If you have a USB power supply, you could use it to power the Raspberry Pi, or if not you can try using your laptop's USB connector to power the Rasberry Pi.) You should see some lights turn on, flickering every now and then. This means that the Raspberry Pi is booting up.
Connect To Satellite CCRMA
In order to see what your Satellite CCRMA kit is doing and program it, you need to log in to it. To do so, follow these instructions.
After you login, you will see the prompt ccrma@satellite:~$ This means that you are logged into a computer named "satellite" as the user "ccrma", and you are currently in the directory ~, which is the shortcut for your home directory.
Avoid Powering Down the Board Without Halting it First!
Would you take the battery out of your laptop and unplug its power adaptor without shutting down? I don't think so! The same goes for Satellite CCRMA, at least when you can avoid it, because it is a small computer running linux.
Now we will test the halt procedure. Run the halt command as superuser by typing sudo halt at the Satellite CCRMA prompt. Then you will again have to type in the password temppwd in order to have the privilege to run this command. Wait until about 15 seconds after you see the message "Connection to 192.168.105.106 closed by remote host," and then disconnect the power from the Raspberry Pi via the micro USB connector.
Getting Comfortable With Satellite CCRMA
- Turn on Satellite CCRMA again using the same procedure as before by plugging the micro USB connector into the Raspberry Pi. After about 30 seconds, the board should be booted up again, so you can log in again by running the command
ssh -XY firstname.lastname@example.org
- Run the command pwd to find out the current directory. You will find that you are in the ccrma subdirectory of the directory /home.
- Type the ls command to see what is in the current directory. The blue items are subdirectories of the current directory. You can change directories using the cd command. For instance, to change into the pd subdirectory, you should run the command
- Now again type pwd to make sure that you understand where you are! Run the ls command to see what files are in here.
Starting Audio And Pd
- In order to be able to hear audio, you will need to plug a pair of ear buds, headphones, or loudspeakers into the 1/8" (2.54mm) jack on the Raspberry Pi (often it is yellow).
- A default pd patch starts running automatically when your kit finishes booting up. To stop the default pd patch from running, execute the command
Remember that each time you boot up your kit and want to edit your patch, you should stop the default patch from running by using the command stop-default
- Start pd now with the following command (the "space" & just means that the pd process shouldn't take over the terminal -- that way you can keep using the terminal independently of whatever pd is doing)
This time the graphical user interface (GUI) for pd should also start.
- To start audio, click on the Compute audio checkbox.
- Now to test audio, go to the media pull-down menu and choose Test Audio and MIDI. If you still do not here any sound, then probably you missed one of the steps so far. If you look at the messages in the main pd window, you might find a clue.
- Once you have audio working, close the window test audio and MIDI window.
- Choose Open from the File menu and select the patch 4_algorithmic_music.pd within the pd_lecture subdirectory. Then go back to the patch, move the speed and width sliders slightly to the right, and bring up the volume. You should now hear some sound in your headphones. Play around with the parameters to see what new sounds you can discover.
Troubleshooting: If you still do not here any sound, then probably you missed one of the steps so far. If you look at the messages in the main pd window, you might find a clue.
Dive Into Pd
- The patch ~/pd/examples/just-play-WAV-files/play-WAV-file.pd shows the easiest way to play a WAV file. Try it out!
- Look at the pd lecture patches stored in ~/pd/pd-lecture (For example, see the patch 4_algorithmic_music.pd. Make sure that audio is on and increase the volume from zero in the patch.)
- Right-click or option-click on any object to get a contextual menu including "help," which opens that object's help patch. (If you are using a Mac and don't have a right mouse button, then go to the X11 pull-down menu, select Preferences, and make sure that Emulate three button mouse is checked in the Input pane. Now, you should be able to right-click by clicking while holding down the Command key.)
- Right-click on a blank portion of a Pd patch. Now when you select "help" you get a list of Pd's built-in objects, arranged by category.
- In the upper right hand corner of each Pd window is a "help" menu. This accesses the Pd tutorials as well as some online reference documentation.
The Patches Are Already On The Board
- You can find the main patch for the laboratory exercise at /home/ccrma/pd/labs-Music-250a-2012/lab1/myinstrument.pd Open it and make sure that compute audio is set to on. Play around with the patch. You should be able to exhaust its musical potential in a matter of minutes; reflect on its strengths and limitations.
- Also try to understand how it works as a piece of software. (But please don't get hung up on the arcana - as always, if you get stuck, ask for help rather than waste time.)
Why is the following patch a bad idea?
Make a patch that shows how to connect some objects together to calculate the function 1-x where x is an input number. Save the patch in a file called OneMinus.
List Of Objects
- Here are some lists of pd objects that you can use to discover new object names: http://protman.com/content/list-puredata-objects-and-extended-objects http://www.umatic.nl/workshop/objects.txt
More Sound Synthesizer Patches
- Try out some of the patches from Andy Farnell's book Designing Sound. These patches are installed in ~/pd/DesigningSoundBookExamples Most of the patches in there work with this version of pd, but a few patches don't! (As you try out the patches, keep in mind also that many of the patches are subpatches. That means that they are lower level patches that are used to serve some specific purpose within a higher level patch. Therefore, you may have to search around some to find the higher level patches that are easier to use to make sound.)
- One intriguing way to synthesize sound is using physical models. A physical model is a computer program that simulates the laws of physics to create sound. Some physical models simulate traditional acoustic musical instruments, or other models simulate hypothetical situations that could be built using physical elements, but might be impractical. Try playing around with some of the physical models in ~/pd/SaM-models -- the FireFaderSimulator versions of the patches are the ones you will want to use. The process of tuning the model parameters can be useful from a compositional perspective because it can help provide you with a specific palette of sounds.
Copying Files To and From Your Kit
- Alternatively, if you would like to use software with a nice GUI for copying files back and forth from your kit, you can install additional special software on your laptop. For Windows, install Secure FX, or for Mac OS X, install Fetch. These programs actually use scp, but they hide the details of the pathnames from you.
Design a different musical interaction
Here are some ideas of changes that might make the patch more interesting:
- Involve more QWERTY keys
- Involve the mouse (see the [MouseState] object)
- Load in a larger collection of samples.
- Implement a mechanism to switch among banks of samples
- Multiple gestures to one result: design a way for the parameters of each triggered note to depend on multiple key presses. For example, maybe only the space bar triggers notes, and all the other keys determine parameters of notes.
- Make your patch automatically generate a bassline as a function of the key presses
- Set multiple parameters modally, as volume works in the sample patch
- Use chording: keep track of all the keys that are currently pressed, and use only that information to set the parameters for each note.
- One gesture to multiple results
- Use the "metro" object to trigger a steady stream of notes. Now you have two new parameters: repetition rate, and whether the metro is on or off.
- Use the "counter" object to step through a cycle (of samples, parameter settings, etc.)
- You could combine "metro" and "counter" to build a rudimentary sequencer that can step through a rhythmic pattern
- Invent a mechanism to record short sequences of keypresses and play them back in time.
- Incorporate looping or other interactive controls over the soundfile playback
- Use Pd's "spigot" object to route control information to different parts of your patch at different times
- Use some additional signal processing such as a filter, delay line, reverb, tremolo, etc. This gives you more parameters to control.
- Polyphony: make it so the patch can play multiple samples at the same time. (Hint: put multiple copies of "play-sample" in your patch)
- Use a totally different form of sound synthesis, such as FM, granular, or physical modeling.
We recommend that you pick only one or a small number of these and work on it in depth, iterating on both the program/test/debug cycle as well as the design/implement/play cycle to craft something that has actual musical potential or is at least more fun to play. If you have an existing idea for your class project, you could use this lab to start thinking about implementing some of the modes and mappings. By all means, if you're inspired to try something else, go for it. If you'd rather spend today getting more of a broad sense of Pd's capabilities, feel free to work on many of these suggestions.
There is a large, dedicated, and very generous community of Pd users on the Internet. Do some web searching (e.g., with a search engine, or else starting from some more specific resources) and look for interesting externals and/or patches. Optional: Download, install, and play with at least one. Can you incorporate it into what you programmed in the previous part?
For more help in finding resources, don't forget to look on the PID Links page.
- If you are having problems with audio, make sure that compute audio is set to on.
- If the audio is stuttering, then your processor might not be powerful enough to run all of the patches that are open. Remember, Satellite CCRMA is not as powerful as a laptop. Therefore, be careful about building complicated patches. You can monitor how much CPU you are using by running the top command in the terminal.
- Type dmesg to see if there are any relevant messages that look like error messages.
- If you are running out of space on the SD card, you can free up some space by deleting items in /usr/src. For instance, all of the files needed for building Pure Data Extended are rather large.