How silly is that.īoth Amazon (Android) and IOS have very advanced narrating voices for book reading. Yet, the only practical answers I read involved editing the text to add multiple commas where periods were found. I know that in MacOS it is possible to tweak this pause, and I assume that’s also possible in IOS. Both kindle Fire and IOS devices do so on commas.Īll that’s needed is for the narrator to pause at least as long, if not a bit longer, when reading a period, and insert a longer pause at the end of a sentence. Obviously, it is possible for a narrating voice to pause to reflect punctuation.
:max_bytes(150000):strip_icc()/how-to-get-siri-to-read-text-on-ios-and-macos-51184702-063bb3402f4a4f179c17a66d6c7ebf6f.jpg "siri text to speech ios")
However, I realized that both voices had the same issue: the narrating would pause appropriately on a comma, but blow right through an end of sentence period and even a end of chapter.Īssuming that Amazon and Apple use different technologies, why would both display this same annoying shortcoming and why would both ignore their users clamoring for better text to speech capabilities.Īccording to the age of the forum posts I have read, some complaints are as old as 2012. I compared the voice quality to the one in IOS and I concluded that txt2speech quality on my very cheap kindle Fire ($40) was better and more human sounding than on my much more expensive and powerful iPhone and iPad. Yet, not only there are no answers, but the original questions are so old I had to start a new thread.Ĭuriously, I found the Issue of text-to-speech pausing on commas but ignoring the pause on periods and paragraphs while experimenting on. This has been asked repeatedly and for a long time.
0 kommentar(er)
