Module 1: Audio

Here we look at code as a performative interface. Looking beyond code as a fixed object, we find artistic value in the process of code evolution. We explore experience of writing code in front of an audience and accepting imperfection. In a more practical sense, this is particularly good training for coding interviews.

Project 1: Live coding with Sonic Pi

Due Nov XX, 11:59pm

Your goal is to experience first-hand the practice of live coding. You will be using Sonic Pi and will record a video with audio of you live coding.

During your performance, you must:

Code, live, in real-time. Show your code.
Improvise, though you can plan most of the piece ahead of time. Even with most of the code pre written in a separate window, you should be experiment with new values for random seeds, loops, pitch values, etc during the “performance”
Generally, adhere to the Live Code Manifesto

Some language features you *must** use include:

setting a random seed (5 points)
sync’ing live loops (5 points)
loops inside a live loop, for example 3.times do... (5 points)
play samples (5 points)
use a synth (5 points)

The recording should last roughly 10 minutes (10 points). Note that in order to achieve this length, you will need to improvise a bit with your code in real-time. Do not plan out all 10 minutes exactly ahead of time, but instead have “goalposts” as discussed in class (10 points). Demonstrate familiarity with a core subset of the language (10 points). Make sure to have a focus on building a “soundscape” as a opposed to replicating your favorite sound (5 points).

Key tips

Make a short (30 sec) recording first to make sure your screen share and audio recording work working correctly
If you use zoom, make sure to share screen and share computer audio before recoding
You do not need to include your camera/face in the recording.
Use headphones when recording so that you are sure you are recording the computer audio directly, and not through your microphone. Mute your microphone so we only hear the Sonic Pi audio (unless you intentionally want to use live_audio).

What to hand in?

A link to the public posted video recording of your live code performance in Sonic Pi. The description field of the video should contain a short (at least 2 paragraphs, more if you like) write-up highlighting interesting moments in the performance or lines of code you thought were creative. Submit this link as a .txt file.

How am I graded?

Rubric

60 points - Technical Sophistication. Does your project utilize your programming skills in an effective way? Have you gone significantly beyond any example code you have used? Is this “your” work?
30 points - Documentation. Did you record properly (sound recorded directly from sound card of computer using share sound 10 points). Have you shown your complete code during the performance (10 points)? Have you posted the recording so that is publicly viewable (10 points)? Does the documentation highlight both the artistic aspect of your work, as well as the technical sophistication? Your work should be equally well appreciated by both a technical and non-technical audience.
10 points - Creativity. This is a subjective measure. You need to get comfortable with your work being judged in a subjective manner when working in Computing in Arts. To score full points here, you will need to put significant time into practicing live coding. Try to gain a level of fluency with Sonic Pi that allows you to explore new creative ideas during your performance.

Lecture 2-1: Technicals of Audio

https://docs.google.com/presentation/d/14o-OaOWX7zwejh8IHnCKAh89SrrJ3vnTPMu60T6Wqxk/edit?usp=sharing

What is digital audio? How is sound represented in a computer? What new challenges arise in programming audio as opposed to non-time domain programming?

Lecture 2-2: Live coding How to

https://docs.google.com/presentation/d/1GRB-i_KYCa-KAku-XM8XZEPdbnenraJ5bXYKBnguwsY/edit?usp=sharing

Lab: Sonic Pi

Installing and finding your way around Sonic Pi.

The goal of this lab is for you to install Sonic Pi, learn the basic interface, and make a short recording.

Complete sections 1.1, 2, 2.1, 2.2, 2.3, 2.4, 3, 3.1, 3.2, 4, 5.2, and 9.2 in the Sonic Pi tutorial.

To turn in:

Once you have completed the above tutorial sections you will have a good foundation to start live coding yourself. Record a video of you live coding in Sonic Pi. It doesn’t have to be fancy or long (less than 30 seconds is fine) - though a loop that plays a single note is enough. This is to confirm that you have the tool installed, understand the basic usage, can record your audio and code at the same time, and can post a video online. Post your video recording publicly, and save the link. For the lab, simply submit the link in a .txt file!

A note on recording

Please be sure you are recording the sound directly from your computer, and not record the output of your laptop speakers. If you are using zoom, you will want to share computer audio. Be sure to also go to “More” > “Select sound sharing mode” > “Stereo (high-fidelity)”. Be sure to mute your microphone. Follow analogous instructions for other screen recorders (e.g. quicktime). Once you have made your recording, be sure to listen to it once to make sure the audio has recorded properly and has not picked up your roommates’ conversations.

Lecture 2-3: Live coding ethos

https://docs.google.com/presentation/d/1RTROZiomVgFj6PGKguJcqWhoqLcFnBGo83bCgl388Fk/edit?usp=sharing

We start be examining the design of languages around creativity - how does the structure of a programming language encourage exploration and creativity? We then look at the practice of live coding and algoraves. How can language design guide us to ensure code does not break on stage? We ask - if code is art, what is virtuosity in code?

Lecture 2-4: Live coding visuals

https://docs.google.com/presentation/d/1C1to9CnMwM2WImtZL5XSJmPFrzmHkb5minvRBjVurko/edit?usp=sharing

Live coding in Hydra - how to program in a language you have never seen.