Our audio tracks include 1/2 sec of silence at the end. However, I've noticed on occasion that a slide will not play the last word or syllable on rare occasion on a slide or two.
Recently, the I've had feedback from clients who reported the same early cut-off at end of slide. I first noticed this maybe six months ago. I've had to extend the end of track silence or drag the timeline beyond the end of the audio to resolve the issue when it arises.
Has anyone else seen this or is this just another anomaly on our development systems? I should mention all the playback I am referring to is Flash playback, not HTML5.
Well, first this seems to be a bug in Storyline that requires a workaround. It is hard to reproduce on demand so I won't wait for a fix.
I don't understand Walt's workaround "advancing not when the timeline ends, but when media completes". In my case, timeline end and end of media (audio) are one and the same.
Hi, Sam -- Thanks for your reply, and if you have a file you might be able to share with our Support Engineers for further investigation, you are welcome to use this form to send it along for review.
In my case, timeline end and end of media (audio) are one and the same.
You may have it set this way, but if there is a buffering problem, the timeline keeps running while the audio pauses . It's only part of a syllable, so you don't notice it, but the audio won't be finished by the time the timeline is. That's why it occurs at random, and you can't predict it, nor reproduce it. Change your "Jump to next slide when timeline ends" to "Jump to next slide when media completes" and see what happens. It allows the media to complete, even if it is one or two syllables after the timeline ends.
If you are correct and changing to "jump to next slide when media completes" solves this issue, then someone should call this a bug and have it addressed.
My belief is that it is a buffering issue, and even though SL attempts to preload (see this discussion: https://community.articulate.com/discussions/articulate-storyline/storyline-preload-handling), this is probably not something SL can control. At least, that's my guess. I base it mostly on the random way it occurs. I think if it was a bug, it would be more predictable.
Triggering the jump until media completes is the best solution, as network latency delays and hiccups are operating system level, outside of SL's control.
9 Replies
Yes, and I solved it by advancing not when timeline ends, but when media completes. Avoids buffering issues, which is what I think causes this.
Thanks for the input, Walt! Please let us know if that does the trick for you, Sam, or if you are still in need of assistance!
Well, first this seems to be a bug in Storyline that requires a workaround. It is hard to reproduce on demand so I won't wait for a fix.
I don't understand Walt's workaround "advancing not when the timeline ends, but when media completes". In my case, timeline end and end of media (audio) are one and the same.
Sam
Hi, Sam -- Thanks for your reply, and if you have a file you might be able to share with our Support Engineers for further investigation, you are welcome to use this form to send it along for review.
This post was removed by the author
You may have it set this way, but if there is a buffering problem, the timeline keeps running while the audio pauses . It's only part of a syllable, so you don't notice it, but the audio won't be finished by the time the timeline is. That's why it occurs at random, and you can't predict it, nor reproduce it. Change your "Jump to next slide when timeline ends" to "Jump to next slide when media completes" and see what happens. It allows the media to complete, even if it is one or two syllables after the timeline ends.
If you are correct and changing to "jump to next slide when media completes" solves this issue, then someone should call this a bug and have it addressed.
Sam
My belief is that it is a buffering issue, and even though SL attempts to preload (see this discussion: https://community.articulate.com/discussions/articulate-storyline/storyline-preload-handling), this is probably not something SL can control. At least, that's my guess. I base it mostly on the random way it occurs. I think if it was a bug, it would be more predictable.
Triggering the jump until media completes is the best solution, as network latency delays and hiccups are operating system level, outside of SL's control.
The buffering theory doesn't explain why it happens during Storyline Preview Slide. Yes, my project is on drive C and it is a solid state disk.
Sam
This discussion is closed. You can start a new discussion or contact Articulate Support.