The default captivate output for HTML5 works with audio for iPad, but not for Google Nexus 7 with Android 4.1.
Using the Nexus 7, my slide audio will not play at first with the console error:
StAd1 /members/ERISK_content/ERISK_1_1_1/ar/StAd0.mp3 gotStuck @0
But, if I Pause the project for a while and then play it again, it works fine. The audio will not eventually load if I simply let it play - It needs to be paused before it loads. Does anyone know what is going on?
The only way I figured out how to get around this was to masquarade as an ipad. I changed the code in CPLibrary.js to handle the google nexus in the same way the ipad was handled, and everything started working. Not the most elegant solution, but whatever
I am having the same issue on a Samsung Galaxy Tab II with Android 4.1 installed using the Chrome browser. Now that android only uses HTML5 this has become a huge issue for my company and we really need a fix fast. The weird thing is that I had it working on my LG Optimus G phone with the same Android version and google chrome. Need some help please!!!
Go take a look at this page with your Android browser:
If this page shows your browser does not support the <audio> tag, Audio() object, or MP3 then you are currently sunk and this issue is NOT Adobe or Captivate's fault.
HTML5 is quite frankly a nightmare to support at the moment because everyone seems to somehow expect it to be as good or better than Flash SWF output, even though the browsers across this new landscape are a dogs breakfast of incompatibilities.
Bottom line: If you are planning to try and use HTML5 output from Captivate, TEST, TEST, TEST, TEST, in ALL browsers used by your target audience BEFORE you promise anybody anything.
UPDATE: Here's another good link for testing purposes:
This is not definitive. Of four browsers I have tested on the Acer A210 with Android 4.1, all show the same combatibility yet only one plays audio correctly for Captivate 6 HTML5 output. That is Dolphin with the Jetpack add-on.
Yes but do ALL FOUR browsers actually have all the codecs they need to play that audio?
One of the things I've noticed when reading lots of blogs and forum posts about the myriad of HTML5 issues being experienced is that even when the browsers DO supposedly support the new media tags for HTML5 they don't necessarily have everything they may need to play the files.
So, in one sense you are correct, it's NOT as simple as just looking at a test page. But if your test suggests that the browser SHOULD be able to play the media, then you need to dig deeper to find out why it actually does not do so.
Thanks for trying to help and postin the html5 test links. It looks like google chrome should be able to play audio. And now I see it does with a very long lag time. The audio doesn't start playing until the slide has paused for at least 20 to 30 seconds. I've tried compressing the audio to make the file size smaller thus decreasing load time. This did not work. There is no latency in the same browser on my LG Optimus G phone. Anyone know if you can adjust setting in the Samsung Galaxy Tab II to help this? I know there is no latency adjustment in Captivate. Or is there?
Something just occurred to me. Captivate will normally concatenate audio clips in a project if the audio on each slide is set to begin at the very beginning of the slide. If you delay the start of the audio clip by only a fraction of a second on each slide, Captivate will split the audio into separate small clips, one per slide.
In your HTML5 project how many audio files does it show? Can you check to see if you have only one big audio file for the entire project or if there are numerous audio files corresponding to each slide?
If it turns out that you have only one large audio file, then perhaps your issue with the delayed start to the audio is that the browser is downloading the entire clip before starting audio playback. Breaking up into smaller clips might give a better user experience.
Europe, Middle East and Africa