Features/Text To Speech In The Toolkit: Difference between revisions

Godiard (talk | contribs)
Created page with "<noinclude> Category:Feature Page Incomplete TextToSpeechInTheToolkit </noinclude> == Summary == Sugar have a global text to speech feature, you can..."
 
Godiard (talk | contribs)
No edit summary
 
(7 intermediate revisions by 2 users not shown)
Line 1: Line 1:
<noinclude>
<noinclude>
[[Category:Feature Page Incomplete]]
[[Category:FeatureLanded|TextToSpeechInTheToolkit]]
[[Category:Feature|TextToSpeechInTheToolkit]]
</noinclude>
</noinclude>


Line 24: Line 23:
== Detailed Description ==
== Detailed Description ==


These are the functionalities needed by the activities
say(text,[voice], [pitch], [rate])
:voice, pitch and rate are optionals, if not set use the default values configured.
:Return a id to enable pause and stop
:We will need some type of notification when the TTS finished playing. In this way we can change the state of buttons, and start a new text,
by example when have long texts, we can send it by parts.
pause(id)
stop(id)
get_languages()
:Return array of translated language names (to show in the UI),
:and the voice name related in the backend. 
get_voice(lang)
:lang is a language code
:Return the best voice name available for the language.
=== Activities using TTS ===
* Clock
:say the time in the default voice
* Memorize
:user can select the language and the game say text in the selected voice.
:games based on Art4apps do TTS if a sound file is not available.
* Read
:The user can select a languages from a list and make the activity do TTS on the text using that voice
:The user can pause and stop
* Speak
:The user can select a languages from a list, pitch and rate, and make the activity do TTS on the text using that voice
:The user can pause and stop
* Story
* TurtleBlocks
* Write
:The user can select a languages from a list and make the activity do TTS on the text using that voice
:The user can pause and stop


== Benefit to Sugar ==
== Benefit to Sugar ==


Easier implementation of TTS in activities. Faster startup of activities.
Easier implementation of TTS in activities. Right now, there are a lot of code,
usually implementing TTS with more than one backend, and with code copied from other activities.
 
Faster startup of activities. Initialize gstreamer takes a substantial time.


== Scope ==
== Scope ==