Hello Rajeev - 

This type of anomaly is sometimes fixed by clearing the browser cache. 

Please do so, then logout and login - and try again.

Let me know if the issue is resolved.

Best

Gil

THe SitePal Team

Hello!

1.

If you are looking to improve performance - there is no need to store the audio because our built-in caching system already does that for you. We cache over 20M audios on the cloud to ensure that subsequent calls for the same audio take less time.

If your intention is different - please send us a note to support@sitepal.com and explain what you have in mind, we will advise.

2.

Yes, when you call sayText or sayAudio or sayAI - you can use out callbacks to know when audios start speaking & end speech. You can also receive progress callbacks if you want to.

See this example for reference - https://sitepal.com/api/examples/syc_classic.html

And checkout the "callbacks" section in the Client API reference for more information.

Note: Start & End audio callbacks are always sent - all you need to do is setup the JS callback functions to receive them.

To receive progress callbacks you need to turn ON progress attribute using the 'setStatus' call.

Hope this helps!

Regards,

Gil

The SitePal Team

Yes, ChatGPT is pre-integrated with SitePal. 

Please review this document & let us know if any questions.

https://sitepal.com/docs/Implementing_Your_AI_Agent.pdf

Regards,

Gil

Hello Mustafa - 

When you run the nextjs build locally - does the build fail on localhost but then work on your live page?

We're looking into it - will advise asap.

Regards,

Gil

Hello Mustafa !

Can you share a link to your page where the problem can be seen?

Also pls advise which platform/browser you are using.

If you prefer - pls send the information to support@sitepal.com & we will advise asap

Thanx

Hello Mustafa!

I think you are misunderstanding the functionality of our callbacks.  

I suggest to use our technical example as a guide - 

https://sitepal.com/api/examples/saytext_classic.html

copy the source code of the example to your own test page, then replace the embed code in the example with your own, and update your licensed domain - without making any other changes to the page.

This will allow you to get it working with minimum effort - and then you can further adapt to your needs.

Our technical note (mentioned above) guides you step by step in getting started with using dynamic TTS - and that's the best way to start.

Note: there is no need to define any callback function to get sayText to work.

Hope this helps,

Gil