Fall2015.CITA180Homework5 History

Hide minor edits - Show changes to output

Added lines 1-73:
'''Assigned Date''': Friday, Dec. 4, 2015\\
'''Due Date''': Friday, Dec. 11, 2015\\
'''Due Time''': 8:00 AM

Last modified on {$LastModified} (see [[http://www.cs.cofc.edu/~manaris/index.phpFall2015.CITA180Homework5?action=diff&source=n&minor=n | updates]])

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


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 (also see [[https://www.dropbox.com/s/ssrvf0xrv8etgt8/guicontrols.py?dl=0 | guicontrols.py]]), MIDI, and/or OSC controls (e.g., see [[http://hexler.net/software/touchosc | Touch OSC]], and [[http://charlie-roberts.com/Control/ | Control OSC]]) for realization of live performance.

* Creating a sonification of an image that results in an interesting musical experience.


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


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 :)
# Author: Your names
# Email: Your email addresses
# Class: CITA 180
# Assignment: Final Project
# Due Date: The assignment's due date
# Purpose: A full description of your program (use your own words).


Your submission will consist of the following:

* A '''hardcopy of a written report''' (created via Word or Google Docs) that includes:
## Your name, class, assignment, and title of piece.
## A description of your aesthetic objectives and work process.
## List of sounds (for those obtained from a website, include URLs), if using samples.
## Your final GUI paper prototype (as a digital image) with caption/description, if applicable.
## Your Python source code (in an Appendix).

* A '''USB stick''' (will NOT be returned), to include:
## Your name, class, and assignment on an envelope containing the USB stick.
## Your report in '''PDF or Word format''' (see above).
## All your source sound material (strictly WAV or AIFF format), '''in a separate folder called "sounds"'''.
## 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'''.


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.