Simons_Mith [OP] 2 points 6y ago
I work for a company that produces ebooks, including non-fiction and drama. When an ebook is read with the robot voice, the voice will presumably be the same for the whole book. Headings and sub-headings may get minor customisations, like pauses after they're read, but our books already do those bits correctly.
I was looking at CSS as a possible way to define different voices for different characters, and for stage directions. But if I did that, would anybody like it? Could it actually be worse than having the whole play read in one single voice? I don't want to over-customise this stuff if most robo-voice listeners would dislike the results.
Say there was a child and an adult character, and I made a childlike voice by using the CSS (that nobody supports) to raise the voice pitch and speed, and slowed the adult voice down slightly. But if you've already configured your reader to read the default voice at the fastest intelligible speed, the child-voice might cross over into unintelligibility. So while there's things I _could_ customise, (speed in this case), I need to canvas the preferences of actual users on how much customising I _should_ do.
And if you're used to a monotone generic robot voice, you might even find an increased variety of robo-voices a distraction, because they'll still remain unavoidably robot-like. On the other hand if you've got a play with a dozen characters, having them all read in the same voice could also be confusing. So, what's the best compromise? And I bet it's different again for a plain novel or a piece of non-fiction.
If I did customise the voices, how readily distinguishable would they be? Can I use CSS to make only 4 to 6 distinctive voices, or could I make 20? Are there any libraries of CSS voice settings I can refer to? There's lots of customising you can do - how much difference do all those settings actually make in practice? Are there any examples of ebooks with custom voices that I could study?
It seems like the answers to most of these questions are basically 'nothing supports that' or 'no'. So for now I'd probably do better to ask specifically about CSS support before worrying about particular implementation details. I need better support first, before I can implement the customisation I'd like to do.