@ -9,12 +9,12 @@ _rtsp-simple-server_ is a simple, ready-to-use and zero-dependency RTSP/RTMP ser
@@ -9,12 +9,12 @@ _rtsp-simple-server_ is a simple, ready-to-use and zero-dependency RTSP/RTMP ser
Features:
* Read and publish live streams with UDP and TCP
* Publish live streams with RTSP (with UDP or TCP) or RTMP
* Read live streams with RTSP
* Each stream can have multiple video and audio tracks, encoded with any codec (including H264, H265, VP8, VP9, MPEG2, MP3, AAC, Opus, PCM)
* Pull and serve streams from other RTSP or RTMP servers, always or on-demand (RTSP proxy)
* Serve multiple streams at once in separate paths
* Encrypt streams with TLS (RTSPS)
* Publish legacy RTMP streams
* Pull and serve streams from other RTSP or RTMP servers, always or on-demand (RTSP proxy)
* Authenticate readers and publishers separately
* Redirect to other RTSP servers (load balancing)
* Run custom commands when clients connect, disconnect, read or publish streams
@ -181,14 +181,14 @@ Edit `rtsp-simple-server.yml` and replace everything inside section `paths` with
@@ -181,14 +181,14 @@ Edit `rtsp-simple-server.yml` and replace everything inside section `paths` with
```yml
paths:
all:
publishUser: admin
publishPass: mypassword
publishUser: myuser
publishPass: mypass
```
Only publishers that provide both username and password will be able to proceed:
RTMP is a protocol that is used to read and publish streams, but is less versatile and less efficient than RTSP (doesn't support UDP, encryption, most RTSP codecs, feedback mechanism). If there is need of receiving streams from a software that supports only RTMP (for instance, OBS Studio), it's possible to turn on a RTMP listener:
```yml
rtmpEnable: yes
```
Streams can then be published with the RTMP protocol, for instance with _FFmpeg_: