Tag: rtmp

Playback RTMP with JW Player

You can publish a rtmp stream to a rtmp address and then playback with an external player like JWPlayer.
If you publish StreamName to rtmp address rtmp://your-rtmp-address-here then you will need to configure JW Player:
var flashvars = { file: StreamName.flv, streamer: rtmp://your-rtmp-address-here, autostart:”true”, type:”rtmp”}

 

Webcam video streams can be published from web with a video Live Streaming broadcasting script. With the VideoWhisper Live Streaming soulution, StreamName is channel name (in example Studio586). Important: As latest VideoWhisper solutions also support P2P streaming, these need to be configured with alwaysRTMP=1 parameter in their _login.php or equivalent script so streams are always published to RTMP server.

 

If you want to publish for other devices special encoders and codecs would be required. Using an external encoder you can encode with codecs and settings not available in browser flash player (due to flash limitations). Not all encoders and versions are compatible with all rtmp servers and versions. Some require special configuration and usage instructions.

Adobe Flash Media Live Encoder can be used for Adobe Media Interactive server and is also reported to work with Wowza.

Wowza & Wirecast documentation and support is available for Wowza Media Server hosting.

 

Note that when publishing H.264, video player should be configured to play StreamName.mp4 instead of StreamName.flv .

Configuring Flash Live Video Streaming Applications

Measure connection capabilities

To configure flash applications streaming you will first need to determine the connections that most users will have. So test first with your connection and also request other users to test.

So let’s consider this situation determined by http://www.speedtest.net (measure speed to a server close to the location of your streaming server):
Download: 9.43Mbp/s
Upload: 0.49Mbps

This looks like ADSL (in this situation upload bandwidth is 20 times lower than total connection bandwidth).

0.49 Mbps = 502 Kbps (kilobits per second)
8 bits = 1 byte,  so that means you can upload with 62 kb/s  (kilobytes per second)

As you can see, usually, connection is the cause of quality and latency limitations. A server with 1000Mbps connection will theoretically be able to handle up to 2000 x 0.49Mbps streams, so the server is not the problem with your tests, unless you’re on a shared plan and other clients are maxing out the resources.

How to configure flash videochat applications?

Considering you also have to upload audio and other data on that connection, you could setup camBandwidth to 49152 bytes/s (allocate for the compressed video stream).
On chat systems buffering should be reduced to 0.1 so delays are minimized. On 1 way streaming systems, you can use higher buffering to increase fluency in case of connection turbulence.

Flash streaming applications vs Skype

Skype desktop application uses different technology than these web based applications limited by browser based flash technology limitations . Skype uses:
–  p2p connections between all users and also uses fast 3rd users as proxies (not using server – so if you are in the same local network with the other tester or with a 3rd skype client with better connection, it uses the local bandwidth)
–  better codecs to get better quality for same bandwidth (flash player currently encodes only h263 and external encoders must be used to encode h264)