I know what this is actually, I think I might have reported the cause a while back to the list. The pause you are seeing is caused by the server mimicking what FMS does at the end of the clip, which is to go back to the beginning and pause. Technically FMS does a seek instead but this method doesn't break compatibility too much. The trouble comes in that FMS sends the NetStream.Play.Stop event once the server has finished sending the data to the client and Red5 sends it when the client "should" have finished playing the content. Making that change will cause most clients such as the FLVPlayback component's complete event handler to fire. The change involves only sending the NetStream.Play.Stop event earlier though, not actually closing the stream. The second and larger problem here is that the Red5 stop timer, which is a timer that gets initialized once the server has sent all the data, does not take into account mid clip buffering correctly. So for example when watching a VOD clip if your stream buffers in the middle of the clip, the stop timer will go off early cutting the clip off before the end has been reached and usually cause most "complete" event
--Dan-- On Feb 14, 2007, at 10:39 PM, Dan Rossi wrote: > Hi there im for some reason getting pause notify events when a stream > has ended, i dont seem to get the onPlayStatus event to get a complete > event. Here is what happens > > NetStream.Play.Stop > NetStream.Play.Reset > 05:36:23.890 [INFO] Subscriber Playback Started > NetStream.Play.Start > 05:36:23.890 [INFO] Subscriber Playback Paused > NetStream.Pause.Notify > NetStream.Buffer.Flush > > > Any ideas, do i have it wrong again how to call a VOD clip properly ? > > _______________________________________________ > Red5 mailing list > [email protected] > http://osflash.org/mailman/listinfo/red5_osflash.org _______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org
