October 26, 2015

RTSP playback support in Nimble Streamer

Early this year our team introduced RTSP transmuxing support for Nimble Streamer which allowed to take RTSP streams and produce HLS, DASH and MPEG-TS outgoing streams.

As our customers requested, now we introduce RTSP TCP interleaved playback in Nimble Streamer which means the stream can both be played and pulled from the Nimble instance for further processing. To make this output, the Nimble Streamer instance may take the input of RTSP, RTMP and MPEG-TS protocols.

1. Install Nimble Streamer


Use this installation instruction to get Nimble on your server or desktop. The procedure is easy and straight-forward so having any popular 64-bit Linux, Windows or MacOS will allow you to get it working.

2. Make general settings


Since you've completed WMSPanel account sign up at the previous step, you can log into the system and go to "Nimble Streamer" -> "Live stream settings" menu.

The first tab you need is called "Global". Here you need to select output protocols which you will use for playback at selected server. In the following example we see HLS, RTSP and MPEG-DASH.

Selecting protocols for playback.



Now to be able to use RTSP for playback, we need to specify which interface will be handling this type of transmission. Go to "Interfaces" tab.


You can define any available network interface here and specify which protocol it will be used for. In the example above you can see port 1935 being assigned for RTMP for all IPs.
Now we need to add RTSP interface by clicking on a corresponding button.


If you want Nimble to handle same port for all of its available IPs, then just specify value in Port field. We use port 1937 in this example. Clicking on Save you will set new interface.

3. Set up streaming scenarios


Now you're ready to proceed with giving Nimble Streamer some input streams so it could transmux them into selected protocols, including RTSP. As it supports wide variety of scenarios, please use any of the following articles to take what you need:

With all these scenarios being set up you can now use outgoing RTSP streams for playback or usage in other media software. Your URL will look like this one:
rtsp://192.168.10.11:1937/application/stream
and the exact URL will depend on your stream setting.

Further usage


Having the output streams ready for usage, you may follow various scenarios which include RTSP playback on your devices to live media delivery between origins and edges in your infrastructure.
If you need to change content parameters, like change the bitrate, use our Live Transcoder for Nimble Streamer to transform. It has high performance and low resource usage.


You may control Nimble Streamer RTSP behavior via pull API, control your publishers via Publish control framework and limit your content accessibility with paywall features like hotlink protection or pay-per-view.

No comments:

Post a Comment