Newbie Guide to Recording

This guide is to help volunteers get started with the recording process. We understand that technical knowledge among volunteers vary, so we have tried to make this guide as clear and comprehensive as possible.

Getting Ready

In order to be able to record, you will need a microphone and a recording software. The typical recording setup used by most volunteers at LibriVox is a USB mic plugged into a computer running the free audio program, Audacity.

Hardware

Main article: User-Recommended Equipment

In order to record, you will need a computer and a recording device, which can either be a microphone that plugs into your computer or a digital recorder.

1. Microphones: Microphones can be analog or digital. An analog mic will plug into the soundcard (plug goes into the pink round jack), the performance of the mic will be affected by the quality of your sound card. A digital mic plugs into the USB port and bypasses the sound card, which will give you much better sound quality.
   1. Desktop microphone: A desktop mic sits on your desk. Perhaps the cheapest mic widely used at LV is the Logitech USB desktop microphone (PN 980186-0403) for about $30US - very satisfactory for the price!
      Opinion: the sound is more digital and not so rich as the Samson mics ($50-90), but it's not so edgy or harsh as the headset models. A recommended first, economy mic.
      The Samson mic is a popular "upgrade" among volunteers who love recording. (Q1U ~$50US, C01U about $90US)
   2. Headset microphone: The Logitech headsets are very widely used (especially the 250 for ~$40US; and the 350 for ~$50US; the models are proliferating). Some models are surprisingly uncomfortable to wear (the 250), but some folks like the headset convenience for keeping the mic location consistent and the hands free.
      Opinion: the sound is inferior to the cheaper, desktop mic by Logitech. For the extra money, consider investing in a higher quality Samson mic.
2. Digital recorder: When opting for a digital recorder, you should always pay attention to what format it supports. If you need to transfer the files into a audio editor for editing, you should make sure that the formats are supported by your editing software. Also, the recorder should be able to provide a reasonable audio quality.

Software

Main article: Audacity 1-2-3

Most LV volunteers use Audacity. The last stable version is 1.2.6 but we suggest you use the beta version, 1.3.6, as it has several improved features. Although it might not be as stable as 1.2.6, some volunteers only routinely use the Beta version without encountering any problems.

• Please consult Audacity 1-2-3 for a guide to help you step-by-step: download, install, and test Audacity with a first recording. If you have a built-in mic, try it out. If you have ordered a microphone online and are waiting for it, you can download and install Audacity while you're waiting for the mic to arrive.

Some volunteers use GarageBand, or Wavepad.

See Software We Use for other recommendations and some tips about software you may already have.

|NOTE: Many people worry that they are not 'technical' enough to manage the recording side of things. But it isn't that difficult - else there wouldn't be so many of us doing it! The vast majority of LibriVox volunteers do not have a technical background.

Some folks use other recording setups, but this guide focuses on the most direct route to recording for LibriVox -- recording into a computer, editing on a computer, and sending files over the Internet.

Preliminary Test

Main article: 1-Minute Test

Before you make your first long recording, we suggest you either record a 1-minute test, or post a contribution to the Weekly Poetry, or the Short Poetry Collection. This will enable us to give you quick feedback, to make sure everything is correct.

If you need or would like some feedback on your technical setup, it's a good idea to start by submitting a 1-Minute Test to the "Listeners & Editors wanted" subforum for constructive criticism (CC).

Signing Up

1. Read through the sub-fora in the section "Volunteers Wanted" to find a collaborative project that interests you. There are numerous collaborative projects open and looking for readers at any time of the day or night, in numerous languages:
   1. Readers Wanted: Short Works and Poetry: this usually includes a Poetry Collection and a Short Story Collection, but also things like a Short Mystery Collection, Short Ghost Story Collection, Short Non-Fiction Collection and many many more. For most of these collections, readers can pick a poem, story or essay of their own choice to contribute.
   2. Readers Wanted: Books: whole books being recorded by multiple readers, where you can contribute one or more chapters.
   3. Readers Wanted: Dramatic Works: plays or dramatic recordings of books, where you can contribute in the cast.
2. Carefully read the first post in the thread of the project that interests you - this contains all detailed instructions specific to this project, and shows you which sections or parts are still available.
3. Hit "Post Reply" at the top left of your screen. This will add a post to the 'thread.' Leave a message for the Book Coordinator indicating which part you'd like to read, and check back later for the reply. The Book Coordinator will leave a reply for you in the same manner, and tell you that you have successfully 'claimed' the part.

• Please Note: It is recommended that you do not put any important information in the subject line of your reply to a post. You'll notice throughout the forum, that the subject line is so small that no one sees the subjects of individual replies. If, for example, you put the chapter number you would like to claim in the subject line, and not the post, your book coordinator will likely have no clue what you're talking about.

• For many of the collections in the "Short Works" forum, you do not need to 'claim' anything. Just follow the instructions in the first post, and pick a poem, story or essay you like (as long as it's in the public domain).

Recording

Double check your recording setup

Take a minute (please) at the beginning of each recording session to check your setup. Computers return to defaults (wah!) and microphones move. Usually you have to adjust something a little to get back to your equipment's best recording setup (we are not aiming at perfection, though).

1. Plug in your microphone before you open your recording software
2. Open your recording software
3. Check your input volume and microphone selection
4. Double-check your settings
5. Record a wee something ("Peter Piper packed a paper pumpkin. Thank you thirty thousand thanks. Fine fun on the forums, fortunately.")
6. Look at the waveform:
   1. is it tiny? (increase input volume or speak closer to the mic)
   2. is it clipped? (decrease the input volume or back away from the mic a bit. A clipped waveform is flattened at top and bottom -- clipping causes distorted sound)
7. Listen to the recording (ideally on headphones)
   1. got plosives? (move the mic outside the stream of breath, above/below/side)

Prepare all your text to be recorded

We recommend you download the text from its online link given in the project's top post. It helps to save the text to your computer and add any information you need to read; it's all in the top post in your project, but it's very very handy to copy and paste all that you need to record into a single document with the text. For instance:

• Intros/outros: Chapter and title, LibriVox "disclaimer," full book title and author's (and translator's) name, chapter number and title, and any other important intro information. (It's a little different for poems!) ... text ... End of such-and-such, etc.
• Personal notes, like how to pronounce a word you're not familiar with
• ID3 tags for your particular reading
• what to name your recorded file
• where to send your recorded file
• It's all in the project's top post; if you can't find or don't understand something, ask the Book Coordinator (BC) or Meta Coordinator (MC).

If you would like to spruce up text from Gutenberg (most of our projects use Gutenberg text), you might like this: Guten Mark

Record

Get a glass of warm water or herbal tea, and enjoy yourself. (Thanks for recording for LibriVox!) If you've followed the steps above, you should have everything you need: all the text and intros and outros and file specs (all from the project's top post).

• Remember to save along the way -- it is very frustrating to lose a whole chapter because the software crashes (possibly because the file has not been saved and is taking too much temporary memory) three paragraphs from the end. Sad, very sad.

• Important: read the authorized text only. Other editions may be in copyright and we rely on folks to use the Public Domain versions (as identified in the project's top post).

TIPS: There are a few things that you can do while you're recording to make the editing process more easy later on. As soon as you make a mistake tap the mic three times, or say a really loud "MISTAKE!". Then repeat the sentence that you goofed up. The point is to create a spike in the sound waves of your editing software. This allows you to more easily find your mistakes in the editing process. Make a test recording to be sure your mic and editing software is set at the correct volume before recording the text. It is possible to alter the volume later, but raising the volume too much will also amplify the background noise. Don't stop the recording for anything. If you need to get a drink of water, let it record through that. Need to clear your throat? Keep recording so you end up with one long track. This will prevent inconsistencies in sound or volume. If you stop recording and return later, it will probably be obvious to the listener that you stopped and started again later.

Follow this link for more tips to Improve Your Recording.

Editing

Main articles: Audio Processing Concepts and Editing Audio

You will make mistakes in your reading, there is no doubt about that. Don't worry about the mistakes too much as you're recording, because they can be edited out. You can also make adjustments to volume, and remove small amounts of background noise in the editing process.

The editing step usually involves 2 concepts: Fixing mistakes, and Audio Processing.

1. Editing Audio: This part usually involves deleting, cutting, copying, and pasting. For instance, if you misread a word, and re-read it, you will need to delete the section with the mistake. Cutting, copying and pasting are used much less frequently. the most common occurrence of which would be to copy and paste silences.
2. Audio Processing: This refers to filters and other effects applied to the entire track or a selection, and changes how the recording sounds. The most commonly used effects are Amplify (or Normalize) and Noise Removal. More experienced users might further process their recordings, using BassBoost, Leveller, Compressor, etc.

Most readers edit their own recordings. A great benefit comes from that, besides the obvious benefit of having a corrected file: the more you record and edit, the more (almost unconsciously) you'll find yourself making little adjustments to your reading style and to your recording setup that make the whole process more enjoyable.

• See this great Audacity Tutorial for basics of editing in Audacity, the free recording/editing software used by most LibriVoxers
• Here are some tutorials for common edits in Audacity: Audacity Tutorials
• Check the Audacity FAQ

Exporting

Once you are satisfied with your recording, it is time to export it, or, basically, save it as an mp3. In order to do this, you must have the LAME plugin successfully installed. In Audacity, this is done by going through the following steps:

1. Go to File > Export... A dialog box will open.
2. Choose the folder in which you want to save your file.
3. Type in the file name. Please make sure to follow exactly the format presented in the first post. Use all lowercase, and DO NOT put any spaces in the file name.
4. If using Audacity 1.3, click Options... and make sure that you have the correct export settings:
   - Bit Rate Mode: Constant
   - Quality: 128 kbps
5. Click Save
6. A dialog box should open, so that you can put in the ID3 tags. (NOTE: in some versions of Audacity, you will NOT be prompted with the ID3 tags dialog after clicking Save. In these cases, you will have to open the ID3 dialog and insert the tags BEFORE exporting. Do this by going to File > Metadata Editor.)
   1. Fill in the information in the required fields: Author, Track title, and Album title, EXACTLY as they are presented in the first post.
   2. You may add "Recorded by (your name)" in the Comments field.
   3. Click OK.

Audacity should then start exporting, and may take a few minutes.

Uploading

Main article: How to Send Your Recording

Unless the top post of your project requests a different method, please use the LV Uploader:

http://upload.librivox.org

|UPLOAD LOGIN PIC|

(If you have trouble reading the image above, please message an admin)

• Before you upload, you'll have to select the project MC's name from a list so your file will go to the right folder. (That's the Meta-Coordinator, MC, not the Book Coordinator, BC -- they can be two different people.) If you're sending a test file, follow your BC's instructions or call it yourname.mp3 and select "xx - Non-project files" from the uploader's MC drop-down list.
  • How to find the project's MC: Each project thread title has the MC initials at the end. Example: "[SCIENCE] The Voyage of the Beagle by Darwin - ks" Find those initials in the Uploader's drop-down list of MCs (in this example: "ks - gypsygirl")
• When the upload is complete, a link to your file will appear.

Posting

After the uploader gives you the link to your recording, you should copy the link and post it (as a reply) in the project thread to let your Book Coordinator know you're done. Please avoid sending the link to the BC or MC as a Private Message. Folks will use that link to prooflisten your file and later to catalogue your file. When posting the link, remember to include the section number (if you have claimed many sections) and the length in minutes:seconds of your recording.

If this is your first contribution, let the BC know how you would like to be credited on the Catalog page, and your Web site if you would like that with your credit.

Editing After Prooflistening

All recordings are "prooflistened" to catch repeats, big stumbles or long pauses. For some specific projects, the recording is even checked against the text. The notes from the "proof-listener" will be posted in the project thread or in a specific prooflistening thread for the project. For more information, see Guides for Prooflisteners. Keep an eye on the status of your recording once in a while, in the "Magic Window" of your project.

• If the prooflistener caught some mistakes, his/her notes will be entered here. Please edit your recording and resubmit the new version.
• If the recording is marked "PL-OK" or just "OK", it means that it is all set for cataloging as soon as the whole project is done. No further action from you is required.

Once the project is complete, it will be catalogued. You may want to know what will happen to your file when you've sent it to your coordinator! Here's an overview of the LibriVox recording process and some other useful information.

After Your First Contribution

You have done it! You have contributed a recording! If you enjoyed doing that, please come back for more. You have several options now:

1. Contribute another section to a collaborative project, as detailed above.
2. Launch your very own project - see the New Projects Launch Pad. Read the stickies there for details on how to do this. Your options are:
   1. Going Solo: record a whole book on your own. (Note for first-time recorders: Reading a whole book, as many of us have discovered, is often more time-consuming than one thinks. We therefore strongly encourage you to read a chapter for one of our collaborative projects before you start a solo project.)
   2. Become the book coordinator of a collaborative project: book, play or short works collection. See also How To Become A Book Coordinator.