In class: CtrlMarkov demo
By next Tuesday, post your final project proposal to the documentation blog. It should include:
Concept. A short description of what you intend to create. You may include sketches.
Prototype. A first working iteration (or second, if you started last week)
Plan. Break down your project into specific taks, such as ’send data from two potentiometers to p5’, ‘gather MIDI files and convert to JSON’, ‘create animation’, etc.
The focus is more on getting started, working on your prototypes, and identifying any challenges that might take time to solve. Don’t agonize over your concept: it can evolve as you work on your project.
A brief history
Discussed + listened to examples:
Came up in discussion:
– Process music: It’s Gonna Rain by Steve Reich
– Longplayer: a piece that lasts 1000 years
– Eno’s Music for Airports and Bloom app
– Bach’s Fugue in G minor
Pieces that shocked audiences in their time:
– Beethoven Grosse Fuge
– Stravinsky’s The Rite of Spring
– Stockhausen’s Helikopter-Streichquartett (vid here)
As promised, a report of the Loop Summit.
Discussion: Buchla’s approach vs Moog’s approach
Discussion: scientific vs. artistic projects
Discussion: machine-made music vs human-made music
Came up in conversation: Hatsune Miku
By Jiwon Shin. Code examples + presentations.
by Owen Roberts
Combining the p5.play game library with Tone.js. Code: NAS/6_p5_play
1. Concept. In one or two sentences, what is your project? What does it do?
Why this: What were your motivations/inspirations? What were you looking to explore/express/learn? (particular elements of music, interface mappings, sound techniques, aesthetics, etc.)
What context do you envision it living in? What do you hope people will get out of experiencing it?
– Link to working project hosted on NAS
– Demo video / screen capture of you performing it (especially if interaction / intent not obvious on interface)
3. Technology. How does it work?
4. Process. What stages did you go through in creating it? Include early sketches, describe challenges and solutions/workarounds. Next steps: what would you improve in a next iteration?
5. Acknowledgements and references If you used code from examples or other projects, cite them, and tell us what you did. If you got help from fellows/teachers, thank them.
Documentation posts are due on Tuesday.
Next two classes:
– Thursday: Gaming lib with Owen Roberts
– Tuesday: Communication from Arduino to p5 with Jiwon Shin