Absolute Nightmare

Guys I sorted this, at last.

Guess what it is.

As I was being lazy with the flash and hitting f12 which gives a publish preview, it was launching the swf in the browser with its file path so something like this

file:///C:/Inetpub/wwwroot/flash_files/my_app2.html

That is where the problem lay, it should have been

http://localhost/flash_files/my_app2.html

Well hey, im gonna eat my santy hat now.

Now I need to go off and discover how to set up different bandwidth streams.

Does the server actually determine the connection speed or do I have to write some stuff for that?

Happy Christmas

Thanks again for your reply

but im afraid that makes no difference either.

Thank you for your reply and help, I really appreciate it.

Done exactly what was said here.

Deleted all the directories.

Put the main.asc in

applications\my_app\main.asc

Put my video in
applications\my_app\streams\test\abc.flv

Here is my client code
my_con = new NetConnection();
my_con.connect("rtmp://localhost:1935/my_app/test");

my_ns = new NetStream(my_con);
video1.attachVideo(my_ns);

Tried variations of the my_ns.play("abc", 0, 1);
my_ns.play("applications\my_app\streams\test\abc", 0, 1);
my_ns.play("applications\my_app\streams\test\_definst_\abc.flv", 0, 1) created that directory

All times, no clients in console and no streams showing, no stream plays in client

As I was saying, I have tried an unmerciful amount of variations on the file structure and the client connection url, I am almost giving up.

First off, your directory structure should look like this:

Your asc files:
applications\my_app\main.asc

Your video files
applications\my_app\streams\[app instance]\myVideo.flv

About the [app instance]... FMS has the ability to create separate instances of the same application. When you don't specify an instance name (more on that below), FMS connects to the default instance, and names it _definst_ .

when you make your netconnection, you're just connecting to the application instance, not the video stream. Your connection string will look like this:

my_con.connect("rtmp://localhost:1935/my_app/test);

In this example, you're connecting to an an instance of my_app, with an instance name of test. Once you have established your netconnection, you then create a netstream to play your video, like so:

my_ns = new NetStream(my_con);
my_video_object.attachVideo(my_ns);
my_ns.play([streamName], 0, 1); // See the docs for the meaning for the flags after the stream name

The value of [streamName] will be the name of your flv, without the flv extension. Since we've defined an instance name (test), the path to the flv will look like this:

applications\my_app\streams\test\myVideo.flv

If we didn't define an instance name (meaning we want to use the default instance) the video would be here:

applications\my_app\streams\_definst_\myVideo.flv

The examples here doing include any status handlers for the netconnection and the netstream, which you'll want to add. Typically, you'll want to wait for the onstatus event from the netconnection before you create the netsream. Without those event handlers, your client app can't respond to errors or failures. All of that is covered in the docs.

About the console... you won't see any streams listed until a client connects to a stream. The console lists active streams, not recorded files. When a client connects, you'll see two entires show up in the list. One is the server playing the recorded file, and the other is the stream being published to the client.

Hope that clears things up a bit.