Frustrating seekbar issue.

Alex,

That might be a bug. Have you played with the "When revisiting" settings? We have had a few issues clicking the timeline in certain situations which made the slide kind of start over incorrectly. Have you tried to do the same on a layer?

Yes I have, it doesn't make a difference, the funny thing is if you seek anywhere BEFORE the 7 second mark (where the trigger is firing up) everything works as it should - click anywhere after that, and the trigger fires up regardless.

Actually, found a "workaround" by hiding the layer .10 sec down the line.

Awesome! Glad you found a workaround.

Still not happy about it, though. It's a clumsy one IMHO, especially if your slides contain multiple layers or you're showing one multiple times...

Hey Alex - 

Can you post an example? Having trouble visualizing. Are you using a timeline event or cuepoint event? Those will trigger whenever the seekbar is moved within the "zone" after the time or cuepoint and the next time or cuepoint trigger. 

I've avoided using cuepoint and timeline events for this reason.

It almost sounds like you still have a timeline event still active somewhere. I think the hiding the layer trigger .10 sec down the line is throwing interference for the other trigger. You could test the theory by changing the trigger to change a variable. 

The seekbar timeline events thing is annoying. Curious to know the cause in your case.

Hey Steve, here's a simple example.

Slide 1(issue),
Slide 2(solution).

Variable change still makes no difference in this case, nor does the old timeline manipulation using an off-stage object and a trigger any more... :(

Blah. I don't remember it behaving this poorly before. It's being super annoying with the timeline. I have a really old example of a video synced with layer popups at cardinal points in the video. 

This feels like a bug. I used to do this a ton and it never misbehaved like this. My suggestions above won't help. Playing with it for a bit to see if I can find a workaround. Your hide layer trigger seems to be the only good solution in this case. Bug.

Here's another super-goofy workaround that keeps the event from firing continuously when the seekbar is dragged. Rather than When Timeline Starts on a trigger object, use When the State of object is NOT hidden. Timeline objects are there even when they aren't visible. The timeline basically controls visibility. So taking advantage of that one time binary switch end-arounds the event bug.

This is becoming officially weird... :)

I understand there might be scenarios where this behavior might come in handy, but I just wish the current "feature" was a little more clear - why not add an additional trigger option - say "at exactly" x sec, which would only fire up an event at that specific time in the timeline...

I mean, at this point the functionality isn't exactly "when timeline reaches" but more like "when timeline reaches or at any point after that".

It didn't do this in release 4. I'm using it for a course I just published in the previous version and it's not firing continuously like this when my trigger objects are in view. Similar construction to what you're trying to do. I'll try it again when I get to work. We're always a version or 2 behind:)

Yes. The timeline reaches feature should be when it crosses that time or that time+ a padding of time. Makes it tough to fire once when scrubbing rapid-fires:)

Hey Alex - 

Just tested in release 4 of SL2 and the latest of SL1. The issue was there for those as well. Not sure how this never irked me before. I was sure that I'd built things that didn't display this issue. Even when the object is not extended into the timeline, the trigger still fires on drag of the seekbar.

Your hide trigger or my state event change from hidden seem to be reliable workarounds.

Yeah, me too - and the thought of having to re-test each of my recently published projects for this behaviour is terrifying...

The most worrying thing though isn't the changed approach, but the fact that the seekbar - as it stands - only makes sense for slides that contain layers which do NOT require user interaction to get out of.

For example: Try including a layer with an inline "exit" button, and the seekbar for the layer turned off and base slide paused, and then run the slide. Once you get to the layer, instead of clicking on the exit button, click on the play button to the left of the seekbar and watch as it goes on to play the rest of the slide with the layer still on...

Found another bug on seekbar behavior - if you replay the slide via the icon to the right when ON a layer, the slide will replay but no audio if the audio starts at 0.

Adjusting the timing of the audio object to start at 0.01, does the trick though.

Noticed this with some HTML5 published content back in SL1. Got into the habit of starting audio at a quarter second. Good catch:)

Me too, but I had a continuous set of slides that had to play in sequence and .25 wouldn't have worked.

It's those special/rare cases that come back to bite you...

Hi Alexandros,

Have you already opened up a support case? It may be best to test a few of the items you've mentioned here as it seems you've stumbled upon a few things that aren't working as you'd expect.