Sure.

But I think the existing (old) version may exhibit other problems - specifically, the issue of activation by clicking a button on the mobile page. As you yourself pointed out, in the old version, you need to touch the character to enable speech. This is one of the problems the new version resolves.

François -

I appreciate the detailed feedback.

We did not see this problem before - but the team is taking another look. Will advise.

Best,

Gil

Bonjour François -

I'm delighted to hear it!

Regarding the volume - this functionality is not supported by the browsers on mobile.

Only the user can control the volume - the browser does not enable JS code to change it.

So the call 'setPlayerVolume' on iOS does nothing. It is a mobile browser limitation.

This is mentioned in our developer API.

Regarding your experience on Android - I expect it to be the same as iOS - but according to your report it is sometimes high volume and sometimes silence. We will look into it.

Regards

Gil

Bonjour François,

I think that in the example you posted instead of attempting multiple statements in the HTML link, defined a js function and use a single call to that function. Within the function you can make multiple calls.

Regards,

Gil

I'm very glad this now works for you - and confirms our own testing. I noticed the list of problems you included in our report - and those have been added to our developers' list.

Thank you for the detailed report.

Gil

François -

Please look at the following examples again - this has been fixed and verified on iOS and Android.

Full Body -

http://www.workboy.com/qa/FB_Live/DynamicCallTTS1.html">http://www.workboy.com/qa/FB_Live/DynamicCallTTS1.html

Classic -

http://www.workboy.com/qa/3D_live/dynamictts.html">http://www.workboy.com/qa/3D_live/dynamictts.html

Regards

Gil

Francois - thanks again for your input.

We are aware that there are problems with getting the characters to dynamically respond to the API. That is why we are developing the new generation of characters - which are not yet quite ready.

Your testing and evaluation of the fv=0 (next gen) characters was premature, but we will be ready in a few days.

I will let you know and perhaps you could take another look then.

Best,

Gil

Hi François -

I tried different languages in our TTS demo - they all seem to work fine.

See -

http://www.oddcast.com/demos/tts/tts_example.php?sitepal

Why are you using the <P> tag in the text to be spoken? What are you trying to achieve?

HTML tags cannot be interpreted with the exception of documented SSML tags, and should not be used. If used, they will either be stripped and ignored, or the result might be unexpected.

Please remove these tags & try again. If you still see a problem - please post a link to your page where the problem can be seen & we will look into it.

Best,

Gil

Yes

If you use fv=0 (to view the pre-release version) it should work for you by clicking a link.

Here are a couple of examples - please try -

Full Body -

http://www.workboy.com/qa/FB_Live/DynamicCallTTS1.html

Classic -

http://www.workboy.com/qa/3D_live/dynamictts.html

Problem has been fixed.

Classic characters should now work correctly on older versions of IE (IE9 and older).

Please verify.