Hello!

Each SitePal Scene, when embedded into your page, is embedded in a "Portal", which is our name for the "embedded placeholder" defined by the embed code, in which your Scene is loaded.

So when you embed a SitePal Scene into your web page, first comes the Portal, which then loads the specified Scene.

In most cases you do not need to know or care about this distinction between Scene and Portal, but in some cases you do.

One such case is when you want to hide ("unload") the Scene from your page, or replace it with another. You can do that by instructing the Portal to unload or load a Scene.

The other case is when there are multiple Scenes embedded in your web page, and you need to address them individually with API calls. The Portal is an addressable object. When the embed code first loads into your page, you can get the Portal ID as a return value from the embed function. Then use that value to direct API calls to the Portal.

This is done using the 'setPortal' call. When you call 'setPortal' - you are letting us know that all further API function calls should be directed at that Portal. This includes 'sayText' & 'sayAudio' calls. 

That's how we implemented the SitePal conversation example, and that is also the answer to your question.

Please see this example - https://sitepal.com/api/examples/conversation.html

and take note how the Portal ID is initially retrieved when the embed code loads, and how 'setPortal' is called whenever it is the next character's turn to talk.

So even though you may not be looking to implement a conversation - this example is entirely relevant to your question.

For more information please see the section: "Portals & Embedding Multiple Characters on a Page" in the API reference - https://www.sitepal.com/docs/vhost_API_Reference.pdf  (on page 6), and see the API calls related to Portals, documented on p.26. 

I hope this is clear & helpful.

Regards,

Gil 

The SitePal Team

Hello! 

This problem was fixed yesterday. Please try again now & if you still see a problem please send us a note to support@sitepal.com. 

Regards,

Gil

The SitePal Team

Hello Tejashwini, 

This issue has been identified and fixed. We've verified the fix on your own test page.

Please clear your browser cache before checking.

Thanks for your patience.

Regards,

Gil

There may have been a momentary problem, but we are not aware of any recent downtime that may explain this. 

We will investigate further.

Do you still see a problem on your website?

If you do - please send a note to support@sitepal.com & include the link to your page where the problem can be seen, and we will advise asap.

btw - the URL you listed works for me (you need to remove the ID3Only param to get the audio) - see - 

https://cache.oddcast.com/tts/gen.php?EID=3&LID=1&VID=3&TXT=%2C%20in%20paris&IS_UTF8=1&EXT=mp3&FNAME=&ACC=5883747&API=&SESSION=&CS=9ffa642912606cdf9ed0800e03e57368

Regards,

Gil

The SitePal Team

The problem has been resolved. 

Thanks again for reporting the issue.

Regards,

Gil

Hello Illia - 

Regretfully the video generation implementation cannot generate 60 fps at present.

The solution to enable 60 fps requires some re-engineering & is not available at present.

We're ready to cancel your subscription & provide a refund if that is your preference.

Please send a note to support@sitepal.com - with a link to this thread - and we will take care of it for you.

All the best,

Gil

Hello Frank!

This is entirely doable, and we have two examples on the support pages that showcase exactly that - 

On the advanced examples page - look for "SitePal Conversation":

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

However - I would advise you to wait for about a week, as we are just about to release an update which would greatly simplify api access to multiple characters on the page.

In the examples noted above - we demonstrate how to control each character via the API. This is accomplished by loading each character into its own iframe, which enables the characters to be individually addressed / called.

Needless to say this makes page design and maintenance a bit more cumbersome than it otherwise would be.

In the upcoming update, we add new built in addressing capabilities to the API - which will make it possible to embed your characters into the same page, without using an individual iframe for each, and access each of them individually via the API.

When we launch this update, we will provide new examples that demonstrate the new method.

Hope this helps,

Gil

The SitePal Team