[writing] Being less of a chicken about the Sunspin readaloud

Apparently I am coming to grips with the reading aloud question [ jlake.com | LiveJournal ]. Yesterday I put in several hours on Calamity of So Long a Life with GhostReader, which seems to process about 45 pages per hour through its text-to-speech engine, working at a pace that I can track along with in the manuscript file.

This is both interesting and a little frustrating. I do suspect if I were reading it myself, I’d catch a few more things, but GhostReader is still helping me a lot. The flat, 1990s style computer voice borders on the distracting, and it’s not optimized for manuscript format, so scene breaks are handled a bit strangely. Still, this has gotten me past my logjam. I reckon another 12-13 hours of work to make it all the way through with GhostReader, then another few hours to clean up things as noted. Plus I need to process a couple of more sets of last-first reader feedback.

Still on track for the month end, and maybe a little earlier.

2 thoughts on “[writing] Being less of a chicken about the Sunspin readaloud

  1. Other than the export as an MP3, is it better than the built in text to speech the Mac OS has?

    1. Jay says:

      Haven’t managed to figure out how to get the Mac OS to read me a Word file…

Comments are closed.