oohoo - Text to Speech

Blocks ::: block_tts
Maintained by Patrick Thibaudeau, Nicolas Bretin
OOHOO Text to Speech is a Moodle block that reads outloud the content of a resource
Latest release:
97 sites
23 downloads
17 fans
Current versions available: 1

This block adds text to speech functionality to Moodle

It can be configured to use either the Google speech engine or the Microsoft speech engine. When added to a resource such as a page, it reads the contents.

There is also a lexicon to add pronunciations for words that it pronounces improperly. For example, it could possibly say I.V. for the text IV. It should, however, say 4. You could add in the lexicon IV = four and it willpronounce it properly.

 

A special thank you to Ryan Thomas who is the original author of this block.

Screenshots

Screenshot #0
Screenshot #1

Contributors

Patrick Thibaudeau (Lead maintainer)
Nicolas Bretin: Developer
Please login to view contributors details and/or to contact them

Comments RSS

Comments

  • tong adam
    Wed, 3 Apr 2013, 4:22 PM
    it only works for English, right? I tried other language but didn't work. Although Google TTS support multiple languages. Also, will it be ready for Moodle 2.5? I tried it in Moodle 2.5 dev but not work.
    Thank you.
  • Nicolas Bretin
    Thu, 4 Apr 2013, 12:01 AM
    Hi,
    It should be working for other languages, at least for English, French, Spanish, Italian and German.
    The languages pack for the desired language must be installed on the Moodle server and the language must be the active one on the current page.
    For example, you forced the Italian for a course so the whole interface is in Italian and the TTS will read the text in Italian.
    If you choose Microsoft for the TTS, you will probably have more languages available!

    Concerning Moodle 2.5, we didn't try our plugins yet but we will test and update them for the official release date, just give us a month.

    Don't hesitate if you need more info,

    Thanks,

    Nicolas
  • Roland Sherwood
    Thu, 18 Apr 2013, 12:13 AM
    Many thanks for making this block available; in terms of accessibility, it really is a life-saver for some of our users. One quick query: for some reason (possibly javascript related?) the block doesn't seem to function when using the Bootstrap theme (v. 2013032800 - available via: https://moodle.org/plugins/view.php?plugin=theme_bootstrap ). Previously, I thought the issue might be related to the inclusion of jquery within Bootstrap, but that's been replaced with YUI support in the latest version and still the problem persists. It does work properly under any of the current core themes in 2.4 - just not Bootstrap. Any insight you could offer as regards this issue would be much appreciated.
  • Nicolas Bretin
    Thu, 18 Apr 2013, 1:13 AM
    Hi Roland,

    The TTS block search for the element with ID="region-main" in the HTML structure. Unfortunately, bootstrap rename this div ID with "region-bs-main" so the TTS doesn't find the element and stop here.

    The solutions are:
    Short term fix will be:
    - You can modify the value directly in the TTS code, in the file "tts/app/_php/config.php => define("SELECTOR", "#region-main");
    - You can try to overwrite this constant in an other php file in order to not modify the TTS file.

    Medium term fix will be:
    - You can ask bootstrap developers to change the tag name of region-bs-main
    - We can add an option on the configuration of the TTS with the name of the main block.

    Nicolas
  • tim wilde
    Thu, 18 Apr 2013, 2:19 PM
    Hi Nicolas, Re my post 8 March, 16:42 and your reply 18 March, 23:59

    We are still experiencing issues with the TTS plugin. I add it to a course and when I display the page the plugin just spins and is grey out. You can see an example here
    http://sli.perceptiveits.com.au/course/view.php?id=146

    The above account has guest access enabled and the site is in debug mode.

    This is a test site, but I have the same problem on two sites on different servers and as yet have not managed to get it to work on any site.

    Is there any additional logging/debugging that I can perform?

    Any help would be appreciated

    Thanks

    Tim
  • tim wilde
    Thu, 18 Apr 2013, 2:25 PM
    PS am I running TTS release = '1.0.3 (Build: 2012121400) and Moodle 2.2.7+ (Build: 20130118). http://sli.perceptiveits.com.au/blocks/tts/tts_test.php runs fine. Thanks
  • tim wilde
    Thu, 18 Apr 2013, 4:42 PM

    tim wilde
    -
    18 April, 16:32





    More clues!. I have added it to a normal site page (not a course) here

    http://sli.perceptiveits.com.au/mod/page/view.php?id=2390

    and it does not spin this time but there is no volume bar and it does not play anything. Hopefully this will provide more clues!. Thanks
  • Roland Sherwood
    Thu, 18 Apr 2013, 10:34 PM
    Many thanks for the info and workaround suggestions, Nicolas - much appreciated. Just to confirm also that I'll pass on details of the issue to the Bootstrap devs in order to see if they can come up with a resolution. However, if they're not able/willing to - and since Bootstrap will be a core theme under 2.5 (which, presumably, means its use will grow considerably) - it would be great also if you were able to implement a renaming option within the settings of the TTS block. Either way, many thanks again for your help.
  • Nicolas Bretin
    Thu, 18 Apr 2013, 10:40 PM
    Hi Tim,

    I have an error 500 http://sli.perceptiveits.com.au/blocks/tts/tts_test.php.

    Otherwise I saw that you have jQuery in your theme. TTS uses jQuery so one problem could be a conflict. That explains why the volume bar does not exists.

    Nicolas
  • Nicolas Bretin
    Thu, 18 Apr 2013, 10:46 PM
    Hi Roland,

    Yes for Moodle 2.5 if Bootstrap team doesn't update the code we will add a setting.
    But I'm curious why they change the tags names. Every other theme has this structure.

    Nicolas
  • Nicolas Bretin
    Thu, 18 Apr 2013, 10:46 PM
    Hi Roland,

    Yes for Moodle 2.5 if Bootstrap team doesn't update the code we will add a setting.
    But I'm curious why they change the tags names. Every other theme has this structure.

    Nicolas
  • Roland Sherwood
    Thu, 18 Apr 2013, 11:25 PM
    Hi Nicolas. Yes, I'm curious also as I would have thought themes need to adhere to certain standards in order for core and third-party features to function properly. Either way, I've now raised the issue and will drop a reply here when I hear back from them.
  • tim wilde
    Thu, 18 Apr 2013, 11:36 PM
    Thanks Nicolas, The 500 error is an intermittent test server error.If you refresh the page some reason it disappears. I have changed the theme to “afterburner” and I still experience the same problems.

    http://sli.perceptiveits.com.au/course/view.php?id=146

    Any debugging clues would be appreciated. Thanks
  • Nicolas Bretin
    Thu, 18 Apr 2013, 11:57 PM
    I still have the 500 error on the tts test page.
    To help me debugging, can you try to activate Firebug in Firefox and tell me if you have javascript error and what is the response of the first GET request (something like http://sli.perceptiveits.com.au/blocks/tts/app/_php/tts_config.php?courseid=146&service=microsoft&voice=en&_=1366300633688) in the console tab ?
    Thanks,
  • tim wilde
    Fri, 19 Apr 2013, 2:33 PM
    Hi Nicolas

    I think we should ignore the test server as it may be giving us spurious 500 errors.

    Please see the live server here http://smartmove.moodle.com.au/course/view.php?id=3
    and the TTS test results here
    http://smartmove.moodle.com.au/blocks/tts/tts_test.php
    Do you still get the 500 errors? It runs clean from this end.

    The results of Firebug are here
    http://smartmove.moodle.com.au/misc/TTSlog.txt

    I have tested as follows
    Different servers. Same problem.
    Different theme. Same problem.
    Different Moodle Versions. Same problem
    Different Browsers FireFox, IE and Chrome. Same problem.
    Different machines. Same problem

    I am running out of ideas and hope that the Firebug log file will provide more clues!

    Thanks for your help

    Tim
Please login to post comments