16 Replies
Alyssa Gomez

Hi there Becky,

Happy to help you sort this out, and I have a few questions to start!

  • Are you on the latest version of Storyline 3? To check, click Help >> About Storyline. You should see 3.3.15007.0 there.
  • Is your player seekbar set to Free or Read Only?
  • Does the audio play on it's own when the timeline starts, or do you have a trigger to play the audio?
Becky Beyea

Hi Alyssa,

I do not have the latest update to SL3 - I don't have the authorization to download or update any software in my company so I have put in a request to have this done for me. 

The seekbar is set to "Allow user to drag seekbar."

I have a variable "audiocompleted" set to false and a trigger set to play the audio when the variable is false.  Then I have a second trigger to change the variable to true when the audio completes.  This was the only way I found to set it up so that the audio didn't start over and play again when the user revisits that particular slide (they revisit this slide after each scene of the course to click on another tab). 

I think my issue has something to do with the variables or triggers.  For example, before I created the variable and triggers, the audio line of the timeline showed the "sound waves" and after I set the variable and triggers, the audio line of the timeline simply says the word "recorded." 

When it shows the sound waves, I could skip around in the audio and it acted like I expected but when the audio line simply says "recorded" the audio doesn't skip around even though the animations on the screen do.

Alyssa Gomez

Hi Becky,

Instead of using variables and triggers, could you adjust the slide properties to "Resume saved state"? This would prevent the slide from starting over and the audio from replaying when a user revisits a slide. 

If you can share a sample slide with me so I can take a closer look, that would be really helpful!

Alyssa Gomez

Hi again Becky! I just replied to your email and sent you an updated file to review. 

The bug that was affecting your file happens when you're using a Play Media trigger to play an audio file. Check out the updated file I sent, and let me know if that workaround will work for you.

As soon as this bug is fixed, I'll let you know here!