15-322 Introduction to Computer Music: 15-322 Projects





15-322 Introduction to Computer Music: Projects

This is an overview of course projects and schedule. See individual project pages for details.
  • All labs are due 11:59pm on the shown due date
  • You have 3 grace days for the entire semester (P0 through P9 only) - use them wisely.
  • You can use at most 1 grace day for any one assignment
  • All assignments are handed in via AFS.

Schedule

Proj  Weight (%)  Name  Due 
P0   2   Nyquist, Audacity, Hand-in   Jan 13  
P1   7   Sound Sculpture   Jan 18  
P2   8   Additive Synthesis   Jan 25  
P3   9   Short Composition I   Feb 1  
P4   8   FM Synthesis   Feb 8  
P5   9   Short Composition II   Feb 15  
P6   6   Term Project Proposal   Feb 22  
P7   9   Granular Synthesis   Mar 1  
P8   4   Interim Term Project Report   Mar 24  
H1       Homework on Week 10   Mar 31  
H2       Homework on Week 11   Apr 7  
P9   17   Term Composition   Apr 21  
P10   9   Term Project Written Report   Apr 29  
P11   4   Term Project Oral Report   Final Exam Period  
(Note: 8 points reserved for additional homework.)
Total100

Collaboration and Academic Integrity

All assignments in this course are single-student assignments, except for the term projects which can be done in a team of at most four. In general, projects consist of three ingredients:
  • Code: the top-level program used in your project must be your original creation. You can incorporate example code provided to the class, but this should either be called as a subroutine from original code, or the example code should be substantially modified or extended.
  • Music composition: projects that require composition must contain an original composition. It is not acceptable to realize existing music by another composer.
  • Sound files: if you incorporate samples in your work, you must acknowledge them by providing URLs or copies of the sounds unless you recorded them yourself. If you record another musician, you should provide the raw recording, acknowledge the musician, and make sure the recording does not violate the "Music composition" rule (see previous item).
Moreover, the student is responsible for understanding and carrying out the intent of each assignment. Attempts to meet the written requirements without doing the intended creative work will receive low grades.

It is not considered cheating to clarify vague points in the assignments or textbook, or to give help or receive help in using the computer systems, languages, debuggers, or other facilities.

It is not considered cheating to discuss a general technique or approach to achieve a goal in programming, synthesis, composition, or sound editing.

It is not considered cheating to ask or tell what built-in function to use to achieve a goal or specification.

It is considered cheating to copy or disclose a specific program fragment, synthesis algorithm, or element of composition.

Homework (written short-answer assignments on the reading and lectures) must be done individually. Do not give, take, or discuss answers.

© 2010 - Roger B. Dannenberg