Schedule

• Milestone 1: Wednesday Nov. 16, 2016
• Milestone 2: Monday Nov. 28, 2016 (before class)
• Final Presentations: Tuesday Dec. 6, 2016, 6:30pm
• Deadline to Submit all the Final Deliverables: Friday Dec. 9, 2016 at midnight. This is a hard deadline and any submission made after that date will be ignored!

Late days don't apply to final projects!

Instructions

The format of final projects for this class is extremely open-ended. It can be an audio plug-in (AU, VST, AAX, etc.), a standalone application, a smartphone app, etc. The only requirements are:

• it should be programmed in C++,
• it should involve interactive graphics (2D or 3D),
• it should involve real-time audio synthesis and/or processing,
• it should sound good, look good, be fun and interactive,
• it should be innovative and focus on artful design.

Feel free to use any framework introduced in class (JUCE, Faust, STK, OpenFramworks, etc.) or that you can find. Try to implement the different principles that we studied in class: artful design, interactivity, standaloneness, etc. Your project doesn't have to be something that make sense: it could be a purely abstract piece of art. However, think carefully about every design decision that you make: try to create an "inner coherence" in the system that you will build – it should make a whole! For example, if a specific gesture generates a specific sound, and specific graphics, try to reflect on why it's doing that. In other words, your artistic and aesthetic approach matters as much as your technical implementation and will have a large impact on your final grade.

You should think about what the goals of your final project are: do you want to make a tool reusable by other people (in that case, a plug-in is probably a better choice)? Do you want to create a system for a performance, a video game, an art installation, etc.?

Depending on the nature of your project, different criteria will be taken into account for your final grade. For example, a plug-in might have less graphics involved than a standalone application, etc.

Milestone 1

A draft of your project should be available on git and you should be able to demonstrate it in class. Additionally, the markdown README file on your git should contain a short description of what your project is about, build instructions, a short documentation and a hand drawing/screen shot giving an overview of the different features of your project. Don't forget to send us the link to your project on git!

Keep in mind that we want you to create a webpage on your personal space on the CCRMA website presenting your project once it will be done. It is very easy to convert a markdown document to an html file using pandoc for example. Thus, if your README file is well written, you should only have to convert it to an html file and place on your web directory on the CCRMA server which shouldn't take more than 5 minutes. If you've never done that, check this wiki page.

Milestone 2

All the main features of your project should be implemented and pushed on git. You should have a draft of the README/documentation written. You should be able to present your advancement in class.

Grading

• Milestones: 30%
• Final Presentation: 30%
• Final Deliverables: 40%

Final Deliverables

• Final presentations will take place on the CCRMA stage on December 6 at 6:30pm. Each student will have 5 minutes to present their work (this includes set-up, presentation, performance, wrap-up, etc.). If your project is an art installation, it can be set-up outside of the CCRMA stage but you will still have to present it (we'll ask the audience to move where it is). If you made a tool, prepare a demo, same thing for video-games, etc. Also, feel free to include a performance to your presentation. There will be doughnuts, pizza and refreshments!
• As for homeworks, your code should be available on git and you should make a demo video presenting your project and make it available on YouTube (or somewhere else). Try to make it good (i.e. don't use the built-in speakers and microphone of your laptop to make the audio recording, also make sure it doesn't click!)!.
• In addition to that, you should create a webpage on your personal space on the CCRMA website. At the very least, this page should contain the content of the README file of the source code of your project, a link to your git, a packaged version of the source of your project, some screen shots and embed the demo video.
• Finally, make sure that your project is properly packaged on git: write a short documentation in the README and make sure that your code can be compiled on another computer. Unlike for homeworks, we will try to compile and run everyone's project. This is important as we want to make sure that other people can reuse your work.
• Send everything to Romain and Tim.