Assigned Date: Monday, Apr. 27, 2015
Due Date: Friday, May 1, 2015
Due Time: 8am
Last modified on April 28, 2015, at 09:14 AM (see updates)
- Understand functions and use them to design processes involving modularization.
- Use predefined classes in program development (object-based programming).
- Understand events and graphical user interfaces and use them to develop simple computer-based instruments for electroacoustic music.
This is the final class project. You may work by yourself (solo), or with one partner (duo).
Compose a 2-3 minute piece for live performance. It is OK if you reuse (parts of, or all of) the previous assignment. If working with a partner, you may combine or focus on one of the previous submissions.
Your goal is to create something awesome - something that the audience will be inspired by, or very interested in seeing - a performance.
The piece should consist of at least 5 different sounds (audio files, or MIDI sequences).
The performer(s) need(s) to be actively engaged in the performance (i.e., decisively interacting with their program via GUI, MIDI, and/or OSC throughout the performance).
The first thing you need to decide is what type of sound experience you are trying to create.
Then, decide what types of music/sound building blocks you will need. It is okay to use (remix) existing sounds (e.g., audio loops off the Internet, or your personal music library); it is okay to record and use your own sounds (you on an instrument, or some ambient (e.g. traffic, birds, etc.) sound recorded by you); it is okay to use MIDI sequences (e.g., a BASS instrument or Percussion for rhythm). Any combination of these is is okay. The building blocks are up to you, as long as they make for a cohesive whole.
This assignment aims to develop and apply skills in planning, designing and executing a sound design, interactive musical performance, and/or music composition using JythonMusic. Possible techniques and approaches in completing this project include:
- Using audio recording/manipulation software (e.g., Audacity) to generate building (sound) blocks for ambient soundscapes.
- These files will be loaded into your program as AudioSamples.
- Using JythonMusic code to create and save MIDI files.
- Combining use of audio samples and MIDI generated sounds.
- Developing interfaces (GUI, MIDI, OSC) for live performance.
- Planning and executing a live performance.
- Aim for smaller WAV files that can be looped, as opposed to large files that will be played once. Otherwise you may run out of memory inside JEM, or when you try to submit your work on OAKS.
- If you use other people's work, give appropriate credit. For each sound file you use, keep a list of name, author/composer/creator, and URL (where the file came from). Include this list in the top-level comments of your program and the written report (see below).
Submit your work via OAKS. It should consist of the following:
- Your program (give it a descriptive name).
- All media (WAV and/or MIDI files) needed by your code. Again, aim for smaller files that can be looped, as opposed to large files that will be played only once.
- A document file in PDF format (created via Word, Google Docs, etc.) that includes the following, as separate sections:
- Your name(s), class, assignment, and title of piece.
- A description of the sound experience you are trying to create (your aesthetic objectives) with this piece.
- List of sounds (for those obtained from a website, include titles, authors, URLs).
- One of more images of your interface (GUI, MIDI, and/or OSC) with caption(s)/description(s). We should be able to appreciate the depth of your work through these images (and remember, a picture is worth a thousand words).
- Your program (code) included as an Appendix
On the due date:
- Bring a printout of the report and hand it in to the instructor.
- Be ready to perform your work in class on the due date.
Your grade will be based on how well you followed the above instructions. Also on:
- The variety of ideas you tried in your composition.
- The aesthetics and usability of your GUI design (aim for something that works well and looks pretty).
- Quality of code (e.g., comments, variable names, etc.)
- How interesting your music is.
- Live performance of your piece in class.