Assigned Date: Wednesday, April 17, 2013
Due Date (Paper Prototype): Monday, April 22, 2013
Due Date (Final Piece): Monday, April 29, 2013
Due Time: 10:50am
NOTE: No late days can be used for this assignment.
Last modified on April 17, 2013, at 10:21 AM (see updates)
This is an assignment that could be pursued either solo or in pairs. Pair and solo designations will be decided and approved by the instructors within a day of the initial assignment (and finalized no later than Friday, April 19th, 2013). You may discuss the assignment only with your partner or the instructors.
This assignment aims to develop and apply skills in:
- Planning, designing and executing a sound-based composition inspired from the musique concrète stylistic tradition.
- Recording, collecting, or generating primary sound source material.
- Gaining experience with audio recording/manipulation software and generating soundscapes and textures.
- Combining use of samples and MIDI generated sounds.
- Shaping formal structures building upon experience acquired throughout the semester.
- Developing GUI’s for realization of live performance.
- Realizing finalized compositions in performance.
Compose a 4-5 minute piece for laptop performers using Audacity to record, collect and manipulate sounds.
Design and implement an interactive musical interface using Python (and the music and gui libraries) to facilitate performance of the piece and interaction between performers.
Follow these steps:
- Decide what "kind" of piece you want to compose: Are you interested in creating an ambient piece? a speech/text based piece? an industrial/mechanical piece? a noisy piece? a beat-based piece? This is an important decision that will guide your search for sound material.
- Select a title for your piece. Write it down.
- Familiarize yourself with Audacity: Experiment with loading pre-existing soundfiles, splicing them (cutting and pasting), processing them (by using some of the following found in the Effects menu: Change Speed, Change Pitch, Equalization (try extreme settings), Invert, Reverse, Sliding time Scale/Pitch Shift, Echo, Reverb), and assembling them in various ways by creating new tracks and layering them up against each other.
- Explore how to make a loop of your own here and here.
- Decisively begin searching for source material: Try to have an idea of what "kinds" of sounds you are seeking (i.e., metallic, vocal, grainy, ambient, etc.). This will make your search more directed and fruitful. Look for sounds with interesting identity, rich in timbre and/or envelope. You can record sounds yourself, using your iphone, or computer (good mics will give you better sound quality). Alternatively, you can find great recorded sounds (audio files) here:
- Catalogue your sounds and categorize them by description, source, etc. Start loading them on Audacity and process them in any and every way that seems appropriate/relevant. Save every interesting result and re-name it. It is very important that you document your work in every step of the way. Frequently pause and audition what you have, and reassess/revise your original composing plan.
- Finalize your piece conceptually, and create a sketch diagram/score: Decide what needs to be pre-assembled and what can be put together live in performance. How many performers will be needed? How will sounds be projected? What is the best method in presenting the material?
Interactive Musical Interface
Follow these steps:
- How many individual musical objects does your piece have? What types of actions does your piece require for each of these objects (e.g., start/stop, loop, pause/resume, change volume, change pitch (frequency), etc.)?
- What types of GUI widgets or graphical objects would you like to use on your interface? Does your interface make use of the computer keyboard or the mouse? In what ways?
- Does your interface make use of color or randomness? In what ways?
- Carefully read the paper prototyping section in Ch. 8 of the textbook (pp. 15-17).
- Create a paper prototype of your musical interface. It should be hand-drawn, but feel free to use color to make it more realistic.
- Bring your paper prototype in class on the first due date (see above) for presentation and comments. Your classmates are your target audience (some of them may be your performers).
- Once the paper prototype has been presented and commented on, you may begin implementing your GUI design in Python. Carefully follow the steps in "A Simple Methodology for Developing GUIs" in Ch. 8.
- Observe all coding style guidelines presented in class (e.g., top-level documentation, in-line comments, good variable names, etc.).
Your submission will consist of the following:
- A hardcopy of a written report (created via Google Docs or similar), to include:
- Your name, class, assignment, and title of piece.
- Your composition work journal.
- List of sounds (for those obtained from a website, include URLs).
- Formal designs, sketch diagram/score description of sound processing.
- Your final GUI paper prototype (as a digital image) with caption/description.
- Your Python source code (in an Appendix).
- A CD/DVD or USB stick (will NOT be returned), to include:
- Your name, class, and assignment on the CD/DVD (or on an envelope containing the USB stick).
- Your report in PDF format (see above).
- All your source sound material (strictly WAV or AIFF format), in a separate folder called "sounds".
- All your Audacity project file(s), in a separate folder called "Audacity files".
- All your Python programs (source code, sound files, any images used, etc.) in a separate folder called "code". Include a "README.txt" file providing instructions on how to perform the piece (e.g., which programs to run, in what order, etc.).
We should be able to perform your piece simply by dragging-and-droping the contents of your "code" folder (from your CD/DVD/stick) into our jythonMusic folder. Make sure everything is there.
Test this before you submit your CD/DVD/stick.
Your grade will be based on how well you followed the above instructions. Also on:
- How interesting your music is.
- The variety of ideas you tried in your composition.
- The aesthetics and usability of your GUI design.
- Quality of coding (e.g., comments, variable names, etc.)
- Live performance of your piece in class.