[process] Listening to the book

As recently discussed [ jlake.com | LiveJournal ], I have added a step to my novel manuscript revision process. I know from experience that reading a manuscript aloud always helps me find copy editing errors, infelicitous wording, word echoes and so forth. But I also dislike reading aloud at length, and especially all by myself.

The tension between knowing what was right and being pretty strongly avoidant about it was troubling. Something had to change. After much dithering, I finally had the MacBook Air read me the entire book aloud, using the GhostReader application, as recommend by commentor rip.

The voice in GhostReader is functional but primitive. It took me a little while to get used to the flattened, mechanical tones. Then I experimented with the reading speed to see how fast I could set the playback and still be able to make notes without having to pause the application.

What I did then was open GhostReader in one window and the Word document of the manuscript of Calamity of So Long a Life in another window. I simply listened, and whenever something struck me as wrong or off, inserted [brackets] in the text. Occasionally, if the fix was very easy, like a missing simple word, I would just make the correction on the fly. I didn’t try to sort out the larger issues, just marked them for later read through.

While I suspect that reading the whole manuscript aloud would have been more effective, I think I got 80% of the value of the readaloud by listening to GhostReader without wearing out either my voice or my patience. Also, this meant I could work on the book in public spaces and on airplanes without looking like a crazy person. Even coffee shops, despite what [info]scalzi says about that.

One of the minor problems of the process was when I went back through the manuscript, sometimes I’d have trouble figuring out why I marked a section. The answer to that, of course, was just to read it aloud to myself. Another minor problem was sometimes I’d go on a word hunt when I’d realized I’d used a crutch word, and then hit that point of neural fatigue where the word became a meaningless string of letters and stopped making sense in situ.

I’m extremely pleased with this outcome. GhostReader (or some equivalent) will be an important part of my writing from now on. It adds a layer of time and attention to my revision process, but that layer is worth a great deal more than it costs me. If you’ve never done this, I highly recommend trying it out.

4 thoughts on “[process] Listening to the book

  1. Erin says:

    I’ve used the built-in speech function on the Mac for similar results.

  2. Chris says:

    I haven’t tried GhostReader yet, but most of today’s text-to-speech systems offer a list of voices to select from, with even more voices to download and install.
    If you don’t mind that it’s in French, have a quick glance at this video:
    http://www.youtube.com/watch?v=LUrzwpRJg10
    (Just skim through it to get the idea.)
    Not all the voices seem monotonous to me. Some are quite lively and agreeable.

    As for inserting brackets as reminders: Wouldn’t it be much easier and faster to use just the mouse and the text processing software’s highlight function? I am using LibreOffice, but it seems unlikely that Word should not have a similar, perhaps even better feature. Besides, a red or yellow patch of color is much less likely to accidentally remain in the final revision than a pair of brackets.

    1. Jay says:

      I don’t know how to do a “find” on a colored highlight in word. I can find [brackets]. 🙂

  3. Chris says:

    It seems that Word has a ‘find next highlight’ feature

    http://cybertext.wordpress.com/2010/01/25/word-find-highlighted-text/

    (2nd alternative), but it is only now that I fully realize how this whole blog is built on [brackets]. 🙂

Comments are closed.