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

Godiard (talk | contribs)
No edit summary
Godiard (talk | contribs)
No edit summary
 
(5 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 funcitionalities needed by the activities
These are the functionalities needed by the activities


say(text,[voice])
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
: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)
pause(id)
Line 53: Line 55:
:The user can select a languages from a list and make the activity do TTS on the text using that voice  
: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
: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
* Write
Line 60: Line 70:
== 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 ==