Hi Ray!

You would want to use the API callbacks to coordinate.

Check out the API Reference documentation for vh_talkEnded.

You also need to load the characters into separate iframes to be able to individually control them.

We have a code example doing so - please check it out - 

http://www.oddcast.com/support1/conversation.html

and let me know if any questions.

Best,

Gil

Hi Miral - 

SitePal is not intended to be used to generate individual audios & download them.

We have a different product for TTS Audio - see - www.vocalware.com

Vocalware Export Edition supports downloading the audios (e.g for use in your videos etc.).

Please write to sales@oddcast.com for pricing information.

Best,

Gil 

Hi Rich - 

You can use SSML tags to control the rate of speech.

Example - 

 <prosody rate="slow"> this is speaking slowly <prosody rate="fast"> this is speaking fast </prosody> back to slow </prosody>

You can also use percentage values for more precise control - 

Example - 

 <prosody rate="-25%"> this is speaking slowly <prosody rate="+25%"> this is speaking fast </prosody> back to slow </prosody>

This information & more can be found in the API reference do - see Appendix C - 

http://www.oddcast.com/support/docs/vhost_API_Reference.pdf

Note that SSML tags are only supported for voices from Engines #2 and #3.

Hope this helps,

Gil

Alex - the problem is due to the fact that the page is trying to call sayText before the user interacted with the page.

This is prohibited by the mobile browser. If you comment out the sayText calls made in vh_sceneLoaded, then the problem does not occur, and the SitePal character speaks fine on mobile when button is pressed.

That said - we will look into it further to resolve this issue and ensure that a prohibited call to sayText on mobile fails silently and does not prevent future speech.

Alex - we're looking into it - will advise asap.

Regards

Gil

Bonjour François,

The problem where the callback function vh_sceneLoaded is not called for full body characters has been fixed.

The problem with IE11 where in some cases the text is not spoken for full body characters is being investigated.

Regards

Gil

Thanx for the additional info.

We're looking into it.