Difference between revisions of "256a-fall-2021/hw2"

From CCRMA Wiki
Jump to: navigation, search
(Homework #2: Sound Peeking)
Line 65: Line 65:
 
*** acknowledges help you received for this project
 
*** acknowledges help you received for this project
 
* 2) also submit to Canvas: URL to webpage
 
* 2) also submit to Canvas: URL to webpage
* 3) also submit to Canvas: a high-resolution (screen capture or with camera) video of your visualizer / audio-visual narrative
 
* 4) also submit to Canvas: screenshots of your visualizer!
 
* 5) also submit to Canvas: source code to the project (please clean up project to remove unnecessary files + test before submitting)
 
* 6) also submit to Canvas: README.txt file containing information on your Operating System and any instructions for running the project
 

Revision as of 12:07, 12 October 2021

Homework #2: Sound Peeking

Due Dates

  • HW2 milestone 1: due Friday (10/1): all three initial tutorials completed; HW2 webpage with progress report on learning/playing with Chunity
  • HW2 milestone 2: due Monday (10/11, 1pm): HW2 webpage updated with milestone video + in-class critique
  • HW2 final deliverable: due Monday (10/18, 1pm) HW2 final webpage/video + in-class presentation

reminder: please also organize your weekly reading responses online at http://ccrma.stanford.edu/~YOURID/256a/rrXXX/) -- replace XXX with the number of of the reading response.


Waves-bw.jpg

In this assignment, you are to visualize sound in real-time, using Unity for the graphics programming, and ChucK (via Chunity) as a sound source. Your program will visualize: 1) live microphone input and 2) a designed sound narrative written in ChucK. This is a fun project but there are many moving parts; start early.

Specification (part 1 of 4): Tutorials + Readings

Specification (part 2 of 4): Real-time Sound Input in Unity

  • follow and do Ge and Kunwoo's [Artful Design TV tutorial "HelloAudioVisualizer" https://youtu.be/nMeF2W2gv7E] (do Roll-a-Ball and Chunity tutorials first)
  • ChunityAudioVisualizer starter project => Unity Package | scripts only
  • end up with a usable Unity project as a starting point for your project
    • basic visualization of time-domain waveform and magnitude spectrum
    • test using the microphone input!

Specification (part 3 of 4): Visualizing the Spectrum History

  • design and implement a waterfall plot (like sndpeek), a real-time scrolling spectrogram, or another way to display spectrums over time
    • "make it read"!
    • feel free to experiment on how to represent the spectrum history visually

Specification (part 4 of 4): An Audio-Visual Narrative

  • using Chunity, create a ChucK program to run inside your visualizer
    • can use a combination of microphone (adc in ChucK) and sound synthesis
    • think about different "sections" or "movements", and how to transition between them
    • try to align the aesthetic of your visualizer and your ChucK program (give it personality)
    • (optional): can use keyboard input
  • aesthetic goal:
    • polish not important!
    • technical fanciness not important!
    • making the viewer/listener feel something: important!!

Note

  • have fun with it!!!
  • comment your code!
  • you are welcome to work together, but you must do/turn in your own work

Final Deliverables

turn in all files through Canvas, with concise online documentation + readme

  • 0) reading responses, to Chapters 2 and 3 (upload URL to Canvas, as per usual)
  • 1) HW2 project webpage (should be viewable at http://ccrma.stanford.edu/~YOURID/256a/hw2/). It should include:
    • a name and description of your visualizer design
    • a high-resolution video (screen capture or with camera) of your visualizer in action + narrative
      • (please upload to YouTube or Vimeo and embed the video from your webpage)
    • a few screenshots that capture great parts of your visualizer in action
    • instructions for using your visualizers, including any key/mouse control
    • links to your files of various kinds
    • a short text section that:
      • conveys your ideas/comments in constructing each program
      • describes any difficulties you encountered in the process
      • acknowledges help you received for this project
  • 2) also submit to Canvas: URL to webpage