I have problem in streaming FLV over an HTTP protocol, with fluctuating bandwidth. When an another application sharing the bandwidth is opened/closed, the flash player experiences sudden Play.Stop event for the FLV. The player uses a netstream class and its objects and events. I could only find a timeout specification for FMS server, but nothing for Apache, from where my media content is delivered to clients. What could be the reason for this unexpected Play.Stop event?

// Load the video
var nc:NetConnection = new NetConnection();
nc.connect(null);
var ns:NetStream = new NetStream(nc);
videoPlayer.attachVideo(ns);
ns.play(”externalVideo.flv”);
// Monitor the video
this.onEnterFrame = function() {
if (ns.time >= 25) {
trace(”Video is finished!”);
delete this.onEnterFrame;
}
}

So I am using this and now would like to make the video simply loop, but can’t figure out how. Also, is there a more simple way to make the video loop without having the identifying length, maybe just a parameter

thanks alot.
-Janis

Thank you for pointing me to your blog site. I’ve read the tutorials on working with cue points in Flash and understand this topic so much better. I finally understand how Flash recognizes cue points with specific names.

I also understand your tutorial on how to determine when video reaches completion using onMetadata and onStatus. Taking this a step forward, how do I tell the video to return to the beginning AND STOP once the video reaches the end or the stop button is pressed? I’ve tried using ns.seek(0), but this statement returns the video to the beginning and starts playing again.

Thanks for all your help.

I completely understand now. Except, if “video4.flv” is missing from the directory the videoPlayer continues to buffer. Rather than skip to the first video and start over.
The videoPlayer works and skips to the next .flv file, it is only when the last .flv is missing that it does not skip to the first .flv and start over.

Thank you very much for contribution thus far!
Nick.

In the code you pasted, you already have a complete handler present:

listenerObject.complete = function(eventObject:Object):Void {
  currentlyPlaying++;
  if (currentlyPlaying >= videoList.length) {
    currentlyPlaying = 0;
  }
  trace(currentlyPlaying);
  videoPlayer.contentPath = videoList[currentlyPlaying];
  videoPlayer.play();
};

That event handler references currentlyPlaying and contentPath, and I’m proposing that you add a second event handler that does the same thing for a video that fails to load. Your second event handler would presumably do the same thing — to an extent. The stateChange event handler should probably not loop currentlyPlaying to the beginning again, because that loop would repeat forever in the off-chance that none of the video files are present.

So … you’ll continue to have your complete handler, but you’ll also add a stateChange handler:

listenerObject.complete = function(eventObject:Object):Void {
  currentlyPlaying++;
  if (currentlyPlaying >= videoList.length) {
    currentlyPlaying = 0;
  }
  trace(currentlyPlaying);
  videoPlayer.contentPath = videoList[currentlyPlaying];
  videoPlayer.play();
};
listenerObject.stateChange = function(eventObject:Object):Void {
  if (eventObject.state == "connectionError") {
    currentlyPlaying++;
    if (currentlyPlaying < videoList.length) {
      videoPlayer.contentPath = videoList[currentlyPlaying];
      videoPlayer.play();
    }
  }
};
videoPlayer.addEventListener("complete", listenerObject);
videoPlayer.addEventListener("stateChange", listenerObject);

Thank you very much!

Although, as good as you are at Flash I am unfortunately not.
With the above ActionScript you gave me, Do I replace the old script or simlply add it?

In regards to the updating of the currentlyPlaying and contentPath, I dont quite understand…

By any chance are your two books based on Flash? Because I would realy love to have a copy of my own!! Hope all goes well.

Thanks, Nick