General guide-lines for the etudes:
General guide-lines for the etudes:
There are three parts to the grade:
• Experiential Effectiveness: Does it create an emotionally powerful, memorable, or though-provoking experience?
• Style: Clear graphical layout so the flow of logic, factorization, and dependencies on components are clear. Good documentation. Clear labelling of who did what, and references to others' works.
• Technical quality: Does it work? Is it fast, responsive, robust to use? Does it exercise any interesting or significant techniques?
Grades in each part typically come in three levels: Insufficient / Failed to achieve anything; Adequate; and Superlative -- went the extra mile in some dimension.
- Your patches must start up and initiate on their own or have a one-button start procedure. Make sure to close your patch and test how it initiates.
- You are not solely evaluated on your patches. The result (installation, performance, UI, ...) must stand on its own regardless of the underlying technology.
- When presenting your work, statements such as "it is supposed to work but ..." are not acceptable. Treat your project with professionalism and count in the time needed for on-site debugging, calibration and unexpected technical difficulties. If things are not going as planned then use whatever you have at your disposal to present something interesting.
- From time to time get away from the computer and the patching window and test your ideas in the real world! Work with cameras, projectors, sensors, objects, matter, space, time, architecture, the body, the senses, movement, light, sound, feelings, affects, poetry, staging, physics, illusions, magic, ...
- If you are using pre-recorded video then it is best that you thoughtfully record/edit/prepare the video yourself. Avoid using "canned" video unless if conceptually relevant (ie. quoting, remixing).
General guide-lines for the etudes:
There are three parts to the grade:
• Experiential Effectiveness: Does it create an emotionally powerful, memorable, or though-provoking experience?
• Style: Clear graphical layout so the flow of logic, factorization, and dependencies on components are clear. Good documentation. Clear labelling of who did what, and references to others' works.
• Technical quality: Does it work? Is it fast, responsive, robust to use? Does it exercise any interesting or significant techniques?
Grades in each part typically come in three levels: Insufficient / Failed to achieve anything; Adequate; and Superlative -- went the extra mile in some dimension.
Etude #1 (modulate)
*video = matrix
- Modify Live | Recorded Video by combining or by applying a process.
- Two *videos effecting each other: Live-recorded, recorded-recorded, live-live
- Try to modulate the behaviour of your patch so that it evolves over time.
*video = matrix
Etude #3 (Audio-Vision) [due Nov25]
* audio = sound, inaudible-vibrations, audio-rate signals, etc.
Sample Student Work
- *Audio effecting video and/or video effecting audio.
- Think of the audio-visual field as a single (responsive) canvas.
- Think what it means to have on-screen and off-screen sound, and separation between sound and its apparent source.
- Try to modulate the behaviour of your patch so that it evolves over time.
* audio = sound, inaudible-vibrations, audio-rate signals, etc.
Sample Student Work