Audio Issues when Using Next Previous Buttons

Apr 13, 2014

Setup: Wind 7, Powerpoint 2010, Studio 2013, Articulate Online.

If I let my presentation auto advance from slide to slide, it plays fine.  If I start using the slider bar to advance farther into the slide I typically notice the last few seconds of the audio being cut of.  To compensate, I have started adding a few more seconds of silence to the end of the audio as a work around, but wonder if this is a pre-fetch caching issue in Presenter or AO?

Additionally, if I use the previous button, then the next button after using the slider, the following slide will NOT play the audio for that slide.  This will not be acceptable for users and I won't be able to field all the support calls.  At this point I am considering disabling the navigation controls entirely and just let the presentation play like a radio.  Anyone else run into this problem?  I did submit a ticket to Articulate on this but have not heard back.  We are suppose to go live tomorrow with our training, so I am looking for reasonable work arounds.  Not sure if this is a Present publishing issue, or a AO playing issue, and don't know how to test to isolate which is the root cause.

Thanks,

Bobj.

2 Replies
Bob J
After additional testing, the problem appears to happen after the following:
1. Play a few slides, then use the slider bar to advance 70-80% through the current slide.
2. Let the slide automatically advance to the next slide. 
3. Then use the previous button to go back 1 or 2 slides.  The audio will now play though video works find.  This seems to occur about 30-50% of the time.

I was able to get rid of the problem late last night (I think, but have not done extensive testing as we went live this morning) by changing the action for ALL PreviousButtons to go the the specific previous slide, instead of using the normal PreviousButton action (which goes to the relative previous slide, depending on what slide you were previously on).  If this holds up, the problem appears to be some type of caching /pre-fetching being done due to the new way that the PreviousButton works.  Setting the PreviousButton to go to the absolute previous slide seems to clear up the problem.  I am using a 2009 presentation that was converted to 2013 by Presenter 2013.  I did not create this presentation from scratch in Presenter 2013 (and don't want to!).  Can anyone else confirm this problem in their presentation?  Wondering if this is a 2009-2013 conversion issue, or a problem with all presentations in Studio 2013.

Thanks,

Bobj.

This discussion is closed. You can start a new discussion or contact Articulate Support.