CITA/CSCI 180 – Spring 2019 – Final Project

Assigned Date: Wednesday, Apr. 17, 2019
Due Date: Monday, Apr. 29
Due Time: 8:00am

 

Assignment

This is a pair-programming assignment.  You may work with a partner, as per these video instructions.  However, it is OK to work on your own, if you prefer.

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 include:

Details

Compose a 3-5 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. Remember this counts for 10 percent of your class grade.

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

Each audio file used should be no more than 15-20 seconds.

Background

To get possible ideas for your submission, you may explore the following:

Program Documentation

Follow the documentation instructions from Homework 2.

Remember, 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.”  Your code should have general comments at the top, which explain what the program does. You should comment all variables, obscure statements, and blocks of code.

Follow the textbook examples on how to write comments.

Your code should be organized well, so it is easy to read and understand.

Submissions

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

Be prepared to demonstrate your program in class.

Do all of the following:

(Suggestion: Print this out and use it as a checklist, to make sure you do everything asked – again, this is for 10% of your grade…)

  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, if using samples (for those obtained from a website, include URLs).
    4. Your final GUI (as a digital image) with caption/description, if any.
    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. We should be able to understand your performance by reading this report.  It does not have to be long.  It just has to be complete and clear (ask a friend to read it, to make sure it does this).
    7. Your Python source code (attach it to the end).
  2. Upload the same on OAKSThere 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

Your grade will be based in part on the report and in part on the performance.  Both are important.

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.

 

Skip to toolbar