-
Notifications
You must be signed in to change notification settings - Fork 1
Homework Allison 04
A big part of learning at ITP is learning from each other. So share your work and in exchange you'll get to see everyone else's!
- Do the assignment.
- Contribute a question.
- Post documentation in the form of a blog post. Ideally something visual, some written thoughts, and code. If you are struggling with your sketch and can't get things to work, you should feel free to put your energy into writing about what didn't work (and vent any frustrations!).
My e-mail address: aparrish@nyu.edu
There's a link to schedule office hours with me on the ITP/IMA Help page (along with links for residents, staff, and other professors). If you don't see a time there that suits you, please send me an e-mail and we'll schedule something separately!
(You're welcome to send me e-mail at any time, day or night, but please be aware that I don't generally answer e-mail on the weekends.)
I save all of my in-class p5js examples in the web editor. You can see a full list here.
Assignments are due before class begins each week. I want you to succeed, and the material can sometimes be challenging! I'd still prefer that you turn in work that is unambitious or incomplete, rather than turn in work late.
Use this form to turn in your homework assignments. Here's the spreadsheet showing everyone's submissions. If you have work you want to turn in that you don't want to share with everyone, let me know, and we can make alternative arrangements.
I have a Google Drive folder that contains a worksheet for each week. (The worksheets were created by the inimitable Mimi Yin.) In my section, these worksheets are not required, but they are a very helpful way of testing your knowledge. If you have any doubts about your understanding of the week's material, I highly recommend doing the worksheet corresponding to that week. I won't be officially grading worksheets, but I do invite you to send me an e-mail or schedule office hours if you have questions about worksheet materials.
Allison's notes:
See also:
- Chapter 7 in Getting Started with p5.js.
- Video/capture: p5.MediaElement reference
As always, all in-class examples can be browsed here.
Media used in class:
- transit.mov (swiped from Shiffman's examples)
- "I was wrong"
- Kitty: JPEG version and PNG version (original, used under creative commons license)
- Filet-O-Fish
- Charon
First, review curriculum material for next week.
Due in two weeks: Make a project that manipulates images or video on the pixel level. Some inspiration:
- Color modes
- Copying pixels
- Slit-scan cameras
- Off-screen graphics
- PoseNet example w/ml5 and video
- Review materials on sound for next week
- Complete work on your assignment (see last week's description). Turn in with blog post.
- Media: Images and sound
- Sound synthesis
- Programming melodies and rhythms
In-class examples:
- Drum loop with framecount
- Sound jump
- Controlling an oscillator
- Lots of random sines
- Weird vowel synthesizer
Inspiration:
Media used in class:
First, review curriculum material for next week.
Due in two weeks: Make a project that sequences, synthesizes or analyzes sound.
Allison's notes:
Other resources:
- Pitch detection with ml5
- Jason Sigal's Visualizing Music with p5.js workshop notes (many cool examples)
Continue work on sound sketch (see previous week for brief), due next week. Also, review curriculum material for next week on strings and text.
Allison's notes:
First, review curriculum material for next week. (We'll likely only cover a small subset of this material in class, but there is a lot of material in there that may be useful to you!)
Then, come up with a proposal for your final project. Everyone will have 2–3 minutes to discuss their idea in class.
- More text analysis
- Loading external data sources
Each student will have 5–8 minutes to present their final project. From the syllabus: in the course of making your final project, "[y]ou are expected to push your abilities to produce something that utilizes what you have learned in the class that is useful in some manner to yourself or the world." Interpret that how you may!
It's up to you to figure out how to best document your project, here are some guidelines if you aren't sure what to include.
- Title
- Brief written description
- Visual Documentation: sketch running online, images, video, etc.
- References: links to related projects, code samples, etc.
- Source code (please cite your sources in the code comments)