- announced RTSP streams published to Nimble;
- streams available via public URL (i.e. pulled streams) through TCP, UDP and over HTTP (VAPIX).
Nimble Streamer allows processing any of allowed RTSP streams types:
Nimble Streamer transmuxes RTSP into HLS and DASH stream.
Nimble supports fallback for multiple RTSP pull sources for redundancy purposes.
Failover for published RTSP streams can be set using hot swap.
These streams can be used for ABR streams combination via easy-to-use web UI.
Nimble Streamer supports RTSP TCP inteleaved playback for outgoing streams with full set of features like paywall and aliases. This enables Nimble to provide RTSP stream for both viewership and further re-transmission.
Nimble Streamer has DVR feature set which allows recording of incoming RTSP live streams for further playback via HLS and MPEG-DASH.
Nimble Streamer can create RTMP and HLS streams by request from pulled RTSP sources in case you have streams which you don't want to pull 24/7.
You can set up RTSP republishing for incoming announced and pulled streams.
This will allow you to bring live streams to edge servers to provide robust streaming.
Same transmuxing engine allows re-packaging RTSP content into the following protocols.
Hot swap capabilities allow switching between source origin and substitute streams with no glitches or artifacts:
RTSP streaming can be controlled in a few other ways besides WMSPanel web UI settings.
Stream aliases are available for outgoing streams produced from RTSP. It allows defining flexible security settings and stats.
Usage snapshot shows example of combined usage of Softvelum products including processing camera input.
and required to achieve the purposes illustrated in the
If you want to know more or withdraw your consent to all or some of the cookies, please
refer to the