CITA/CSCI 180 – Spring 2019 – Homework 4

Assigned Date: Monday, Feb. 25, 2018
Due Date: Monday, Mar. 4
Due Time: 30 mins before class



As discussed in class, Live Coding is the practice of creating a musical performance by coding on-the-fly.

Write a Jython program that generates an interesting Live Coding performance.  In the interest of time, you should pre-code different code portions in a file, so that you can execute them quickly by using JEM’s Live Coding Run options:



  • Your Live Coding performance should last between 1 to 3 mins approximately.  A little longer is OK, especially if the performance is engaging / interesting.
  • Your program file should contain at least three pre-coded portions that generate sound using different instruments.  It is OK to use percussion (channel 9), if you wish.
  • You should clearly document these code portions using multi-line comments describing their purpose (what type of sound they generate, and how they fit into the overall performance).
  • Store all code portions in the same file, and give it a meaningful name.  Use this file during your performance in class, i.e., you should do minimal coding in class.  Most of your code should be already pre-written.
  • You should NOT just Run your program (like we have done up to now).  Instead, you should interactively run different portions of your code at different times (i.e., Live Coding).  What these code portions contain and do is up to you.
  • It is OK for different code portions in your program to call Play.midi() on their own.  (I.e., it is OK to have several calls to Play.midi() in your file, as long as they are executed separately – see Live Coding above).

Strong Hints

As discussed in class, consider carefully the interest curve of your performance.

Design before you implement.

Provide usual header documentation describing the performance this program is used to generate via Live Coding.

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


Do all three:

  1. Upload your program file on OAKS.
  2. Hand in a printout of your Python program in class on the due date.
  3. Be ready to perform it in class.

Your program should have a meaningful name, e.g.,

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 grade will be based on how well you followed the above instructions, and the depth/quality of your work.

Skip to toolbar