Fall2014.CITA180Homework6 History

Hide minor edits - Show changes to markup

Changed line 23 from:

Compose a 2-3 minute piece for 1-2 performers.

to:

Compose a 2-3 minute piece for 1-3 performers. All performers need to be actively engaged in the performance.

Changed line 17 from:
  • Developing GUI’s (also see guicontrols.py), MIDI, and/or OSC controls (e.g., see Touch OSC, and Control OSC) for realization of live performance.
to:
  • Developing GUI’s (also see guicontrols.py), MIDI, and/or OSC controls (e.g., see Touch OSC, and Control OSC) for realization of live performance.
Changed line 64 from:
  1. 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.).
to:
  1. 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.). Also include JEM2.jar.
Deleted line 63:
  1. All your Audacity project file(s), in a separate folder called "Audacity files".
Changed line 17 from:
  • Developing GUI’s, MIDI, and/or OSC controls for realization of live performance.
to:
  • Developing GUI’s (also see guicontrols.py), MIDI, and/or OSC controls (e.g., see Touch OSC, and Control OSC) for realization of live performance.
Added lines 1-74:

Assigned Date: Monday, Oct. 27, 2014
Due Date: Friday, Dec. 5, 2014
Due Time: 7:50am

Last modified on December 01, 2014, at 10:51 AM (see updates)

This is an assignment that could be pursued either alone or in pairs.

Purpose

This assignment aims to develop and apply skills in planning, designing and executing a composition using jythonMusic. Possible techniques and approaches in completing this project may include:

  • Using audio recording/manipulation software to generate ambient soundscapes.
  • Combining use of audio samples and MIDI generated sounds.
  • Developing GUI’s, MIDI, and/or OSC controls for realization of live performance.
  • Creating a sonification of an image that results in an interesting musical experience.

Assignment

Compose a 2-3 minute piece for 1-2 performers.

Documentation

Follow the Golden Rule of Style: "A program should be as easy for a human being to read and understand as it is for a computer to execute." [3]

In general, you should comment any variable, obscure statement, block of code, method, and class you create.

Your comments should express why something is being done, as opposed to how – the how is shown by the code.

Top Documentation

Additionally, your code should always include opening comments as follows:

(:source lang=Python tabwidth=3 -trim :)

  1. Author: Your names
  2. Email: Your email addresses
  3. Class: CITA 180
  4. Assignment: Final Project
  5. Due Date: The assignment's due date
  6. Purpose: A full description of your program (use your own words).

(:sourcend:)

Submissions

Your submission will consist of the following:

  • A hardcopy of a written report (created via Word or Google Docs) that includes:
    1. Your name, class, assignment, and title of piece.
    2. A description of your aesthetic objectives and work process.
    3. List of sounds (for those obtained from a website, include URLs), if using samples.
    4. Your final GUI paper prototype (as a digital image) with caption/description, if applicable.
    5. Your Python source code (in an Appendix).
  • A USB stick (will NOT be returned), to include:
    1. Your name, class, and assignment on an envelope containing the USB stick.
    2. Your report in PDF or Word format (see above).
    3. All your source sound material (strictly WAV or AIFF format), in a separate folder called "sounds".
    4. All your Audacity project file(s), in a separate folder called "Audacity files".
    5. 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.).

Grading

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(s).
  • Quality of coding (e.g., comments, variable names, etc.)
  • Live performance of your piece in class.