testing a red5 live streaming rtmp, plus creating a player for the rtmp

We created an app for live streaming here.

Now we going to test it and create a player code so we can start streaming to our site.

Do you have fmle installed on your computer? You need to download it from adobe.

Lets test it first, go to

enter the rtmp of your app. the rtmp is

rtmp://server IP/app



Enter this URL on the long string and click connect, now click “Publish” your camera will start,  and now click “Play” if the 2 players show the same thing you are on. Everything is good.

OK, now we have to work on “stream name”. We talked about rtmp, and we tested it, the testing site if you go back to it

it has a stream name, “testing” this must be on both the publishing and on the player.

so it must be on the FMLE and on the player code.


(click on the image to have a better view)

the FMLE on the left you have your settings, frame per second, bitrate, your camera, format.

on the red5 server your bitrate should be about 320kbps higher then that you need a lot of RAM and server resources.

lets configure the fmle as the image shows.

on the right on the FMS URL enter the rtmp and on the stream enter your chosen stream name, in this case I entered “live” see image.

click connect, and then below click “Start”

you now streaming to your server.


Now creating a player for this stream. Go to


at the bottom on the “Streamer” enter the rtmp:


and on “Stream / File Name” enter the stream name, which we used on the FMLE, “live”

Click  “Generate Code!”

Take the “Preview & Embed” code, paste on your site and that’s it.

You can also use an image on the player, it will show before the user click to play,  enter the image URL on “Overlay Poster”

Adjusting settings on FMLE for live streaming with Wowza

I started on the bitrate I used 400Kbps, and on the fps I started with 30, but it lags and really is blurry. On the format I have to use H.264, because with VP6 doesn’t work on VLC and mobile devices. The audio should be AAC or MP3. If it is MP3, make it Stereo, 44100Hz, 128kbs for best results. AAC audio is preferable.

But the fps at 30 didn’t work, I increased the to 50 and voila it started to work nicely, no buffering nice quality, increasing to 60 even better.

I think lower then 50 fps doesn’t work well and it doesn’t work with the VLC also.

You can try yourself at our Wowza control panel.
username: demo
password: demo

To broadcast use the desktop encoder FMLE, can be downloaded here.

The RTMP on the demo account is password protected, please use:
username: demo
password: demo


A word about fps, the higher the better but at the cost of bandwidth. Each frame has a size, so frame size X fps = total bytes/s approx. Then you have to consider number of keyframes, the more the better motion capture details but even higher bandwidth needed.

For h.264 for example each level of encoding limits the fps and frame size that you can use for best results. Our eyes practically cannot see the difference between 15 and 18 fps, then 18 and 20, so for web 15 fps will seem very good at the same time saving bandwidth.

For webchats for example like skype etc 12 to 15 is best. For broadcasting a football match over the web 24 – 30 will be ideal if you broadcasting for flash players only, but for devices, android and apple iphones, it is better to use 50 to 60 fps.

Take a look at http://en.wikipedia.org/wiki/H.264/MPEG-4_AVC#Levels