Mangst
|
Wikipedia ads | file info – #181 |
I'm a member of the Spoken Wikipedia project, whose goal is to create audio recordings of the articles on Wikipedia. I tend to record articles about software development and computer programming because it's what I do for a living.
I've been awarded the Audio Barnstar for updating my recorded articles.
My recordings
editHere is a complete list of all the articles I've recorded. If I've made any mistakes or if there's an article you'd like me to read, please send me an email or post a message on my Talk page (email preferred). I also review other people's recordings by request.
For a complete list of all recordings made by members of the Spoken Wikipedia project, see the Spoken Articles page.
Technology
editArticle
= article is a featured article |
Last Updated |
---|---|
NeXT |
10/16/2011 |
HTTP cookie |
5/28/2016 |
OpenBSD |
10/23/2011 |
Interactive voice response | 10/26/2011 |
Service-oriented architecture |
10/27/2011 |
VoiceXML | 10/29/2011 |
Parallel computing |
8/21/2013 |
Agile software development |
10/29/2011 |
IBM WebSphere MQ | 10/29/2011 |
JavaScript |
8/20/2013 |
Java (software platform) |
8/19/2013 |
PHP | 11/23/2011 |
Ray Kurzweil | 11/25/2011 |
Representational State Transfer | 11/25/2011 |
Functional programming | 8/25/2011 |
Computational neuroscience | 11/22/2011 |
Minecraft | 1/22/2012 |
Science
editArticle
= article is a featured article |
Last Updated |
---|---|
Iapetus (moon) |
8/22/2013 |
Enceladus (moon) |
10/24/2011 |
Titan (moon) |
10/25/2011 |
Rhea (moon) | 10/29/2011 |
Hyperion (moon) | 1/9/2010 |
Mimas (moon) | 1/10/2010 |
Pandora (moon) | 1/10/2010 |
Prometheus (moon) | 1/10/2010 |
Phoebe (moon) | 1/10/2010 |
Epimetheus (moon) | 1/11/2010 |
Janus (moon) | 1/13/2010 |
Atlas (moon) | 1/13/2010 |
Tethys (moon) | 1/14/2010 |
Telesto (moon) | 1/15/2010 |
Calypso (moon) | 1/15/2010 |
Pan (moon) | 1/16/2010 |
Daphnis (moon) | 1/16/2010 |
Aegaeon (moon) | 1/16/2010 |
Pallene (moon) | 1/16/2010 |
Methone (moon) | 1/16/2010 |
Anthe (moon) | 1/16/2010 |
Dione (moon) | 1/18/2010 |
Helene (moon) | 2/6/2010 |
Polydeuces (moon) | 2/6/2010 |
Kiviuq (moon) | 2/6/2010 |
Ijiraq (moon) | 2/6/2010 |
Siarnaq (moon) | 2/6/2010 |
Paaliaq (moon) | 2/6/2010 |
Tarqeq (moon) | 2/6/2010 |
Saturn |
8/18/2013 |
Bioinformatics | 9/20/2013 |
Connectionism | 11/26/2011 |
Neural network | 11/27/2011 |
Sequence alignment | 6/5/2012 |
Other
editArticle
= article is a featured article |
Last Updated |
---|---|
Battle of the Somme | 1/31/2009 |
ToeJam & Earl | 11/14/2009 |
Recording tips
editSoftware
editI use Audacity to make the recordings. Audacity is a free, open-source, digital audio editor that's available on all operating systems. The Spoken Wikipedia page uses this software went giving instructions on how to record articles, so I decided to use Audacity so that I could follow along with the instructions. But it works well and I have no desire to switch to anything else.
My recording process
editI usually make each recording in two or three separate sessions of about 3-4 hours each, depending on the size of the article. I find that, if I can record for long stretches of time, I get into a good "groove" and the quality of my recording increases. I start each session by getting a cup of warm water so my throat doesn't get dry (don't drink juice or soda because they have sugar, which makes your mouth produce mucus). Then, I warm up by reading a couple paragraphs of the article. Even though I'm just warming up, I still record myself talking because I find that the fact that I'm being recorded has an effect on how I speak (it makes me a little nervous). So, I record myself warming up, even though I'm just going to throw away the recorded audio.
After I've warmed up, I start the real recording. I record the article one section at a time (each Wikipedia article is divided up into a number of sections). If I make a mistake, I re-read the sentence without stopping the recording. When I finish recording the section, I stop the recording and play back the section I just read, deleting the mess-ups and correcting any other mistakes I didn't notice before. Then, I move on to the next section and repeat the process until I finish.
As I'm recording, I like to add labels to the audio file to mark where each section begins (you can do this in Audacity by pressing Ctrl-B). This makes it easier to update the recording later on because it allows me to jump right to the section I need to edit.
Once I've finished the entire article, I listen to the whole thing one more time to catch any other mistakes that slipped through. Then, I perform the following post-processing effects on the recording:
- Remove noise - Even though it's very quiet where I live, there's still a tiny bit of background noise which I can kind of hear after I've Normalized. To remove this noise, select about 5 seconds of sound where you're not talking, then go to "Effect > Noise Removal" and click the "Get Noise Profile" button. Then, select the entire audio recording by pressing Ctrl-A and go to "Effect > Noise Removal" again. This time, click "OK" to perform the noise removal using the noise profile you just created. You should definitely do this if you live somewhere noisy, like next to a busy street.
- Normalize - This will amplify everything to a good volume without making the recording sound crackly.
- Bass Boost (with a small value of about 4 dB) - This makes your voice sound sexier. :)
Then, without saving, I export the recording to an OGG file, then close the recording without saving. I don't save it because I don't want to save the post-processing effects that I made--I want to keep the recording as raw as possible so that I can reopen it later and make edits if I need to. The idea is that you should only run these post-processing steps when you're ready to export to OGG and upload the file to Wikipedia. You should never save the post-processing changes.
How to start and end an article
editBefore reading the text of the article, I start each recording by reading the article title, saying that it's from Wikipedia, then saying the date that the recording was made on (or the date the recording last updated). For example:
Neural network. From Wikipedia, the free encyclopedia, at en dot wikipedia dot org. Recorded on November 27th, 2011.
Then, I read the article introduction, followed by the table of contents. When reading the table of contents, I only read the major sections--I don't read the minor sections or the sections that I won't be reading. For example, I would only read sections 1, 2, 3, 4, 5, and 6 from the table of contents below (section numbers can be enabled by logging into Wikipedia, going to "My Preferences > Appearance" and checking "Auto-number headings"). I leave out everything else, including the sub-sections, because I feel it would overwhelm the listener:
Sections I would read from this table of contents have a "*" next to them: * 1 Overview * 2 History of the neural network analogy * 3 The brain, neural networks and computers 3.1 Neural networks and artificial intelligence 3.1.1 Background 3.1.2 Applications of natural and of artificial neural networks * 4 Neural networks and neuroscience 4.1 Types of models 4.2 Current research * 5 Architecture * 6 Criticism 7 See also 8 References 9 Further reading 10 External links
At the tail end of the recording, I state the title of the article, say that it's from Wikipedia, state the date the recording was made, and then read the licence. For example:
You have just finished listening to Neuroscience, from Wikipedia, the free encyclopedia. This article was recorded on November 27th, 2011. This sound file and all text in the article are licensed under the Creative Commons Attribution-ShareAlike 3.0 Unported License, available at http://creativecommons.org/licenses/by-sa/3.0
Some people like to also mention their names, but I don't do that.
Updating a recording
editWith every change that is made to an article, your audio recording becomes less and less accurate. Because of this, I like to update my recorded articles every six months or so to help keep my recording in-sync with the latest revision of the article.
To help me do this, I create a Word document that contains the text of the old revision (the revision I last used to record the article), with the changes that I need to make highlighted in yellow. I open the old revision from the "View History" screen, and then just copy and paste the entire webpage into Word. I then edit this document with the changes I need to make. Text that needs to be added I highlight in bright yellow, and text that needs to be removed I highlight in yellow and give the "strikethrough" formatting. It takes time to do this, but it makes updating the recording so much easier. It's worth it, trust me.
Determining what changes were made to the article can be tricky. If the article hasn't changed too much, Wikipedia's "Compare selected revisions" feature is usually enough (click on the "View History" tab, select the two revisions by clicking on the radio buttons, then click "Compare selected revisions"). However, if the article went through more complicated changes, then you're going to have to inspect each revision manually, using the "Compare selected revisions" feature only to figure out the location of each change. "Compare selected revisions" also points out changes that aren't relevant to an audio recorder, like changes related to formatting or references, so it often looks like there's more changes than there actually is.
Other tips
edit- Turn down your microphone sensitivity. Doing this will help to remove pops (from making the "p" sound), breathing sounds, and the sounds of your lips smacking together. It also helps to remove background noise. It's OK if the recording is hard to hear when you play it back--running the "Normalize" post-processing step will automatically increase the volume to a good level.
- Many Wikipedia articles contain images, and each image typically has a caption. Some Wikipedia audio recorders will go so far as to describe the image and/or read the image caption. My feeling is that this distracts from the flow of the main text, so I don't do this.