Skip to main content
AfternoonBlend
Known Participant
January 13, 2014
Question

Audio not playing after navigating multiple slides back in HTML5

  • January 13, 2014
  • 5 replies
  • 1848 views

I was doing some testing of an HTML5 course that includes seperate narration on every slide. I noticed that if I clicked back 10+ times the audio on these slides would not play. If I navigate forward from these slides with lost audio, it resumes where it dropped out before. I suspected that the browser may only cache approximately 10 slides which would be maybe 5mb of audio in addition to whatever the slide itself contained (maybe 12-15mb total?). If I publish as a SWF instead, I don't have this issue.

I cleared my browser cache (IE9 - required by work [but the same issues occurs with every browser I've tested]), and ran the course again and I noticed the audio didn't drop out anymore.

Has anyone experienced a similar issue? I know there have been several audio issues with captivate and HTML5....

I'm using 7.0.0.118 until we can get IT security to push the update to 7.0.1 or are allowed to update captivate on our own machines. Could this be the cause?

This topic has been closed for replies.

5 replies

elearningbuilder11
Inspiring
November 16, 2017

SAME THING is happening in CP 2017...

It's now near end of 2017, so this has been a known issue for HOW MANY years now?  

Adobe. FIX your product please.

RodWard
Community Expert
Community Expert
November 17, 2017

Does this happen to HTML5 content when played on a desktop browser, or only on a mobile device?

elearningbuilder11
Inspiring
November 17, 2017

It's on a desktop MAC

Ive tried Chrome, Firefox and Safari...

Participant
July 3, 2014

I have the exact same issue. All is fine if a play a published course (HTML 5, Scalable, Force republish on all slides ) forward. However, if I navigate back at any stage, audio becomes erratic or gets totally lost. The only way to recover audio is by looping back to the start of the course and press Ctrl-F5. I am using Captivate 6, latest updates installed. This is a serious bummer. I just started moving away from Camtasia Studio this week and thought I figured out how to build a course in Captivate and now this happens. It might be a show stopper for me.

Inspiring
July 3, 2014

I’ve never tried patching Captivate 6 to fix this issue. Captivate 7/8 that I do use still have that issue unfortunately, however if you don’t need the feature for a course (I did not), what I did was to just force turning off the multi audio track (channel) feature in the code (I did that by setting cp.multiAudioTrack to false in index_SCORM.html at the start of the initializeCP function. By default cp.multiAudioTrack is enabled on browsers that support it. You can patch index_SCORM (or whichever template version of the index you are using, including the preview ones) in the publish templates or in the output course post-publishing – I have some versioning scripts set up to backup/patch and restore original versions of the Captivate core files for various scenarios – for patches if I’m using playbars I usually put them in the playbar code because I can do that without having to change much in terms of the original files. I put conditional hooks in the templates to call initializers in the playbar code at critical points once it’s been loaded but before the full captivate initialization.

In Captivate 6, Adobe still had the core javascript functions accessible in the installation folders as opposed to now they hide it in DLLs (at least on Windows). The relevant code is in the file CPLibrary.js. On Windows, that file is located in C:\Program Files\Adobe\Adobe Captivate 6 x64\HTML\assets\js\CPLibrary.js. In that version, Adobe sets the maximum number of audio channels just before they initialize them as opposed to setting a configuration value, so you would probably have to patch that file in order to affect it. Try locating the following code:

if(cp.device == cp.IDEVICE)

this.MAX_AUDIO_CHANNELS = 1;

else

this.MAX_AUDIO_CHANNELS = 10;

and patch it to:

if(true||cp.device == cp.IDEVICE)

this.MAX_AUDIO_CHANNELS = 1;

else

this.MAX_AUDIO_CHANNELS = 10;

the idea is to only have it allocate one channel vs. 10 – again not sure if that will fix it in CP6, but it does the job in CP7 and CP8. bviously from the code you can see that some devices require this setting. You could also try reducing the number of channels allocated (e.g changing 10 to 2 or 3) to see what effect that has.

I’d have to try it myself to see if that would still work back to CP6, but it eliminated the problem for my courses in CP7 and CP8. The problem is something to do with there being 10 channels available in the multichannel scenario and something being mismanaged there under certain circumstances. I haven’t had time to figure out exactly what, so that is a workaround for the time being.

Hope this helps someone - let me know if it works for you. Always remember to backup the original files if you make any patches to core installed Captivate files, and keep in mind that updates to Captivate may overwrite your changes, so keep a copy of the changes separately and re-patch and check if necessary after updates.

Your mileage may vary (disclaimer).

Participant
July 3, 2014

Many thanks for your reaction! I tried your solution, modified the file, restarted Captivate and published again, but there was no effect . For now, I solved the problem by extending the audio track to last as long as the slide. I simply add silence at the end of the audio track. That seems to work, but IMHO it is more of a workaround than a solution.

Inspiring
June 6, 2014

Ok, another follow-up - I did a test patching the Captivate CPM.js code in a published course as a test to force cp.multiTrack to false regardless of the device.  This could be accomplished in the playbar code in Captivate so that it does not require patching of the core Captivate code.  Once that was done, the course then operated properly in terms of no audio loss during back branching, however I believe that operating in non-multiTrack mode has other ramifications, and some of the tests are not performed unless the device is an I- or android device.  You can also spoof to make Captivate think it is running on a particular type of device, but that also has it's issues based on the browser support for features.  Perhaps someone knowledgeable can address this point.  I did this mainly to see if the 10 track limit imposed by the multitrack audio pre-buffer limit was affecting this issue, and I do not really consider this to be a fix.  I'm guessing at this point that this is caused by something to do with pre-buffering of audio and the 10 channels available in multitrack mode.

Maybe this could give someone at Adobe some clues as to what is causing this problem to come up with a fix.

Inspiring
June 6, 2014

Was this question ever answered?  I am experiencing this same issue in both Captivate 7 and Captivate 8 when using output published for HTML5.  It is reproducible and does not seem to matter whether the browser cache is cleared or not.  All of the audio seems to be accessible on all the slides when accessed using the TOC or using the Next button going in a forward direction through the course, however when accessing scenes in the reverse direction (e.g. going to the last slide in the course using the TOC and using the back button or the TOC to go back to prior slides), after going back to a varying number of slides (not any specific slide, just seems to be almost random), at some point a slide will no longer playback audio.  The audio does not come back for that slide, and the problem then affects all slides in the course prior to that one (no audio for any slide prior to the point where it drops out).  If slides are accessed after that slide, however, most of the time the audio is still working.

This is a major issue, as it prevents use of random access in the course without random loss of audio.  Muting and unmuting sound via the playbar has no affect, so it does not appear to be an issue of audio level.

There is also a related major problem which is also an issue where in the process of back branching through the course that the playbar will disappear on random slides where the audio problem is occurring.  None of the course settings/actions are set to have the playbar hidden, and the course is set to have the playbar always visible.

Known Participant
June 6, 2014

I'm also experiencing random audio loss after navigation on relatively small presentations published from 7 & 8 to HTML 5. I can find no pattern that would indicate the cause as yet.

VikramGaur
Adobe Employee
Adobe Employee
January 14, 2014

Hello,

Welcome to Adobe Forums.

Does this happens with a test project as well (Project with 5-10 slides, audio included) ?

Are you working on a MAC or Windows ?

Thanks,

Vikram

Adobe Support

AfternoonBlend
Known Participant
January 14, 2014

I'll put together a quick presentation and test now.

The issue is not limited to a single course, it's been everything published to HTML5 so far. The course does not have to be published in order for issues to occur - they can simply be previewed in HTML5 and the audio will drop out.

It only seems to be audio files that have been previously accessed and are recalled by navigating back.