PREREQUISITE
ARTS 2020 (Music and Technology I) or permission from instructor.
COURSE DESCRIPTION
Music and Technology II assumes a knowledge and experience in using computer systems to create, manipulate and engage in research within the fields of sound design, electronic music, electroacoustic composition and performance. The course is directed to upper-level undergraduate and graduate students as a project-based seminar which will guide their progress through the design, researching of and implementation of an individual project within in the course of the semester. This class is divided between a group seminar, focusing on the presentation of the aesthetic/ theoretical/ technical/ historical issues related to the field, and a workshop/lab.
Topics will be tailored to current issues raised through individual and group interests including but not limited to software design for musical systems, sound design, musical composition, audio engineering topics, micro-processors and physical computing, computer-aided composition and generative music, musical interfaces, musical robotics, sound spatialization, music in games and gaming environments, and theoretical research in music synthesis and composition. Each student will propose a musical project focus and scope of work for the semester, as well as a basis of the evaluation for individual work. In this way the hope is to combine the approaches of a music-focused research seminar, private study, guided research and group workshop/practicum.
Cultural and historical issues will be addressed through a series of student-led discussions of readings, listenings, videos, guest lectures and concerts. Students will also be asked to make use of the media collection at Folsom Library, as well as on-line access to media collections and journals.
The two-hour class sessions will generally be divided between classroom seminar presentation and workshop/lab. The final class session will be an informal presentation of individual projects completed in the class.
LEARNING OUTCOMES
Students who successfully complete this course will be able to:
- Design and execute the implementation of a large-scale musical research project or artistic sonic work.
- Manipulate, analyze and process large datasets (fixed and real-time) to populate and control musical systems.
- Break a significant project into component parts, research and realize the technical elements involved.
- Research similar artistic and technical works and build upon that experience in the development of a unique artistic work suitable for inclusion in your undergraduate portfolio or presentation in the ARTS Department Graduate and Critique, and in thesis research/artistic production.
- Articulate historical and technical issues contributing to personal creative production in a prepared lecture and demonstration for the seminar.
- Structure their time and progress towards a deadline in a consistent and disciplined way.
ASSIGNMENTS AND GRADING
- Class presentations, progress reports and sketches (10%)
- Lab Assignments (30%)
- Final Presentation and Project Master (40%)
- Lab and Class participation (20%)
COURSE POLICIES
You will be required to present all of your musical assignments to the class, to show your work within the software environment you used to create it, and to engage the class in discussion of your work. When you are not presenting your own work, you need to be attentive to whoever is presenting, and to engage them in discussion of their work. Failure to participate in class will lower your grade.
Participation in Classes and Labs
Each student is expected to share and assist other students in areas of their research as appropriate. Graduate students are expected to take a leadership role in working with undergraduate and graduate class members in and out of class on projects. If you are not participating adequately you will be informed and graded accordingly.
Attendance
You must attend class to succeed in this course. Two unexcused absences will reduce your final grade by one full letter grade. Each additional unexcused absence will reduce your final grade by another full letter grade. Five unexcused absences will result in an F for the course. Don’t do this. Absences can only be excused by a letter from a medical doctor or from the Office of Student Experience.
Lateness
Attendance will be taken 15 minutes after the start of the class. If you arrive more then 15 minutes late without a valid excuse you will be counted late. 4 late arrivals of this sort are equal to one absence.
Missed assignments
All assignments and presentations are mandatory and must be submitted or scheduled to be presented prior to the last day of class to receive credit.
Extra credit
TBD
Electronic Devices
If you are using your phone, tablet, phablet, watch, computer or other electronic devise for purposes other then class, such as email, chat, Facebook, games or assignments in other classes you will be counted absent.
ATTENDANCE
You must attend class to succeed in this course.
- Since much of the class is focused on listening to and discussing work in class, attendance is mandatory.
- ** More then two unexcused absences will affect your grade, detracting 1/2 grade each additional 2 unexcused absences. **
- Absences can only be excused by a letter from a medical doctor or from the Dean of Students' office.
- Late arrivals are very disruptive - continued late arrival will affect your grade.
STUDIO RESOURCES
Throughout this course, you will make use of the resources in SAGE 2510 as well as potentially the DCC Studio. Students enrolled in the course can gain access to the studio by passing a training sequence as specified in the DCC Studio handbook. You will also have access to recording equipment in the equipment room, which you will be checking out from time to time in order to make field recordings.
When appropriate for an assignment, or to explore sound in general, we encourage the use of your own computer, electronic instruments, etc. Often times, smaller components of a large project can be done on your laptop or home studio facilities and then brought into the main studio to be mixed and mastered.
STATEMENT REGARDING ACADEMIC INTEGRITY
The Rensselaer Handbook of Student Rights and Responsibilities define various forms of Academic Dishonesty and procedures for responding to them. All forms are violations of the trust between students and teachers. Student-teacher relationships are built on trust. For example, students must trust that teachers have made appropriate decisions about the structure and content of the courses they teach, and teachers must trust that the assignments that students turn in are their own performance. Acts that violate this trust undermine the educational process.
Policy on collaboration and cheating/plagiarism
Collaboration between students in this course is strongly encouraged. Likewise, students are encouraged—indeed, to some extent required—to exchange ideas, opinions and information. You are also encouraged to help each other in the lab and with performance, production, and presentation of projects.
Plagiarism of any kind is in direct violation of University policy on Academic Dishonesty as defined in the Rensselaer Handbook, and penalties for plagiarism can be severe. In this class you will be expected to attribute due credit to the originator of any ideas, words, sounds, or music which you incorporate substantially into your own work. This applies particularly to citation and fair usage of sources for media “samples” included in your compositions.
Please refer to the University policy on Academic Dishonesty as defined in the Rensselaer Handbook for policies and procedures governing Academic Integrity. As you will be presenting your work several times as you develop it over the course of the semester, any marginal activities relating to citation and plagiarism will be discussed as you develop your work.
Work found to be in violation of these policies will not be accepted and you will receive no credit for the work with no ability to make up the assignment. If the violation occurs in a final project you will fail the course and it will be reported to the Dean of Students.
DISABILITY SERVICES FOR STUDENTS
Students requiring assistance are encouraged to contact Disability Services: http://doso.rpi.edu/dss to discuss any special accommodations or needs for this course.
COURSE SCHEDULE:
The proposed course topics and schedule will be as follows (take note of project due dates!). Based on class progress and interests, this schedule is subject to change. Special topics, guest lectures, supplemental reading, listening and additional assignments to be announced.
RESEARCH PAPER ARCHIVES:
NIME ARCHIVE: https://www.nime.org/archives/
ICMC Archive: https://quod.lib.umich.edu/i/icmc
TEXTBOOKS / REPOSITORIES / FOUNDATIONAL MATERIAL
Designing Sound, by Andy Farnell (book missing)
Musimathics (Vol. I), by Gareth Loy
Musimathics (Vol, II), by Gareth Loy
Theory and Techniques of Electronic Music, by Miller Puckette
Week 1:
Tuesday, 1/13
Introduction to Music and Technology II
Assignment: Create Project Blogs
Week 2:
Friday, 1/23
Intro Music:
- Conlon Nancarrow's
Study No. 21 for Player Piano (Canon X)
-
Canon X Visualization
- Black Midi (not the band):
https://norient.com/stefan-schultze/phenomenon-black-midi-introduction
- Jean Claude Risset's
Duet for One Pianist https://chrysinanou.net/portfolio/duet-for-one-pianist/
Risset, J.C., Van Duyne, S. 1996. “Real-time interaction with a computer-controlled acoustic piano”, Computer Music Journal, 1996, Vol. 20, no 1, pp. 62-75. [
JSTOR link]
C. Nanou, Hamilton, R. 2009. “For Jean-Claude: [re]Presenting Duet for One Pianist” In Proceedings of the International Computer Music Association Conference, Montreal, Canada. [
.pdf
Nanou, C., Hamilton, R., "Historical Virtualization: Analog and Digital Concerns in the Recreation, Modeling and Preservation of Contemporary Piano Repertoire", Leonardo Music Journal, Issue 27, pp.27-31, Dec. 2017, doi: 10.1162/LMJ_a_01004. [
.pdf
General MIDI comparison (external vs. soundcard):
https://www.youtube.com/watch?v=BBvzCW1UCcc
More GM comparison (hardware synths):
https://www.youtube.com/watch?v=MWAnDOX5Xxw&list=RDMWAnDOX5Xxw&start_radio=1
General MIDI instrument list:
https://www.earmaster.com/wiki/music-technology/list-of-general-midi-instruments.html?srsltid=AfmBOoqMj7NWANq7qO4nIG9YV97vRBu8MXjwI-C1vgz9GsgXc9la_sbI
Pure Data's s_midi.c:
https://github.com/pure-data/pure-data/blob/master/src/s_midi.c
MIDI vs. Frequency (mtof, ftom):
https://caml.music.mcgill.ca/~gary/307/week1/node11.html
MIDI to Frequency (mtof): f = 440 * 2^((M - 69) / 12)
Frequency to MIDI (ftom): M = 12 * log₂(f / 440) + 69
Pure Data's mtof/ftom:
https://github.com/pure-data/pure-data/blob/master/src/x_acoustics.c#L19
DOWNLOAD:
* Max/MSP and Pure Data abstractions:
https://rpi.box.com/s/eiwafhqkjezr6oadd0wf5p0kpiaof78i,br/>
EXERCISE:
The Inner-workings of a MIDI file:
https://cm-gitlab.stanford.edu/craig/midifile
Week 3:
Tuesday, 1/27
Introduction to
ChucK
ChucK Class Library Reference:
- https://chuck.stanford.edu/doc/reference/
- https://chuck.cs.princeton.edu/doc/reference/
Examples organized by topic:
- https://chuck.stanford.edu/doc/examples/
- https://chuck.cs.princeton.edu/doc/examples/
ChucK Documentation (tutorials, language specification, etc.):
- https://chuck.stanford.edu/doc/
- https://chuck.cs.princeton.edu/doc/
Join the Community (seek/give help; share work):
- https://chuck.stanford.edu/community/
- https://chuck.cs.princeton.edu/community/
Many other things ChucK:
- https://chuck.stanford.edu/
- https://chuck.cs.princeton.edu/
Week 5:
Friday, 2/13
Research Paper Review
Audio Assignment: DUE FRIDAY 2/20:
* Create/compose/record a single mono audio track and bring it to class.
* Your audio track should be at least 30 seconds long, recorded as a 48000 kHz mono .wav file
* We will be using these source tracks as we start to explore spatialization both in the 8-channel classroom setup and later at EMPAC.
* One strategy for this assignment is to treat the track as a single voice in what will become a multi-channel spatial audio piece of your creation.
Week 6:
Tuesday, 2/17
NO CLASS (Follow a Monday Schedule)
Week 8:
Tuesday, 3/3
*** SPRING BREAK - NO CLASSES ***
Friday, 3/6
*** SPRING BREAK - NO CLASSES ***
Week 9:
Friday, 3/13
*** ROB @ GDC - NO CLASSES ***
ASSIGNMENT - Blog Update (2 options)
Due Friday, 3/13, please update your class blog's with one (or both) of the following assignments:
1) Attend and write a concert review of the Code Poems concert on Wednesday (3/11) at the RPI Chapel+Cultural Center. Your review should go beyond just "I liked it" or "I hated it" with special attention given to the technology systems at play and how they were used and implemented.
2) Give a detailed update on progress made to date on your own research project.
Week 10:
Tuesday, 3/17
Introduction to practical Ambisonics - Everett Carpenter
Week 11:
Tuesday, 3/24
Pre-EMPAC Demo Review Day
Friday, 3/27
Pre-EMPAC Demo Review Day
Week 12:
Tuesday, 3/31
** EMPAC ** - Spatialization Overload
Turenas - The Realization of a Dream by John Chowning
5th Order Ambisonic speaker dome (36 channel)
Wavefield Synthesis array (512 channel)
Wednesday, 4/1
** EMPAC **
Thursday, 4/2
** EMPAC **
Week 13:
Tuesday, 4/7
Project Status Reviews
Friday, 4/10
Project Status Reviews
Week 14:
Tuesday, 4/14
Project Status Reviews
Friday, 4/17
NO CLASS - FINAL PROJECT WORK DAY
Week 15:
Tuesday, 4/21
IN CLASS - FINAL PROJECT BUFF DAY
Friday, 4/24
IN CLASS - FINAL PRESENTATIONS
For your final project presentations (to be presented 4/24 and 4/28) you are expected to give an ~10 min talk about your research path this semester. You should expect to showcase the current status of your project to the class, as well as give a detailed look at the research paths that you followed all semester long that brought you to this point.
* Please assume that your audience is knowledgeable about issues in music and technology but not experts in the domain in which you are working. For instance, you don't need to define what MIDI is to this group, but you should not assume that anyone know details about your individual research project.
* Plan on giving a demonstration of your project's status. This can be live in class, or pre-recorded "just-in-case".
* Slides are not required for a talk such as this, but some kind of written or descriptive set of aides would be common in a talk like this.
Week 16:
Tuesday, 4/28
IN CLASS - FINAL PRESENTATIONS
Monday, 5/4
*********************** FINAL PROJECT SUBMISSIONS DUE 6:00 PM EST ***********************
This is the absolute last day that you can submit your final projects (or any work assigned during this semester for this class) and still receive a grade. For the final project itself, please submit the following:
* ALL YOUR CODE
Zip up all the code for the systems that you designed for your project and upload them to the class
uploads Box folder. Please put your name on the zip file.
* ALL YOUR DATA
If there is data required to run your system (audio files, image files, text, etc.) please make sure that data is uploaded as well. If you have terabytes of training data, please don't upload all of that (talk to me first please).
* WRITE UP
Please submit a 2-page or more writeup (.docx or .pdf) of your research this semester. Please cover the research question that you settled upon as your primary focus, the different paths or ideas that you experimented with during the term, and the details on how your system works.
* VIDEO
Submit a video showing your system working in its final state. This can be a fancy screen-grab with captions and fire transitions or a hand-held phone capture showing your system working perfectly. Both are equally helpful here in showing me the fruits of your labors.
All of this material should be uploaded to the class Box folder available at: https://rpi.box.com/s/eiwafhqkjezr6oadd0wf5p0kpiaof78i. Please make sure your name is on every document or file so that I can tell which is your work and which work belongs to your classmates.