MY PROJECT WILL LITERALLY NOT SEND BECAUSE IT IS TOO LARGE I HAVE INCLUDED THE LINK BELOW TO DROPBOX

THE LINK

https://www.dropbox.com/s/pm4be2d8urytbif/BMB%20Barbershop%20FINAL.wav?dl=0https://www.dropbox.com/s/pm4be2d8urytbif/BMB%20Barbershop%20FINAL.wav?dl=0https://www.dropbox.com/s/pm4be2d8urytbif/BMB%20Barbershop%20FINAL.wav?dl=0https://www.dropbox.com/s/pm4be2d8urytbif/BMB%20Barbershop%20FINAL.wav?dl=0https://www.dropbox.com/s/pm4be2d8urytbif/BMB%20Barbershop%20FINAL.wav?dl=0https://www.dropbox.com/s/pm4be2d8urytbif/BMB%20Barbershop%20FINAL.wav?dl=0https://www.dropbox.com/s/pm4be2d8urytbif/BMB%20Barbershop%20FINAL.wav?dl=0https://www.dropbox.com/s/pm4be2d8urytbif/BMB%20Barbershop%20FINAL.wav?dl=0https://www.dropbox.com/s/pm4be2d8urytbif/BMB%20Barbershop%20FINAL.wav?dl=0https://www.dropbox.com/s/pm4be2d8urytbif/BMB%20Barbershop%20FINAL.wav?dl=0https://www.dropbox.com/s/pm4be2d8urytbif/BMB%20Barbershop%20FINAL.wav?dl=0https://www.dropbox.com/s/pm4be2d8urytbif/BMB%20Barbershop%20FINAL.wav?dl=0https://www.dropbox.com/s/pm4be2d8urytbif/BMB%20Barbershop%20FINAL.wav?dl=0https://www.dropbox.com/s/pm4be2d8urytbif/BMB%20Barbershop%20FINAL.wav?dl=0

sub sub header thingy

another one

date	what's due	expected files
Tues Jan 21	Soundscape Proposal	Thinking in writing about what you'd like to do for this assignment, posted to the appropriate Issue Queue. This post should include: some basic premise of your narrative; some sense of setting; and a link to your repository, which is the fork of this assignment. In addition, please add a new file to your repo called ASSETS.md, containing a prospective assets chart as per Writer/Designer p. 149. Not sure where to start? Try one of the "parachute prompts" below.
Thurs Jan 23	Soundscape Preview	An early snapshot of your progress, to get the gears turning. Turn in: 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, now with the files you 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).
Tues Jan 28	Soundscape Draft	A solid attempt at a complete soundscape narrative, ideally at the target length. Turn in: A layered Audacity project file (.aup), showing the arrangement of your sounds so far The _data folder associated with your Audacity file, containing your audio snippets. At least one more static screenshot (.png or .jpg) of your Audacity file in progress. When to screenshot? Moments that seem worth remembering as you go: where did you level up, or realize something, or get stuck? An updated README.md file, introducing the soundscape narrative to a new audience. An updated ASSETS.md file, including documentation of any outside sources – and your permission to use them (e.g. licenses, fair use); see Writer/Designer p. 160-165.
Sun Feb 2	Soundscape Final Draft	Include the same five components as in the earlier draft, but updated.
Tues Feb 4	Soundscape Reflection	Give a sense of the work you put into your soundscape and whether it accomplishes what you wanted it to. Turn in: at least 500 words describing the work you did at least two screenshots showing your work in progress at least one photograph of a notecard with feedback that you responded to in revising (and please say how) your own assessment of how you met the baseline criteria for the class, as well as aspirational criteria as appropriate Post your reflections 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 own repo called reflections.md, I won't stop you!)

Setup

1. Fork this repository to create a new version you can control.
2. This will give you an online copy, but for editing purposes you'll definitely want a local copy on your computer. Follow the cloning instructions for your operating system, making sure to put the cloned folder in a place on your computer where you can easily find it.
3. Optional: Because some sound files can take up a lot of space, you may want to use Git Large File Storage, an add-on service that lets you designate certain file extensions as worth tracking and storing off-site, rather than directly in your repository.
   • If you want to do this, it's pretty easy! You'll just need to install the LFS service at the command line to make it work.
   • Simply go to https://git-lfs.github.com, download, and follow the two steps on the screen!
   • Once it's set up at the command line, git-lfs will also work through GitHub Desktop.

Parachute Prompts

As it says above, the genre, subject, and setting for this project are up to you. But if you're stuck for where to start, try one of these options:

• Day in the Life of... Over the course of a few days, record 40 or more 5-second snippets of sound that tell us where you are and what you're doing. (The challenge will be to make at least some of these sounds different from everyone else's: parts of a particular soundscape, not a generic one.) Overlay a soundtrack that shows your energy – or the energy you'd like to have; fiction is fair game, after all – at various times of day. Human voices, including yours, are welcome!
• Interview for a Podcast You know that one friend or family member who's always telling great stories? Ask them for a new one, or to re-tell one of your favorites, and this time, get it on "tape." Record more than you'll need, then go to the editing room to recreate the story in sound: boil it down to highlights, introduce your speaker and yourself, then add a background track and incidentals to round out the sonic atmosphere.