Forum Discussion
Layer problems when using the seekbar
Hi there
I'm trying out the new Storyline 360 and was initially happy to see that videos are automatically paused when you pause the timeline of the slide and keep in sync with the timeline when you use the seekbar. But I also noticed what I think is a huge problem with layers.
Example:
-On the base layer, I have a 1 minute timeline
-After 10 seconds, a trigger on the base layer shows layer2 with some content (the layer hides itself after an additional 10 seconds)
-If I use the seekbar to jump halfway into the slide (30 seconds), layer2 is shown even though it should only be shown when the timeline of the baselayer reaches 10 seconds and then hide again at 20 seconds
- And if I play the slide from 0-30 seconds (and layer2 is shown and hidden as intended) and then use the seekbar to go to 50 seconds, layer2 is shown again.
- Also, if I use the seekbar to pause the slide, only the base layer pauses - any layers visible at the time of pausing will continue playing
In my opinion, this makes it incredibly difficult to create a working module that uses both layers and the seekbar function, and basically renders the seekbar function useless (or the layer function). Is there some way to fix this that I am not aware of?
28 Replies
Hi Martin, thanks for reaching out. I'm going to do some testing to see if I can reproduce what you're talking about and figure out the expected behavior. I'll pop back in when I have more info!
Martin, thanks again for bringing this up. Yes, I was able to reproduce that clicking anywhere on the seekbar in the base layer (after the "show layer" trigger time) would again show the layer, and that isn't expected behavior.
As far as using the pause on the seekbar- do you have your slide layer set to allow seeking? If not, or if automatically decided, set it to yes, and you should be able to notice that your seekbar becomes independent of the base layer timeline.
I'm giving this information and my test file to our QA team to review. I realize that this behavior is frustrating for you, so again, I really appreciate you pointing it out. When we have some information to share on this issue, we'll update this thread. If you're still subscribed, you'll receive an email notification.
Is there an update on this issue?
Hi there Martin,
Thanks for checking in. Our QA team is still evaluating this behavior, so I don't have any updates to share at this time. We’re monitoring the way this issue impacts our customers and figuring out how a change here might fit in with other priorities. You are in the right place, and we’ll be sure to let you know any further information we have to share as soon as we can!
Thank you for your reply. I have just realized that the same problem exists in Storyline 2. I have submitted a bug report. This is a major problem that needs to be adressed fast.
I hear your concern, Martin. I know that we’ve had this issue on our radar for Storyline 2. We continue to share all of your feedback to our QA team, and we’ll post any updates here in this discussion for both SL2 and SL360.
Any updates on this problem? Also, do you know if this bug is also present in the new Storyline 3?
Hi there Martin,
Thanks for checking in. Yes, we're seeing this issue in Storyline 3, as well. We're still working through this bug, and I've flagged this thread to be updated as soon as we get more information. I appreciate you for sticking with us on this!
Has there been an update on this issue. I am experiencing this in SL360.
Thank you.
Hey Mark!
Thanks for adding your voice to the discussion-- I'm sorry you've run into this too. This issue is on our radar for Storyline 360, as well.
I don't have an update at this time, but you're now subscribed to this thread. We'll notify you as soon as we have news!
