Skip to main content
Doyle Lonnigan
Participating Frequently
January 16, 2014
Question

Captivate 5.5 Audio Stutter

  • January 16, 2014
  • 1 reply
  • 350 views

Recently published three Captivate demos.  Two work fine, the third has audio issues.  Specifically, the audio either starts a split second into the clip, cutting off the beginning, or will drop out for a split second in the middle.  Happens on several slides.

I've scoured the internet for a fix and it appears many people have experienced this problem, but the only recommended solution I can find is to apply a patch that it seems I already have.  My build number is newer than the patch, so I assume I've got it.  I've also seen it suggested that I change the slide exit action to "No action", but the slides are already set as such.  What do I do?  My bosses are looking at me to explain the problem, but so far all I can tell them is that Captivate is notoriously buggy and I have no solution other than to find a better software program with which to create our demos.

I've been using Captivate since 3.0 and have experienced this problem in the past, along with some other odd behaviors that I've found my own workarounds for.  Has this particular problem been addressed in newer versions of the software?  I'd be willing to suggest that we upgrade to the latest version, but at this point my confidence in this program is not high.  Advice?

Thanks for any help.

    This topic has been closed for replies.

    1 reply

    RodWard
    Community Expert
    Community Expert
    January 17, 2014

    Why don't you just download the current Captivate trial version, upgrade a copy of the course that has issues and try it out?

    Doyle Lonnigan
    Participating Frequently
    January 21, 2014

    Thanks for the suggestion, Rod.  The reason is because I work for a Government agency and I'm not allowed to download and install software without jumping through a series of hoops.  It'd be easier to just put in to buy the upgrade, which I'd be happy to do if I could get any confirmation that this problem (which has clearly been an issue for others as well, and for quite some time) has since been fixed.  Other than a patch issued quite a while ago (which I installed to no effect), I've seen little from Adobe to acknowledge or address this problem.