Spring2017.CITA180FinalProject History

Hide minor edits - Show changes to markup

Changed line 43 from:
  1. Your final GUI paper prototype (as a digital image) with caption/description, if applicable.
to:
  1. Your final GUI (as a digital image) with caption/description, if applicable.
Changed lines 29-56 from:

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).
  7. Input: What kinds of inputs are being used.
  8. Output: What kinds of outputs are being generated.

(:sourcend:)

to:

Since this is used in lieu of a final exam, you have to also submit a written report that describes it (see below).

Changed lines 60-88 from:
  • Live performance of your piece in class.
to:
  • Live performance of your piece in class.

Code 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).
  7. Input: What kinds of inputs are being used.
  8. Output: What kinds of outputs are being generated.

(:sourcend:)

Changed line 59 from:

You will submit your assignment by both handing in a printout in class, and online via OAKS.

to:

You will submit your assignment by both handing in a printed report in class, and online via OAKS.

Added lines 1-86:

Assigned Date: Friday, Apr. 21, 2017
Due Time: 8:00 AM
Due Date:

  • Section 01: Friday, Apr. 28, 2017
  • Section 02: Monday, May 1, 2017

Last modified on April 29, 2017, at 11:37 PM (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 music and/or artistic composition / performance 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.
  • Combining a traditional instrument with JythonMusic interactive software.
  • Developing creative expressions involving visual components and/or graphical user interfaces (GUIs), MIDI, and/or OSC controls (e.g., see Touch OSC, and Control OSC) for realization of live performance.

Assignment

Compose a 2-3 minute piece or interactive artistic experience for 1 or more performers. This must involve 1 or more OSC devices (see above). It may also include additional MIDI devices and or GUI interfaces.

It has to make artistic sense.

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).
  7. Input: What kinds of inputs are being used.
  8. Output: What kinds of outputs are being generated.

(:sourcend:)

Submissions

You will submit your assignment by both handing in a printout in class, and online via OAKS.

Be prepared to demonstrate your program in class.

Do all of the following:

  1. Hand in a printout of a report (created via Word or Google Docs). This should include:
    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. Photographs (one or more) of your performance equipment (e.g., phone) in action (ask a friend to help you, or use a mirror). Include appropriate captions explaining what each picture shows.
    6. Your Python source code (in an Appendix).
  2. Upload the same on OAKS. There should be several files in your submission (your program, your report with the images (in PDF), and the audio material used).
  3. Be ready to demo your program in class on the day of the exam.

Grading

All your materials (see above) need to be ready on the time of the final - no late days can be used for this. This is the final exam.

Your grade will be based on how well you followed the above instructions. Also on:

  • How interesting your music/art is.
  • The variety of ideas you tried in your composition.
  • The aesthetics and usability of your OSC/MIDI/GUI design(s).
  • Quality of coding (e.g., comments, variable names, etc.)
  • Live performance of your piece in class.