Skip to main content
Known Participant
December 7, 2015
Answered

Sound does not stop with slide - plays sound from next slide

  • December 7, 2015
  • 1 reply
  • 849 views

After four hours of pounding on it and failing to figure it out, I succumb to asking the community.  Here is how I created:

6 slides (just started the project and decided to test it)

Each slide except #2 has voice synthesis audio from speech management. (I used Paul, but that shouldn't matter)

I have a button on each slide to continue so that the slide stops for the user to view graphics, etc.  Button action is next slide.

When the slide plays, it reaches the end of the audio and continues to play the audio on subsequent slides, even though the slide has not advanced.

Why does the sound not stop at the end of the slide?

    This topic has been closed for replies.
    Correct answer Lilybiri

    Same error to the process in 9.


    You misunderstood what I tried to explain. It has no sense to add silence to the audio clip itself (should be noise). But in the Timeline panel, move the audio timeline away from the start of the slide and leave some space after it as well. Something like 0,2secs

    1 reply

    Lilybiri
    Legend
    December 7, 2015

    Be sure to leave a small gap after the audio clip on each slide (I do it in the beginning as well). When that is not the case, Captivate tends to consider it one big project audio clip, that is perhaps what is happening for you.

    Known Participant
    December 7, 2015

    Thanks.  I will go into the editor on each slide and test that.  BTW, know that your work here is very appreciated.

    Known Participant
    December 7, 2015

    On reviewing the audio files, I am finding that when I insert 3 seconds of silence to the end of the file, save, and close, I go back and the silence is not there.  This may be a bug in the audio editor.  I have also tested this by going to the end of the audio track and adding at the playhead.  I may have to wait until I go home so I can use Audition.

    I'll report it to Adobe.  It doesn't solve the other problem, but it definitely found a bug.


    Same error to the process in 9.