Sound studio
Work to have achieved
- Any remaining feedback from last class's workshop
- Work in pursuit of an audio narrative
- Optionally, a short blog post about possible future audio projects or revisions
Plan for the day:
- It’s a studio day! You can choose what to do!
- But I do have some revision-oriented notes for the whole class (5-10 min)
- Studio time (50-60 min)
- Make a plan
- Execute it
- Exit note
- Reflection guidance / deadlines (10 min)
1. It’s a studio day
At the same time, it’s worth noting that you’re working in a shared space, in a studio. If you have questions, or you want feedback on something, you have your classmates and your instructor on-hand. Try not to monopolize anyone’s time, but do be open to the possibility of getting farther together than you could on your own.
2. Some revision-oriented notes for the whole class
A few seeds of ideas I want to plant, having listened through as much as I could:
When giving credit, direct attention to your TASLs.
We talked a bit about this at the start of the unit: the idea that (a) if you're using Creative Commons assets, you're required to attribute them to a source, and (b) that such attribution ideally includes Title, Author, Source, and License, or TASL. (If you know a date, I'd add that, too, for TASLD.) And most of you are doing a great job of listing those things in a file in your repo! Nice. Just remember that for "Source," a link to the search engine or database that you found it with (e.g. FreeSound) isn't enough: you'll want to point to the specific page for the individual file you're using.
A few finer points on CC licenses, especially if they say SA
Remember that in-class quiz: if you're using source material with a Creative Commons license, you do need to specify which license it uses: CC-BY, CC-BY-NC, etc. This is especially important for Share-Alike licenses (CC-BY-SA, etc), because they force you to use the same license and can therefore be in conflict with each other.
And if you are using material with a Share-Alike license, make sure you license your project the same way! All you need to do is add a file called LICENSE.md to your repository, and add the HTML generated by https://chooser-beta.creativecommons.org/.
But now imagine you send your mp3 to someone outside of the class. Does it contain all those references? Probably not. Does it contain a spoken tag letting people know where to find the file with all those references? Maybe not yet. But it probably should.
A lot of the podcasts I listen to end with a sign-off: often, some kind of theme music, and a voice saying who played what role. Often they'll say who wrote the theme music, as well. You can use this same space to say, "For a full list of sources and attributions, please see github dot com slash [your username here] slash audio hyphen narrative hyphen 2025 spring."
Consider removing background noise
Sounds recorded in different places often have different levels of background hum, which can make their entrances and exits feel more intrusive. You can mask this with fade-ins/outs – or you can try to remove the background.
Two options there: you can use Audacity's Noise Reduction effect (which is easiest if you recorded an extra second or two of "silence" before each take), or you can try to use the Spectral View to snip out particular pitches at particular times. Luckily, these are the first two tips in Mike Russell's "10 Powerful Tips Every Audacity User Should Know". Well worth your time!
Consider volume limiters as well as relative volume.
Many of you are doing smart work to differentiate foreground sounds from background, in part through "ducking" the background to a lower volume while keeping the sound going to provide depth. (If you're not, but you want to, look for it under Effects > Volume and Compression > Auto Duck.) But sometimes, there's just too much sound to hear clearly.
On the foreground side, one risk of recording original sounds is overloading the microphone, such that you get a kind of crackle or squeal as the sound level exceeds what the system can handle. If you notice this happening in one or two specific spots – you can look for places where the waveform hits the top of the track, or where the volume goes into the red – try Effects > Clip Fix, which should give you a little more room.
If each individual track is fine, and it's just the sum total mix that puts it over the top, you can apply a Limiter effect to the master track and it will auto-adjust the overall volume to a manageable level. Click the Effects button at the left of any track; you should see Master at the bottom.
Consider a soundtrack.
Even if your narrative takes place somewhere you wouldn't expect music to actually be audible, a low-key background soundtrack offers a lot of benefits: it covers transitions that would otherwise be silent; it masks differences in background noise across assets and thus helps them seem more like they belong together; and, as we noted when we started this unit, music is great at signaling (or shifting) emotional tone. And it doesn't have to be obtrusive: in most movies, you notice it more when there isn't music playing than when there is.
Be sure to check out the Sounds and Music section of the Resources page for tips on where to find openly licensed tracks you can use, including some databases (such as the YouTube Audio Library) where you can search by mood.
Consider adding a voiceover layer.
Maybe I'm just getting old, but as I've puttered around various places by myself I've noticed that I don't stay silent: I mutter as I putter. Even if it's just short reactions to things I see ("nice!") or read ("really? really."), even if it's not actual words ("hmm."), I tend to narrate my day.
All of which is to say, if your audio narrative takes your listeners along on a ride inside someone's head, but you haven't yet included any human voices, I'd at least give some thought to whether a word here or there might help. Or maybe the words are <a href="https://www.youtube.com/watch?v=eDEceUWSCIY>only thought, not spoken aloud
? You do you.Note as well that the voice doesn't have to exist in the same timestream as the events of the narrative: think about some of the retrospective commentary in the NPR reading I had you do, especially the pieces featuring Steve Inskeep and Robert Siegel. Your narrative, that is, could also have a narrator.
And if you like any of these ideas, but don't want to deal with hearing your own voice played back, consider swapping scripts with someone else in the class!
Okay, now go to!
Set a goal
What do you want to work on today? Add it to bit.ly/cdm2025spring-notes.
Exit note
When your time is up, return to the google doc and say how far you got / set new goals for the weekend.
Homework for next time
- Aiming for 10:00pm on Sunday, but definitely by Monday at noon, complete – at least for now – your audio narrative. Your repository (on GitHub, ideally, or in a Box/OneDrive folder shared to me as a fallback) should include:
- Your most up-to-date layered Audacity project file (.aup3)
- A flattened, playable export (.mp3)
- A series, now, of screenshots showing your Audacity project in progress. (Think about what moments are worth remembering as you go: where did you level up, or realize something, or get stuck?)
- If you need to go back, you can browse the repository at different points in the history and download the project files to reopen them – just be careful not to overwrite your current ones!
- An updated set of credits (in their own file or just the README) reflecting what you actually used, including documentation of any outside sources and your permission to use them (e.g. explicit licenses like CC – say which one – or fair use).
- If you use material with a ShareAlike license (CC-BY-SA or CC-BY-NC-SA), add a LICENSE.md file with the matching license. If you don’t have any SA material, this is optional.
- An updated README.md file introducing your audio narrative to a new audience. Give your piece a title! Make it something to live beyond this assignment, if you can. :¬)
- By Monday at noon, write a prose reflection that incorporates images from your feedback and screenshots of your Audacity project. As explained in the prompt, this should include:
- At least 500 words describing the work you did
- Your own assessment of how you met the baseline criteria and goals for the unit, as well as aspirational criteria as appropriate
- At least one screenshot of feedback you used (and please say how)
- At least two screenshots of your work in progress (ideally, related to the discussion in the previous two bullets)
- Post your reflection to the course site’s Issue queue, to make it easier to embed images.
- If you want to then copy the source code into a file in your repo called reflections.md, I won’t stop you!
- If you feel strongly that you’d rather keep your reflection private, you can email it to me instead. But my default assumption is that we learn from each other as much as from ourselves, so I hope you can find a way to write publicly about your experience with this project.
- Relatedly: Want to see a sample reflection? You could do worse than to look at the reflections by the creators of the samples you’ve already heard, e.g. Fatema Quaid’s retelling of her process on “A Haunted Halt”, Jackie Joo’s detailed breakdown of techniques on “Come Over for Dinner”, or Ben Adams’s structured assessment of “Spent on a Rainy Day.” I would point out, though, that these are all significantly longer the minimum length. That’s not necessary, or expected! But you might treat them as a maximal vision of what you could include.