Skip to main content
A
Anonymous
July 30, 2012
Question

netstream seek during buffer flush

  • July 30, 2012
  • 1 reply
  • 3631 views

Hi folks,

Quick question... I am developing a simple AIR video player but I am having small issues with seeking while the buffer is being flushed.

I am listening to and tracing the NetStatusEvents, and I noticed that when the video begins to approach the end of the video the buffer starts to Flush (NetStream.Buffer.Flush).  But if I try to seek during this time, the Buffer Flush trace keeps firing, and most of the time if I continue to scrub (seek) the video while all the Flushes are being fired I end up getting a NetStream.Play.Stop event (which I have set to stop the video).

The only work around I can think of (and implemented) was to disable my scrubber once the NetStream.Buffer.Flush event has been fired.  But I thought I would check to see if any body else has seen such a thing?

This topic has been closed for replies.

1 reply

sinious
sinious
Legend
July 31, 2012

You might want to try enabling inBufferSeek:

http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/flash/net/NetStream.html#inBufferSeek

It might retain a bit longer. Also shortening your overall buffer length will reduce this issue to that amount of time.

Lastly, if it's just a "get around it" issue you might consider adding a "flag" of some sort to tell yourself when those events fire off. Then when a NetStream.Buffer.Flush fires, you set the flag to true to let yourself know it's emptying. Then when the NetStream.Play.Stop is fired off, you simply check that flag and if it's true you know you're in a flush and can run a ns.play() to make sure it plays after the seek.

Just remember to reset that flag when the buffer starts to fill or you do a seek so the NetStream.Play.Stop functions as normal.

A
Anonymous
July 31, 2012

Thanks Sinious,

I will give inBufferSeek a look.

I was looking at shortening the buffer, but the correct me if I am wrong... but after ready about setting buffer, is that it only appluies to videos from a URL.  I should have added that the video files I am working with are for local playback.

As a workaround I did have a listener for the NetStream.Buffer.Flush event, and disabled the scrubber bar upon that event, as the problem only occurs if seeking took place after that event (i.e seeking after NetStream.Buffer.Flush fired - would cause it to fires several times).   Most of the time it causes no problems, but if I test it by doing a large amount of seek requests in short succesion (again after NetStream.Buffer.Flush), suddent the NetStream.Play.Stop event gets fired (which I have a method for that event).

I will look into inBufferSeek to see if that helps.

sinious
sinious
Legend
July 31, 2012

Code operates at gigaflop speed so as long as you have the right conditions setting the right flag at the right time you should be able to avoid the issue. A HUGE amount of code can be completed in just a seconds worth of time. It might even be worth using a timer to put a "hold" on interaction for a single second before the user can proceed, only after the buffer emptying process begins so you don't bother normal seeks.

Playing off the local filesystem renders the buffer size moot. You are getting events for it however. You may as well set the buffer time to 0 and perhaps the event will only fire at the completion of the video.

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices