RTP and RTSP are among the oldest streaming protocols. But they are still actively used because of such protocol features as low latency (in regard of RTP) and support of so-called publishing (in regard of RTSP) when a live media stream is pushed by a client to a server for further distribution. Many modern protocols lack this publishing feature, because already created ones work well enough covering all needs for video streaming software development.
RTSP found wide adoption in security while RTP is actively used in VoIP. Even the relatively fresh WebRTC utilizes RTP as a media transport. So, there is no lack of applications for both RTSP and RTP protocols. Their wide popularity guarantees wide compatibility for new software products using them. Let us take a more attentive look at those RTSP key features that are still in urgent demand among software developers.
- RTSP supports so-called publishing when a live media stream is pushed by a client to a server for further distribution. If a future app is expected to provide their users with a function of publishing live video streams, it definitely should use RTSP.
- 2. RTSP has the client mode that allows your app watching live streams directly from RTSP servers.
- RTSP has the server mode which can be used to broadcast your live streams to RTSP clients as well as create simple two-sided media communication between two devices.
- VASTreaming RTSP library for .NET provides all these client, publisher and server modes in fast, efficient and light code, without any external dependencies.
- VASTreaming RTSP library for .NET publishing mode provides the ability to publish a live stream from any client capture device to an RTSP server, what can ensure some prospect in the quickly changing world of client devices. As a part of the mentioned above feature, your RTSP-based application will receive media source independence. Camera, microphone, screen capture, or any other media can be used as a source for publishing. Moreover, on some platforms it is possible to mix the following video sources together in real-time:
- One or more camera capture
- Screen capture
- Overlay text
- Overlay static or dynamic image (e.g. GIF file) with preserving the transparency
6. VASTreaming RTSP library for .NET can also work as a client to receive a stream from an RTSP server and play it on an end user’s device. The necessary UI controls are provided on all supported platforms, developers can easily integrate them in their client-oriented apps. One of the big advantages of these controls is very low latency on some platforms, what can be crucial for such applications as video chats or video game streaming.
- VASTreaming RTSP library for .NET allows creating simple RTSP server with the ability to ingest published streams as well as re-distribute streams to connected clients. Based on the server hardware configuration, it can serve from hundreds to thousands of simultaneous connections. Server-oriented functions can be a good base for development of new server-side applications unfolding new possibilities for video content providers.
- VASTreaming RTSP library for .NET gives developers an opportunity to implement a customer specific authentication method. The library contains an authentication event to delegate authentication to a customer’s own code.
- VASTreaming team offers various supporting libraries for easy integration of their streaming libraries. Among such supporting functionality, you can find media capturing, encoding, decoding, playing, writing to a file, and reading from a file.
- Extensive support for developers and quick-to-help service to answer any question arises while the VASTreaming library use. You can get even a full-scale supervising over the integration of streaming libraries into your projects.
The listed above advantages stand behind the long-time popularity of RTSP and its libraries. Any of these features can indicate a new direction in software development, ensuring powerful tools for implementation of most breath-taking ideas.