Arin - 

We've made an update to our code that should optimize response times somewhat, possibly by 10 to 15%.

Also - In our review - we see no difference in response times between your page and our TTS demo here:

www.ttsdemo.com

Please try again and let me know. The mechanism used for playback is the same so it should function the same.

You may also want to test on our Vocalware demo page. 

https://www.vocalware.com/index/demo

Vocalware uses the same platform as SitePal so the performance should also be identical to your page.

Let me know what response times you see now.

Thanx

Just to let you know this issue has moved on to engineering review.

I'll know more later this week.

Looking into it. Will advise.

Arin - 

Our best guess is that VLC installation conflicts somehow with our character playback on Safari. We could not recreate it.  To test this hypothesis - I recommend to uninstall VLC and try again. 

Let me know how goes.

Best

Gil

Arin - 

Try loading any of our support examples - e.g. - 

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

Does the character load ok in this page? or do you see the same problem?

Does the problem occur also in other browsers?  e.g. Chrome?

or is it specific to safari (on Windows)?

please advise.

Hi Arin - do you still experience this problem? 

If so - kindly respond to my questions - so that we may further assist.

Regards

Gil

Hi Arin - 

We tested on a few browsers (including Safari on Windows) but our team did not experience this problem.

We saw your character load & speak.  We need more information to be able to address this.

Try loading any of our support examples - e.g. - 

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

Does the character load ok in this page? or do you see the same problem?

Please goto supportdetails.com and send the report to support@sitepal.com, along with the link and screenshot posted above. 

This may help us identify the problem.

Thanx

Hi Arin - 

We can't immediately recreate - looking into it. Will advise.

Gil

The problem was resolved before the above message was posted.

We experienced a problem this morning with one of our database clusters. The system is designed to be failsafe, with an automated failover mechanism built-in. Unfortunately the failover did not kick in this time & our team had to manually address the problem.

We are still investigating why this happened & how to better mitigate should this happen again - and will implement improvements as needed.

Apologies for the inconvenience this has caused.