We have a closed caption feature for all of our courses which displays the closed captions layer when the user clicks a button to turn on the closed captions. The closed captions layer is synced with the Base layer.
We have found that the closed captions layer's timeline keeps going when the user pauses the seekbar. Only the base layer's timeline pauses. Is there a way to get all layers' timelines to pause and resume or restart when the seekbar is paused and resumed or restarted?
I tried your suggestion, but it doesn't work as needed. What happens is the closed captions layer pauses, but the base layer continues.
I came up with a work around that has the closed captions text boxes on the base layer. Instead of the triggers showing or hiding the closed caption layer when the user clicks the closed caption button, the triggers change the state of the closed captions text boxes to show or hide them.
Your way would have been easier to work with.
I have a new feature request to have triggers be tied to the seekbar being paused or resumed.
3 Replies
John, seems like I've seen this problem come up before here in the community... Have you tried setting your layer properties to always allow seeking?
According to the documentation doing so *should* allow the player's seekbar to control the layer content as well as the base - https://community.articulate.com/series/4/articles/working-with-layers
Thanks, Brian.
I tried your suggestion, but it doesn't work as needed. What happens is the closed captions layer pauses, but the base layer continues.
I came up with a work around that has the closed captions text boxes on the base layer. Instead of the triggers showing or hiding the closed caption layer when the user clicks the closed caption button, the triggers change the state of the closed captions text boxes to show or hide them.
Your way would have been easier to work with.
I have a new feature request to have triggers be tied to the seekbar being paused or resumed.
Wow, yes, and confirms my thoughts that I've seen this is an issue in previous posts. Would love to see this addressed in a future release.
This discussion is closed. You can start a new discussion or contact Articulate Support.