Interactive Voices

slices of past student audio and interactive projects

slices of past student audio and interactive projects




This two-part project is called Interactive Voices - it is an exploration of the meaningful integration of sound, movement and interactivity. The student will create an work of generative art combining audio, motion and interactivity.

This project will utilize content covered in lecture_04, lecture_05 and lecture_06, a two-part exercise_04, the Hour of Code, in-class demos, and reference of past student projects (code can be borrowed).



Theme: The content of the project is entirely at your discretion, and the audio and visual elements may be objective or non-objective. Sound sources may be found online, sampled from audio CDs, or recorded by you. Visual elements may be taken from parts of paintings or other images, or may be created from scratch. What is most important is that the sounds interact meaningfully with the appearance and movement of the visual objects.

Avoid using simple narrative. Do not approach the project as a music video or cartoon. Rather than telling a story, try to create an abstract experience. Think of this as poetry, rather than prose.


Part 1 Sound Design

Create sound samples. Explore how texture, rhythm, pitch and volume can be manipulated to evoke responses from the listener.

Use and explore the non-melodious qualities of sound (pitch, rhythm, tempo, amplitude, texture, tonality) to create harmony, dissonance or cacophony. Do not use any unmodified recorded music.

Part 2 Processing

Once the sound design is complete you will create an interactive interface that responds to your sound art.. Color, texture, compositional elements, line, and motion should relate thematically to the sounds they accompany.

The work will involve a performative component. Over time and with interactive input, composition, rhythm, speed, repetition, scale, rotation, position, color, opacity, balance, and perspective can be changed so that objects move and evolve as the sounds are triggered.


Program Downloads and Resources

Audacity website

Processing website



  • Proposal Consultation: discuss your theme and an outline of your ideas.

  • Sound Design Critique: present your audio work in progress.

  • Processing Critique: present your interface work in progress, with sound and enough animation/interactivity to get your message across.

  • Final Submission: Upload your files to CourseWork. Include an artist’s statement with proper credits listing the title of the piece, if any, and the origins of any appropriated source material.




  • Sound may play as an ambient accompaniment (non-diegetic, or background) to the movement on screen.

  • Sound may appear to be generated by the objects on screen, or as a result of user interaction (diegetic).

  • At least three (3) separate sound files must be created, and each of these sound files must contain at least 2 different sources of audio.

  • At least one of your tracks that you generate must be a stereo file

    • with different L/R channels (not a mono track converted to stereo)

  • All audio used must be organized upon submission:

    • original sounds may be recorded by you or found online (at least one segment must be recorded)

    • All audio content MUST must be keep track of using a txt file (not Word).

      • This includes borrowed audio AND your own recordings

  • All sounds must be manipulated so that they have enough difference than the original. One easy way around this is to use multiple sound elements from different sources (layered). This also ends up being more satisfying.

  • You MUST create a separate folder in your project file that contains all of your original sound clips.

  • You MUST submit your Audacity project files within your audio folder.

  • You should not be exporting any tracks from audacity with audio that is peaking (Red indicator), even if the source audio was peaking originally.


  • Your project MUST be titled as “First_Last_Title.pde”

  • Must include a vector object(s) that is generated within Processing.

    • Objects may appear at rest, but at some point must move within or out of the frame.

    • Objects must undergo a translation through time:

      • change in color, size, shape (or any combination of these)

    • Objects and or sound must be made to change at some point based on input from mouse or keyboard.

    • Objects and their movement must relate meaningfully to the audio.

  • May include raster images.

  • Code must be commented.

    • Begin each sketch with a comment section:

      • has our class/school/year and your info

      • explains your intentions, and how to interact, if necessary.

      • includes a list of which libraries to install before running the sketch (most of you use Minim, for example).

  • You may “borrow” code from other sources to supplement your own code (unless copyright or other notices prohibit it.)

    • the majority of the work must be your own

    • Any code borrowed from other sources MUST be credited within the comments.

      • You must also fully understand and explain what the code is doing (in comments for others to understand when reading your code)

      • you should alter it to your own unique usage.

  • Scenes may be used, jumping from one frame to another, allowing different effects or styles to happen all within one sketch.

final submission (audio+code):

All of your Processing and Audacity files should be put into a ‘Master Folder’ and named as “Firstname_Lastname_Project_Title”. This folder should include the following:

  1. A txt document (not Word) of your project statement.

    • this should be the FINAL, not the proposal

    • should include your name, contact info, class name/year/school, other relevant info to future visitors (and potential borrowers of your code).

  2. An audio Project file containing:

    • Original audio from source

    • Audacity file and Audacity project file(s) (remember to not un-linked or rename these). It is good to open and ensure these play before zipping master folder.

    • text file that contains a project statement (if separate from your coding project) and links to where you obtained each file.

  3. A coding project file containing:

    • processing pde file(s) (double check this plays before zipping your master)

    • data folder (containing only content that is required by your code)

  4. Compress (ZIP) your final Master Folder before uploading your final submissions folder on the Google Drive.

Note: that un-used data in your project was not listed above. This means that things that are not required, such as Photoshop files, videos etc, should be taken out of your master folder and its sub-folders before submission. This keeps the file size down and makes it easier for users to navigate (and for me to grade).


This project will be graded on (in order of importance):

• creative and effective approach to your subject matter
• demonstration of technical proficiency with Audacity/Processing and its procedures
• fulfillment of project requirements (each project detailed above)
• involvement in group critique
• oral presentation of solution
• overall completion of both projects (individually and unified)
• punctuality

Note: Make sure you also upload ALL of your project-relevant sketches and audio previews to the project_03 sketches folder on the Google Drive. (I will be factoring your project_03 “sketch” grade on what you upload there).