Describe GuidesforProoflisteners here.
Guides for Prooflisteners
Click the logo on the top of any page to open the Wiki index.
Table of Contents:
Before a project enters the LibriVox Catalog, usually all its audio files are prooflistened.
* * Use the "Listen" link * *
In the top post of each project is a "Magic Box" (some say Magic Window) with a "Listen" link for every file submitted. If you click the link once, the file will load into the browser window and play. If you right-click or option-click the link and download it, you can listen to it on whatever player you prefer. The difference between a listener and a Prooflistener (PL) is that the PL will report back about any errors or gaps in the file.
Two scenarios are common for prooflistening.
Prooflisten in the Project Thread
A PL (prooflistener) spots a project of great interest and posts a message in the project thread something like, "I love this book. I'll prooflisten chapters as they come in."
This is a great boon for any project, for two reasons. 1) If an error is discovered right after a file is submitted, the reader is far more likely to still have the original editing file and can easily fix the error. 2) It's simply more fun, knowing that your file will immediately be heard as soon as you submit it.
Prooflisten in the Prooflistening Thread
A BC (book coordinator) makes a post in Listeners & Editors Wanted; and this usually happens when about half or more of the files are in. Then, typically, various listeners will claim a chapter or more and afterward post in the Listening thread, noting any problems with any files or pronouncing them OK to catalog.
An advantage of this method is that occasionally a lively discussion of the book will erupt on the Listening thread. A disadvantage of this approach is that an error may be spotted long after a reader has deleted the files; or, worse, the reader may be unavailable for making a correction (for instance, recording an accidentally omitted sentence).
Experience is teaching us the value of prooflistening files soon after they're submitted.
How to Prooflisten
The topmost thread of the Listening Forum has a lot of information:
Listeners & Editors Wanted FAQs
See also Advice from Prooflisteners.
Degrees of Prooflistening
Always check the first post for the level of proof-listening requested, or post in the thread to ask. Please do not offer feedback beyond the level requested.
In general, we ask for standard listening -- repeats and gaps:
Listen for repeated passages that the reader likely intended to edit out.
Note any long pauses or bad background noises that disrupt the flow of your listening pleasure.
It is NOT necessary for you to follow along with the text; just listen as you would normally.
A request for detailed listening would include standard and add stumbles:
Note stumbles that can be easily edited out.
A request for word-perfect (example: Einstein's Relativity) includes all of the above, and reading along:
Follow along with the Gutenberg text and note any differences between what is written and what you hear. (Note: sometimes the Gutenberg text is wrong, or differs from the edition that a reader worked from! It is important to use public domain texts. In some cases, the corrected text is actually under copyright(example: Ulysses)! If in doubt, ask the BC.)
A reader may request special feedback, and that would be whatever was asked for. (example: "Needs listeners who can understand French / Spanish / ...") The special need will be explained in the top post for that Prooflistening thread.
And some Prooflistener requests are CC - Constructive Criticism sought.
Sometimes folks would like feedback on how to improve their reading style or their recording setup -- they'll write CC at the head of their subject line and post details in the top post about what type of feedback they want.
Prooflistener Notes
A good prooflistener note gives the minute and second at which a gap or repeat or whatever occurred:
12:33 repeat, "She shells sea-- " (it's at 12 minutes, 33 seconds)
27:54 gap, about 7 seconds
In order to see the timecode, you will need to download the file and open it in something like iTunes or QuickTime. When you simply click on a file, it will often open in QuickTime in the browser window (on some computers), but that window will not show time code. If you open the QuickTime application and then open the saved audio file in QuickTime, you will see timecode.
Folks quickly learn to edit any errors in their file from last to first -- that way the timecode notes stay accurate during correction.
Feedback and Fine Lines
Please see Feedback, a LibriVox web page explaining the function of feedback in a kind and productive community.
We try to catch things like long silences, repeated text, editing problems, volume problems, static etc. But we don’t really make comments on reading style — too fast/too slow, not enough oomph. For instance, we never say: “This reader is not good enough for LibriVox.”
Our policy is to accept ANY reader who wishes to read for us. We have such a huge task ahead of us: to record all the books in the public domain! We can’t achieve that without an open door policy for everyone who wants to help. Plus, it’s part of the LibriVox way. We welcome anyone who wants to help. That’s how we got this far, and we want to go a lot further.
All that being said: WE DO CARE ABOUT THE QUALITY OF OUR RECORDINGS.
If you're ever uneasy about a file you've prooflistened, send a PM* to the Book Coordinator or Meta Coordinator (MC) or to any admin you're comfortable talking to. (*Private Message -- use the PM button at the bottom of a post by the person you want to message)
See Advice from Prooflisteners to pick up tips from peer prooflisteners, or to leave tips for your pals.