COURSE DESCRIPTION

Class Times: Tuesday/Thursday 1:30pm-2:50pm

Location: HH B131

Mailing list: staff-323@mailman.srv.cs.cmu.edu

Discussion list: post+academic.cs.15-323@andrew.cmu.edu

This course presents concepts and techniques for representing and manipulating discrete music information, both in real time and off line. Representations of music as explicitly timed event sequences will be introduced, and students will learn how to build efficient run-time systems for event scheduling, tempo control, and interactive processing. The MIDI protocol is used to capture real-time performance information and to generate sound. The course will also cover non-real-time processing of music data, including Markov models, style recognition, computer accompaniment, query-by-humming, and algorithmic composition. This course is independent of, and complementary to 15-322, Introduction to Computer Music, which focuses on sound synthesis and signal processing.  The pre-requisite for this course is 15-122.

READINGS

There is no textbook. Students are expected to read and comprehend ~1 paper per week.

GRADING

Attendance is required. You should not expect your grade to be higher than the percentage of classes you attend. There will be exams on reading material (15%), a mid-term (20%), and homework in the form of programming assignments (40%). Do not skip any homework assignments or, as simple math will tell you, your grade average will plummet. There will also be a final exam (25%).

You are allowed 4 late days during the semester. They can be used on any project other than Project 5 to turn in a project late without penalty. You cannot spend a fraction of a late day; lateness rounds up. After late days are exhausted, a penalty of 10% per day will be applied. Late group projects will be charged one late day per person per day.

To turn in a late assignment, create a directory in your AFS space, make it readable by elaw@cs.cmu.edu and dawenl@andrew.cmu.edu, copy your work there, and email the path only to the TAs. We will use the email time as the submission time, so the files should not be touched after sending email.

You should not need 4 late days. If there is a crisis in your life, please see your academic advisor. We will be happy to work with you and your advisor if there are exceptional circumstances.

POLICIES

The Carnegie Mellon University Policy on Cheating and Plagiarism is in effect for all courses at Carnegie Mellon including this one. Unless otherwise stated in writing in the assignment  description (for homework, project, exam, or other) collaboration is limited to:

•Discussion of concepts and algorithms,

•Discussion of language and coding details. For example, explaining how to pass a function as a parameter and call it is OK.

Examples of collaboration that is not allowed include the following (this is not an exhaustive list):

•Showing code for a programming project to a classmate,

•Reading code for a programming project from another classmate,

•Reading code solutions from a previous semester of this course,

•Providing or copying answers for homework (you can discuss and explain what the question is asking and the conceptual knowledge required to answer the question, but you may not share numerical answers or text that is turned in).