256a-fall-2013/hw3.5

Homework #3.5: Polished Visualizer Product + Final Project Proposal

Due date:

• part 1: 2013.11.5 11:59:59pm, Tuesday
• part 2: 2013.11.6 in-class presentation, Wednesday

In this two-part mini-assignment, you are to polish your visualizer into a product, make a webpage for it, and put together a proposal/presentation for final project.

Specification (part 1 of 2): Visualizer as Product

• polish your visualizer into a software product!
• finalize a name for it (e.g., probably should not be "VisualSine" or "fft" or "boiler")
• make things smoother, more pot smokin;
• add any addition features
• make a webpage on CCRMA server, to include screenshots, description, usage info, and a download link (use sndpeek's page as reference)

Specification (part 2 of 2): Project Proposal

• put together a proposal for your final project
  • check out this project page template
• recommended number of people on team: 1 or 2 (if 3 or more, please talk to me)
• craft some preliminary design for the product (the vision, for end users)
• architect the software (the engine/framework, for developers)
• make some realistic milestones (2 to 3) leading up the final presentation (in class, finals week)
• for Monday (11/2), present this in a 2-3 minute presentation

components and ideas

• only hard project requirement: your networked instrument should make use of OSC (sending and receiving)
• real-time audio / synthesis
• interaction (who controls what, and on which machine(s))?
• graphics from hw3?
•  ???
• perhaps a one-to-one musical instrument (two laptops, two people)?
• perhaps a networked musical game (e.g., musical hot potato, some form of marco polo)?
• perhaps ??!?!?!?

questions

• what is the interface? (e.g., keyboard? text? mouse?)
• how "real-time" is this instrument (it doesn't have to be)?
• what kind of music can the instrument make (as a group)?
• how many people and machines are needed in a performance setting?

• keep it simple! (aesthetically speaking, aim for a ultra-simple networked instrument that is still by some measure still "expressive")

Note

• have fun with it!!!
• your code should compile and run on the CCRMA machines
• comment your code!
• choose your own coding conventions - but be consistent
• you are welcome to work together, but you must do/turn in your own work

Deliverables

(part 1): in class

(part 2): turn in all files by via coursework:

• 1) source code to the project (*.h, *.cpp, *.c makefile, etc.)
• 2) also
  • links to your files of various kinds
  • instructions on building the project (for example, anyone in the class should be able to download and build)
  • a short README text section that:
    • conveys your ideas/comments in constructing each program
    • describes any difficulties you encountered in the process
    • lists any collaborators