the programming time is limited to 36040
I am trying to select an audio file for one of my scenes, and I have received a popup error that says:
"This audio cannot be selected. The programming time is limited to 36040 seconds and 36040 seconds have been used. Please select an audio up to 0 seconds long."
What does this mean, and how do I resolve it??
Hi Jeremy -
This is curious. Please send a note to support@sitepal.com and we will look into it and clear this up.
Regards
Gil
HTML5 and Bootstrap Dropdown Menu Layering Issue
Hi, all.
I have a sample published here:
https://rtgstorecentus01.blob.core.windows.net/content/sandbox/bootstrap-4-menu.html
The page uses the Bootstrap toolkit. If you click on the dropdown menu in the menubar, you'll notice that it falls behind the avatar. It doesn't do this with the Flash version. Is it possible to alter the layering somehow so that the SitePal player is lower on the z-axis?
The above sample uses the current version of Bootstrap 4.0, which technically is still in beta. This issue also appears in the most recent production version of Bootstrap, version 3.3.7:
https://rtgstorecentus01.blob.core.windows.net/content/sandbox/bootstrap-337-menu.html
Thanks much!
--Alex. :-)
Alex -
We've assigned "z-index: 9999;" to our SitePal player so that it would not be hidden behind other HTML elements.
You should be able to resolve by assigning a larger z-index to the dropdown.
We've verified this will work in your case - please see the following screenshots -
Hope this helps.
Best
Gil
HTML5 Avatars and Player Frames
Hi, all.
I have a sample available here:
https://rtgstorecentus01.blob.core.windows.net/content/sandbox/skinned-player.html
This particular scene is supposed to have a frame (or skin) at the bottom of the player:
Are frames only rendered in the Flash version?
Thanks!
--Alex. :-)
Saytext () instruction limit
Hello,
In Saytext (txt, ...), txt is limited to 900 characters. (225 characters in Chinese and Japanese language).
But using the Saytext () statement in a JavaScript function [sayText ('..'; sayText ('..'; sayText ('..'; sayText ('..'; ...]
or directly in a link [<a href = "javascript: sayText (), sayText () sayText () sayText () sayText (), ...], is it limited number of Saytext() statements?
cordially
François SCHAAL
*****************************************************************************************************
Bonjour,
Dans Saytext(txt,...), txt est limité à 900 caractères. (225 caractères en langue chinoise et japonaise).
Mais l'utilisation de l'instruction Saytext() dans une fonction Javascript [sayText('..';sayText('..';sayText('..';sayText('..';...]
ou directement dans un lien [<a href="javascript:sayText(),sayText()sayText()sayText()sayText(),...] est-elle limitée en nombre d'instructions Saytext() ?
Cordialement
François SCHAAL
Hello François -
Yes you can call sayText repeatedly (in sequence) to speak a longer text.
Below are a couple of technical examples.
You may need to set the value of the "interrupt mode" to zero (OFF).
When Interrupt Mode is OFF, successive calls to sayText or sayAudio are queued for playback.
header Err does != 'ID3' fileErrorCallback for file sitepal2d_v0.js:1
Does anyone know what causes this error? My avatar stops talking and the page stops execution.
Hi. I want to extract a sound from your program but I do not know how please help
Hi. I want to extract a sound from your program but I do not know how please help
HTML5 TTS on iOS Not Working?
When visiting the "Dynamically Call Text-to-Speech" demo page (http://www.oddcast.com/support1/saytext_classic.html) from an iOS device (confirmed with iPads running iOS 9 and iOS 10), a spinning icon appears and the audio is not played. The avatar itself renders fine; it just malfunctions when any of the links on the page are clicked to generate TTS audio. Other demos with static audio work fine. Symptoms appear with Safari, Chrome, and Firefox. We are experiencing the same symptoms with our own avatars on our own pages. Other browsers and operating systems work fine. Is this a known issue, and is there a workaround for iOS devices?
In revisiting this issue - I'd like to add that the code was revised shortly after this discussion to ensure that attempting to initiate speech on a mobile browser before page is activated will not cause an error.
Customer support service by UserEcho