← Back to Coding Art Fundamentals
Coding Art Fundamentals · Final

Final Project

Format. A required group performance, no solo projects, performed in person on December 2, within a shared 1–6 PM window shared by the three Fall 2026 Creative Computing courses (Coding Art Fundamentals, Intro to TouchDesigner, and Coding Music Fundamentals).

Group size. Minimum 2 people, maximum 3.

Forming a group. The week before the midterm, a Google Form goes out for all students to fill out. During the midterm presentation, the responses become a public Google Sheet, and students briefly reintroduce themselves and share a little about their background, so everyone can start seeing who they might want to work with. Week 9 (Nov 4) is the deadline to have a group. If a student doesn’t have one by then, one is formed for them that day.

Connecting to other software and adding interactivity. Every final project has to connect outward in two ways. First, software: beyond p5.js and openFrameworks, connect to at least one other piece of software or programming language, whether that’s ChucK, TouchDesigner, Ableton, Max/MSP, or a combination of these three Fall 2026 Creative Computing courses’ own languages. Second, interactivity: the piece needs some kind of live, external input driving it, a MIDI controller, a sensor, mouse or keyboard input, a camera, or something similar. OSC, MIDI, mouse/keyboard, and camera input are the specific techniques covered in class this semester, but students aren’t limited to those: research and use whatever best serves the piece.

Shared final projects. Some students are enrolled in more than one of these three Fall 2026 Creative Computing courses (Coding Art Fundamentals, Intro to TouchDesigner, and Coding Music Fundamentals), and a group’s final project can count toward more than one of those classes at once, as long as the piece actually uses every course’s own software. A student enrolled in two of the three has to use both of those courses’ tools in the project, ChucK and TouchDesigner, for example; a student enrolled in all three has to use all three, ChucK, openFrameworks, and TouchDesigner.

Masters student leadership. Each group should include at least one Masters student, when enrollment allows, expected to take a leading role.

MFA students only. On top of the group performance, MFA students complete one additional piece: a written application package, as if applying to a real program, grant, or residency, using the final project as the work they’re applying with.

Research and pick one real opportunity that looks appealing, then read through exactly what it asks applicants to submit. A few places to look, though any legitimate opportunity works:

Then build the actual application package that opportunity would require: whatever that means for the one picked (an artist statement, project description, budget, bio, work samples, etc.), using the final project as the project being presented. The point isn’t getting in, it’s learning to communicate the work to someone outside the class, and practicing paperwork every working artist eventually has to produce, for a job, a residency, a grant, or anything else. It also means having something ready if a real opportunity comes up. One is already open: CalArts’ own WaveCave call for works, Spring 2027, which the Music School and Creative Computing program both encourage students to apply to.

Submit the completed package as a single PDF in Canvas. If the application needs more than text, for example work samples in another format, include a link to them inside the PDF rather than uploading separate files.

If this final project is a shared project counting toward more than one of the three Fall 2026 Creative Computing courses (see “Shared final projects” above), the same written application package can be submitted for each of those courses. It doesn’t need to be rewritten per class.

The written package is due the same day as the final project’s digital submission (see “Presentation and digital submission” below).

A few resources on writing a strong application: How to Write a Strong Application, Nailing the Application: Setting Goals and Sharpening Your Written Materials, NYFA’s Application Tips (PDF), and NYFA’s Downloadable Application Guidelines for Visual Arts (PDF).

Presentation and digital submission

Digital Expo: Final Portfolio

Digital portfolio specifications.

Due. End of Week 14, Friday, December 11, at 11:59 PM.

Submission.

  1. Code, on GitHub, for this project, with a README explaining what it is, how to run it, and how it’s organized.
  2. A rendered, good quality recording of the performance, on YouTube, SoundCloud, or Vimeo.
  3. Fill out the CalArts Creative Computing student form at creativecomputing.calarts.edu/studentform to publish the work on the program website, using the group’s shareable recording link. Take a screenshot of the confirmation and upload it to Canvas.

One completed form and screenshot per group is enough. Every member of the group can submit the same screenshot and link along with their own individual submission.

Both the audio and video must meet a professional standard: good quality audio, and thoughtful video editing and lighting. Think of this as your professional digital portfolio, not something a friend recorded on their phone.

Using only footage from the Week 13 performance may not be ideal. Time to present that day is short, and the technical conditions are hard to control. Students are encouraged to meet on their own time outside of class and re-record the performance in a controlled environment, which is exactly why there’s a full extra week to submit this material.

Weight

30% of your final grade. See Grading on the Course Home page for the full breakdown.