Week 1. Introduction 1.

  • Intro to Syllabus
  •  Introductions
    • Luisa: why this class (or how I got to these questions by working on different projects)
      • Mappings.
      • Generative Music.
      • Visual/Physical representations of musical elemnets.
      • Culture/Theory/Physical levels.
    • Students: Why are you in this class? What is your experience with music, code, and design?
  • Exercise: experience one of these interactive songs for four minutes:
  • Discuss: Mappings; Composer/Audience.

 

Assignment

Write about your interactive song experience in your documentation blog:

  • What did the experience feel like? Was it funny/meditative/sad/something else?
  • Were you engaged / bored?
  • What worked / didn’t work?
  • What user actions controlled what aspects of the music? (in your own words)
  • Is this an instrument or a musical composition? Did you feel like a composer or like the audience?

Posts are individual.

 

The Code of Music ––Syllabus

Course Description

This course explores music through the lenses of computation and interaction design.

We will start with a structured exploration of rhythm, melody, harmony, and timbre: each week we will look into one of these elements in the context of music (listening to examples from different musical periods and styles), code (manipulating it programmatically), and design (creating visualizations and interfaces for it).

During the second half of the semester we will cover algorithmic composition techniques, and shift to a more self-directed approach. Students work toward their final projects, which might be digital applications, spatial installations, or physical devices.

Class examples will be written in Javascript, using libraries like Tone.js and P5.js, but students will be free to use other languages and frameworks. ICM or equivalent programming experience is required.

Instructor: Luisa Pereira
Email: lph233@nyu.edu
Meetings: Tuesdays and Thursdays, 4:45 to 6:00
Lab: Fridays, 4:45 to 6:00 (TBD)
Office Hours by appointment, in general on Wednesdays from 2 to 3pm.  Sign up here.

Grading

Class Participation: 10%
Exercises: 30%
Midterm: 30%
Final: 30%

Two absences or two missed assignments are automatic fails —please arrive on time.

Weekly Assignments

  • Assignments range from design exercises, like evaluating an existing system or sketching a new design, to programming exercises and readings. Lab time might be enough to finish some of them, but additional work outside of class might be needed for others. You will be expected to complete them by Monday night each week. 

Midterm Project

  • Create an interactive or generative musical experience focusing on one musical element. Your project can be either a new concept or an extension / refinement / implementation of an earlier assignment.

Final Project

  • Create an interactive or generative musical experience illustrating the concepts covered in this course. In your presentation, discuss musical, design, and programming aspects of your project. 

Weekly Schedule

  • Week 1. Introduction
  • Week 2. Melody
  • Week 3. Rhythm
  • Week 4. Harmony
  • Week 5. Timbre
  • Week 6. Midterm Concept dev and presentations
  • Week 7. Midterm Presentations
  • Week 8. Algorithms 1
  • Week 9. Algorithms 2
  • Week 10. Algorithms 3
  • Week 11. Final Concept presentations
  • Week 12. Workshop + Adv topic 1
  • Week 13. Workshop + adv topic 2
  • Week 14. Final Presentations

Code

The schedule on the second half of the semester will adapt to fit this particular group’s needs and interests.