This week’s big news in books, of course, was the official unveiling of the Kindle 2, Amazon’s second-generation ebook reader. Michael Gaudet of E-reads offers his appraisal, noting some of the new Kindle’s enhancements:
- slimmer, with more memory and longer battery life
- faster screen refresh
- redesigned buttons for navigation
- faster book downloads, and “Whispersync” to keep multiple Kindles synchronized wirelessly
- a text-to-speech voice synthesizer, to read your books aloud to you
These all sound like pretty nice enhancements. But as I look at the device, I’m not regretting my choice of the Sony PRS-700. The built-in light and the touchscreen on the Sony still put it way out in front, in my book (so to speak).
But the Kindle announcement hasn’t come without blowback. “They don’t have the right to read a book out loud,” said Paul Aiken, executive director of the Authors Guild. “That’s an audio right, which is derivative under copyright law.” (From the Wall Street Journal online.)
I’m a member of the Authors Guild, and I was a little horrified to hear Mr. Aiken make this claim—because to my way of thinking, having a Kindle (or any device) read a file aloud should be no different in copyright terms from my reading a book aloud to my family. I mean, really.
And yet, I understand why he made the statement. Authors often license audio rights separately from other rights. There’s a natural concern about anything that could cut into audiobook sales. But to me, there’s a big difference between a machine reading of a stream of text and a professionally produced audio reading by a professional reader who gives the reading inflection and expression, perhaps with the help of music and sound effects. Now, it may well be that some people who like audio books will forego buying audiobooks if their Kindle will read text aloud in a computer voice. (Given that Amazon owns Audible, I imagine there were some in-house discussions about this.) So clearly this is an arguable point. But I still don’t agree with Mr. Aiken, even though he speaks for my organization.
I’ve been frustrated for years that read-aloud is disabled on my own ebooks sold through outlets such as fictionwise.com (a retailer I am otherwise very happy with, I hasten to add). The only format, until now, in which this was relevant was Microsoft Reader format, because only MS Reader had that capability. I’ve always felt that if people bought my ebooks and they preferred (or needed) to listen to it through a computer-synthesized voice, they should have that choice. Why not? They bought the book. It turns out that the disabling of this feature is the policy of Fictionwise. But I wonder now, in light of the statement from the Authors Guild, if maybe it’s based on fear of backlash from publishers who might see text-to-speech as an infringement of audio rights.
What a crazy business. I suppose one day computer synthesized voices, combined with AI-comprehension of a book’s content, could produce a sufficiently expressive reading that it might compete with a true audiobook. But that seems unlikely in the foreseeable future.
For now, my basic position is, whatever gets people buying and reading books (both e- and p-) is probably good. Whatever gets in the way of it is almost certainly bad.
You might want to look at Fictionwise again—MS Reader read-aloud is enabled for your titles. (It's only disabled for MS Reader titles with DRM, not for their Multiformat books. They claim that for other formats read-aloud is disabled, but I don't think any of the others actually support it besides PDF—and that requires a bunch of work when creating the PDF that I suspect most publishers don't do.)
Jeffrey A. Carver
Huh. That’s odd. They used to be disabled. I guess my request that they be enabled slowly filtered through the system, and it got changed. I never noticed the change.
Thanks for the heads-up.
Re other formats supporting read-aloud, I have to assume that mobipocket does, since the Kindle now supports it. Or maybe it just does in their Kindle permutation of mobi format.
Acrobat can also read text aloud. Adobe’s e-book store used to offer you the right to “read aloud,” meaning, to use that feature, but customers generally thought Adobe was trying to control whether they read the book aloud or not. Fail.
The Kindle’s read-aloud is more a feature of the reader software than of the e-book format. The format doesn’t ship with a recording; instead, the reader software makes its best effort to figure out what pronunciations it needs to use. I wouldn’t expect good results for Clockwork Orange or Moon is a Harsh Mistress. MSFT Reader and Acrobat function similarly; in fact, on Windows they both use the same Microsoft Speech Toolkit to generate their voices.
I could see why writers with significant audio version sales might be concerned that this feature would foreclose those opportunities.
I’m not sure whether this feature is infringement, though, and software read-aloud has been important for the disabled community for years.
It will be interesting to catch James Patrick Kelly’s opinion on this feature at Boskone this weekend.
Jeffrey A. Carver
Given that Jim has built quite an audience from his audio giveaways, I’ll be surprised if he finds the Kindle feature objectionable.
There’s an interesting commentary today at http://www.engadget.com/2009/02/11/know-your-rights-does-the-kindle-2s-text-to-speech-infringe-au/. (I’ll reproduce that link in a new post and make it clickable.)
Jeffrey A. Carver
And I wonder why my books on Fictionwise are enabled for read-aloud in the Microsoft Reader format but disabled in the Adobe format. (??)
I haven’t looked at your PDFs in particular, but I thought that read-aloud only worked with files that were produced with accessibility in mind.
Jeffrey A. Carver
No, I tried the Sunborn PDF, and it reads aloud in Adobe Reader. (I haven’t tried any others.)