|
Post by Admin on Mar 7, 2015 0:26:33 GMT 1
Browsing thru the suggestions submitted by the integrated "I have an idea" widget, I found this anonymous comment:
Well yes I know that, and actually Google TTS is supported by ATR, but is only available via the "Custom commands" on the preferences page. The reason I'm not promoting Google voices into the main UI is that the limit of 100 characters is actually very noticeable. Sentences longer than 100 chars need to be broken in two or more pieces; ATR breaks the sentences at comma level or at any punctuation occurrence; still, the discontinuity is not only completely noticeable, but harassing in such a way that at every 100 chars the voice speed and tone vary to simulate the beginning of a new sentence, so the voice intonation becomes meaningless and apparently "random".
|
|
|
Post by Admin on Mar 7, 2015 0:36:10 GMT 1
Looking better at the code, Google voices can be enabled by entering this into "Custom commands":
{"voice.en": "f100", "username": "your-username", "password": "your-password"}
The problem is that breaking out of the default voices requires an authentication (username, password) but at the moment the server does not support registrations or stuff.
|
|