Your comments
With the Gold plan you may upload a photo to create your own 3D character ("3D Photoface") - in the editor, select "Models" from main menu, then select 3D models tab.
Click on "Create Your own" & follow instructions.
Hope this helps,
Gil
Hello!
Yes, TTS is supported by Silver plan and up.
The differences between the plans are detailed here -
Please let me know if any questions.
Regards,
Gil
Hi Mohit -
Please send the image to support@sitepal.com - and ask that it be forwarded to me.
We'll take a look see how we can help.
Regards,
Gil
I see - you are looking to create your own character from a photo (our "photoface 3D" feature).
That's the only editor feature still requiring Flash, it will be replaced by an updated non-Flash implementation in the coming weeks.
For now - please write to support & ask for guidance how to launch the Flash editor.
There as simple steps you need to take - we will help you out.
Best,
Gil
Hi Mohit -
Flash is not needed for SitePal editing or playback.
Please post a link to your page - where your SitePal character is embedded - and the problem can be seen.
We will review and advise.
Or, if you prefer, send us the link in an email to support@sitepal.com, and we will help you out asap.
Best regards,
Gil
Hi Mohit -
Please describe the experience you are trying to create.
e.g.
1. user clicks on button or link in your page A
2. new page B opens in new tab
3. your SitePal scene loads and displays in page B?
Is that what you are trying to do? If not please explain.
Thanks!
Hello!
As you know - we're still looking into this.
The problem seems to be the result of a delay between user interaction and subsequent audio playback - which in your page happens a couple of seconds later and not as a direct result of the user pressing the button.
While most browsers do not have a problem - and play the audio, newer versions of Safari/Mac take a stricter approach.
In our own code, as part of the SitePal code engine, we have encountered a similar issue - and were able to work around it by calling and playing an "empty" audio at the moment the user interacts with the page.
This allows subsequent audio playback to function successfully. The browser logic accepts that the user has initiated audio playback - and thus further audio playback is no longer blocked. I believe that's what you are seeing in the console.
This works fine on all browsers - including Safari/Mac, including in React.js.
The Scenario in your page seems somewhat different - and we're looking at various ways to help you work around Safari browser restrictions.
For example - if you were to initiate speech immediately upon the user clicking the start button - that might help.
You may want to try that - while we continue to look at this from our end.
Hope this helps - we'll follow up via email early in the week.
Let us know if you make any progress.
Take care,
Gil
Hello!
Our engineer is standing by for your Skype call.
His Skype handle is: <redacted>
Customer support service by UserEcho