Transcribing linguistic data: bottlenecks and one way to speed up

Transient Languages & Cultures published a nice post by Peter Austin last month on the question of how much time it takes to transcribe linguistic data. Working under tight time constraints during some recent fieldtrips, I found one way to speed the process up. It still takes an awful lot of time, but here goes.

In my experience, two very important bottlenecks in transcription, especially of conversational material, are (1) initial recognition (what exactly was said?), and (2) writing it down (how quickly can this be written down in the orthography you have chosen?). In my field situation (a Siwu-speaking village in eastern Ghana with few literate and even fewer computer-literate people), I don’t have someone (yet) who could do the actual transcribing, which is usually done directly in ELAN, so I am responsible for bottleneck #2 (getting it into the computer).

As regards the first bottleneck, for a native speaker it is much, much easier to ‘hear’ a fuller form of conversational speech than for a non-native speaker, so it makes sense to get that kind of help for bottleneck #1. Initially therefore, I would sit down with a consultant, play a conversation utterance by utterance (I would have done the segmentation in ELAN beforehand), and have the consultant repeat the speech while I wrote it down. For bottleneck #2 reasons this often meant replaying the same utterance multiple times. I soon realized that this was a waste of time for my consultant, who would patiently repeat two to four times what he already got right the very first time. Essentially I was using him as a tape recorder, rewinding and replaying his careful repetitions to make up for my deficiencies in short-term memory and typing speed! So here is what I did to speed up the process:

  1. Presegment the conversation in utterances in ELAN.
  2. Go through it a first time, utterance by utterance, and record the consultant’s carefully pronounced repetition of each utterance.
  3. Get the results of 2 (tens to hundreds of small audio files) onto the computer, batch rename them if needed (I always include at least date and speaker ID in the filename), and put them in a media library that allows quick and easy file selection and playback (I used WinAMP).
  4. With that material in hand (essentially slurred and non-slurred versions of utterances) do a first rough transcription. No need to bother the consultant during this time-consuming process.
  5. Mark all the problematic points and get back to the consultant for a final check.

During my last fieldtrip, my main consultant had to study a lot for his final exams. The above modus operandi turned out to be a win-win situation. He provided me with carefully pronounced utterances (we would get so good at this that we nearly achieved real-time speeds), and I provided him with a place to study in my improvised office on a shadowy compound. So after an initial intense recording session, he would spend the afternoon learning while I would put my headphones on to do the first transcription, which was a breeze with his crystal-clear repetions (which included whistled tone patterns if needed!). Hours later, the final check would be a matter of minutes and we would be ready to enjoy our well-earned fufu in palmnut soup with goat meat — surely the best part of the whole transcription process!

4 thoughts on “Transcribing linguistic data: bottlenecks and one way to speed up

  1. Pingback: Tweets that mention Transcribing linguistic data: bottlenecks and one way to speed up — The Ideophone -- Topsy.com

  2. Thanks for sharing, Mark! Still sounds like a lot of work… By the way, downloaded WinAmp and am still asking myself what the advantage is of having my soundfiles organized there?

  3. WinAmp is not essential; just happens to be the media player I use, and it has useful hotkeys for pausing and skipping around files while transcribing (no screen/mouse work needed, so you can focus on the transcription screen). But any media player that can do that would work.

  4. Thanks for the details, Mark. I’d never considered a re-recording, but in some cases I’ll bet it would work better than what I’m doing.

    BTW, I use the “partitur-editor” from EXMARaLDA for transcriptions. I find it very useful, but I’m not familiar with other tools, so can’t speak to advantages/disadv. over, say, ELAN.

    Good to see you’re back blogging, btw!

Leave a Reply

Your email address will not be published. Required fields are marked *