Sound Criteria and Stretch Goals
Work to have done:
- Work on your soundscapes, and push a soundscape preview to GitHub: .aup file, data folder, screenshot, and text description, plus updated list of assets and an mp3 export.
Plan for the Day:
- Reflective writing (5 min)
- Refresher on soundscapes we’ve liked (5 min)
- Gathering criteria (45 min)
- Sources, assets, permissions, citations (5-10 min)
- EXT: Studio and microconferences
1. Reflective writing (5 min)
2. Refresher on soundscapes we’ve liked (5 min)
Shift now in your writing to think about the blog posts on listening to soundscapes – or, if you haven’t read through them in a while, look at them quickly now with an eye toward what people are praising in the sound pieces: what seems to make a soundscape narrative work well? Jot down some notes.
3. Gathering criteria (20-25 min)
Primed now by that writing and thinking, I’m going to ask you to get in groups and brainstorm in pursuit of baseline and aspirational criteria for this unit.
3a. Crowdsource ideas (10 min)
To bring all our notes together while allowing for real-time collaboration, use this google doc: bit.ly/cdm2020fall-notes.
3b. Comment and Discuss in the Doc (10 min)
Read through the other groups’ notes, adding collegial comments in the margins to upvote or propose modifications. As you see consensus forming, propose an official version for our list of shared criteria. If debates emerge, maybe we can use mutually exclusive aspirational goals!
4. Studio While I Synthesize (25 min)
I’ll work solo to write up a list that reflects your consensus in the comments, while you all work solo (with groupmates on-hand for questions or other feedback) on your projects and any needed tutorials.
Like last time, please set yourself some studio goals in the doc; set a timer for 20 minutes; and then write a brief exit note on what you were able to achieve / what your next steps are.
5. Confirming criteria (8-10 min)
Please head back up to the criteria in the doc. Before we head into the weekend, I’d like to confirm that we’re on the same page. (At least pending any new input from async participants.)
For next time:
- Work to bring in a full draft: a solid attempt at a complete soundscape narrative, ideally at the target length. Rough edges are still welcome.
- Continue taking periodic screenshots and posting meaningful commit messages in git / GitHub Desktop.
- Not sure when to commit? One option is to do so whenever you’re about to stop working, with a note for what you’ll come back to. (e.g. Did you save and commit just now? Do you want to?) Add more commits whenever you’re happy with the (potentially interim) state of some new feature.
- Remember that you don’t need to change the project filename from draft to draft. Why duplicate or triplicate your file storage needs? Just say what’s changing in your commit messages, and keep track of which draft is which that way.
- Push a full draft, with the same four parts as the preview plus a CREDITS.md file with citations for the sources you’ve actually used (including direct links where possible) and permissions/license to use them. (This can be the same file as your ASSETS.md, now renamed.)
- NB: I’m only suggesting all-caps for special files readers might want to find quickly. It kind of loses the effect if everything is in caps. (Better to be all lowercase, if you have to choose.)
- Bring headphones