-
Notifications
You must be signed in to change notification settings - Fork 795
Seeking event never fires #175
Comments
@heff - I don't know that we ever actually seek inside the SWF. When we set currentTime in the tech I thought we purged the buffer, grab the new content, and force it in/ update time values. If that is correct, I would say we should fire seeking in the tech. |
This is related to #170. |
We may want to look at doing an 'in buffer' seek where we calculate if the seekTarget is within the buffered range then netstream.seek to that value else standard purge/grab/set routine. Just a thought. |
@seniorflexdeveloper that will not be an option with the tagbuffer work since the flash buffer will be barely 2 seconds long. |
Actually, I think the issue here is that with Flash, we don't actually trigger the events on the tech itself. We bypass the tech and trigger them directly on the player. I was only checking the tech events, so it's possible seeking is actually firing, just not where I need it to be. This could be an easy change in the Flash tech. |
I think it fires now. |
For some reason with the interaction between the HLS plugin and the swf, the
seeking
event never fires. It looks like it should, or at least we think it should.I'm wondering if it has something to do with the source buffer calling abort() before updating the time. Or if
NetStream.SeekStart.Notify
just never fires in appendBytes mode. Anyone have any ideas?The current workflow after HLS.setCurrentTime is called appears to be:
The ideal workflow I'm trying to work towards (to mimic the video element) I believe would be more like:
Are there any other challenges in getting there that anyone can see?
The text was updated successfully, but these errors were encountered: