Forward the Soundscape Foundation (Intro to Audacity)
- Welcome back, and thanks for posting! (5 min)
- Audacity Demo (10 min)
- Audacity Play Time (20 min)
- Command line redux: Versioning beyond GitHub (10 min)
- Share and Enjoy (15 min)
- HW Preview
- EXT: Studio time and microconferences
1. Welcome back, and thanks for posting!
Many thanks to everyone for keeping the conversation going online, even when we weren’t meeting face-to-face. I’ve read through all the posts as of 9pm last night, on both threads: the blog post on listening to soundscapes and your soundscape narrative proposals.
Lots of overlap and plenty of difference in the proposals, which is always a good thing. A bunch of you are working on days-in-the-life-of; you might find that you’re able to divide and conquer some of the standard sounds, like pouring coffee or turning on a shower. Have a look through the queue and reach out to each other if you want to trade!
This is also, of course, a good reminder to try to find ways of making your story your story, even as it takes on the conventions of a particular genre. If your proposal is focused on routine, what stories does your routine allow you to tell? If it’s a game or a performance, what will draw listeners to this particular game or performance?
Remember, as well, that one tool you have in your toolkit is music, especially open-licensed music. The resources page of our website has lots of links and suggestions; please do make use of them!
2. Audacity Demo (10 min)
I’m going to quickly walk through the basic features of Audacity, and then you’re going to try your own hand at using them.
Import. Lay of the land.
Visual rendering of sound.
Select tool; zoom tool.
Play a loop. Zoom. Selection adjust. Add label at selection.
Time shift tool.
Split vs. split new. Mute/solo tracks.
Save vs. export.
A project is an index to a folder full of sounds. You definitely want to save this! But to make it playable outside Audacity (and also a lot more transportable), export to mp3.
3. Audacity Play Time: Representative and Reprehensible Reporting
Your turn! Your mission is to produce two short clips (≤15 seconds) from the same 4ish-minute audio file, which I’m about to give you.
We’ll share these among each other, but not post to GitHub – we don’t want any of our fake clips to circulate widely!
4. Command line redux: Versioning beyond GitHub (10 min)
Have a look at the project files you’re saving. There’s a single file with the .aup extension, and a folder ending in
_data with dozens of little .au audio clips. Trust me when I say that you do not want to upload this folder through the GitHub website. It might not even work.
Last week, we ran out of time to talk about what we get by running git from the command line. Well, here are three things:
- extended functionality
- multi-file commits
- time to problem-solve before sharing
I’ll explain in more depth:
Git, like many other applications, supports plugins and add-ons. One that we need for this class is Git Large File Storage, or git-lfs. This extension allows us to store files “offsite” (i.e. not on GitHub) that would otherwise slow down our repositories to a crawl – while still having full access to those files locally and using our normal git workflow.
- If you’re on a Mac with Homebrew, type
brew install git-lfsfrom any terminal window. (And if you’re on a Mac without Homebrew, get Homebrew! It makes life so much easier.)
- If you’re on a PC with Git for Windows, congratulations! It comes pre-installed with git-lfs.
- If you’re on Chromebook, try
crew install git-lfs, but I don’t know that it’s been ported yet. :\ You can also try the direct download at git-lfs.github.com/.
- All systems: at a command line, type
git lfs install
To set up to use with .au files:
- In the folder with your soundscape repository, enter the following, one line at a time (i.e. press enter after each line):
git pull git lfs track *.au git add .gitattributes git commit -m "track .au files with git lfs" git push
As you’re saving your Audacity projects, your
_data folder is going to be morphing and shifting, creating and deleting .au files all over the place.
When you’re ready to record a commit message – that is, when you’re ready to mark a save spot in your composing process, naming what actions you’ve just taken in your project – you can scoop up the entire folder in one go.
In the folder with your soundscape repository, enter the following, one line at a time:
git add * git commit -m "your headline commit message" -m "your optional extra details"
Now everything in the folder is labeled with that single commit. (If you want to see what’s happening, add in a
git status around each of those lines.) Keep editing, and repeat the process at your next save spot!
Time to problem-solve before Sharing
All those commits you just made are local to your computer: they’re not shared yet. So you can try things out, make mistakes, and fix them before anyone stumbles onto your project and starts making judgments about quality.
When you’re ready to push your projects to GitHub, type this in your command line (again, from the repository you want to share):
Not only will that sync to GitHub, it’ll also know which files you want to sync using Git Large File Storage, and make the transfer accordingly!
5. Share and Enjoy (15 min)
Before we have to go, let’s hear at least a few of the 15-second clips you were able to produce from our Speaker of the House!
Homework for next time:
- If you didn't yet, please finish the work above!
- Work on your soundscape narratives, including making at least two recordings and putting them into conversation in Audacity. If you have time, do more!
- Push a soundscape preview to your GitHub repository, using the steps above. As per the assignment prompt, this should include:
- A layered Audacity project file (.aup), showing the arrangement of your sounds so far (need not be a complete soundscape or narrative yet).
- A static screenshot (.png or .jpg) of your Audacity file in progress (for comparison later to subsequent drafts).
- The \_data folder associated with your Audacity file, which should contain at least two recorded sounds.
- A plain text (.txt) or markdown (.md) file, explaining in at least 300 words what you're showing us in this preview. Feel free also to ask questions or lay out next steps for yourself!
- An updated ASSETS.md, indicating which the files you've actually recorded or otherwise obtained. Add source documentation for any outside sources – and your permission to use them (e.g. licenses, fair use; see Writer/Designer p. 160-165).
EXT: Studio time and microconferences
If we have time left, I’ll be pleasantly surprised, but let’s use it to get working on your proposed soundscape narratives!