ready-to-use RTSP / RTMP server and proxy that allows to read, publish and proxy video and audio streams

Overview

rtsp-simple-server

Test Lint CodeCov Release Docker Hub

rtsp-simple-server is a simple, ready-to-use and zero-dependency RTSP / RTMP server and proxy, a software that allows users to publish, read and proxy live video and audio streams. RTSP is a specification that describes how to perform these operations with the help of a server, that is contacted by both publishers and readers and relays the publisher's streams to the readers.

Features:

  • Publish live streams with RTSP (UDP or TCP mode) or RTMP
  • Read live streams with RTSP or RTMP
  • Pull and serve streams from other RTSP / RTMP servers or cameras, always or on-demand (RTSP proxy)
  • Each stream can have multiple video and audio tracks, encoded with any codec (including H264, H265, VP8, VP9, MPEG2, MP3, AAC, Opus, PCM, JPEG)
  • Serve multiple streams at once in separate paths
  • Encrypt streams with TLS (RTSPS)
  • Authenticate readers and publishers
  • Redirect readers to other RTSP servers (load balancing)
  • Run custom commands when clients connect, disconnect, read or publish streams
  • Reload the configuration without disconnecting existing clients (hot reloading)
  • Compatible with Linux, Windows and macOS, does not require any dependency or interpreter, it's a single executable

Table of contents

Installation

Standard

  1. Download and extract a precompiled binary from the release page.

  2. Start the server:

    ./rtsp-simple-server
    

Docker

Download and launch the image:

docker run --rm -it --network=host aler9/rtsp-simple-server

The --network=host flag is mandatory since Docker can change the source port of UDP packets for routing reasons, and this doesn't allow to find out the publisher of the packets. This issue can be avoided by disabling UDP and exposing the RTSP port:

docker run --rm -it -e RTSP_PROTOCOLS=tcp -p 8554:8554 -p 1935:1935 aler9/rtsp-simple-server

Basic usage

  1. Publish a stream. For instance, you can publish a video/audio file with FFmpeg:

    ffmpeg -re -stream_loop -1 -i file.ts -c copy -f rtsp rtsp://localhost:8554/mystream
    

    or GStreamer:

    gst-launch-1.0 rtspclientsink name=s location=rtsp://localhost:8554/mystream filesrc location=file.mp4 ! qtdemux name=d d.video_0 ! queue ! s.sink_0 d.audio_0 ! queue ! s.sink_1
    
  2. Open the stream. For instance, you can open the stream with VLC:

    vlc rtsp://localhost:8554/mystream
    

    or GStreamer:

    gst-launch-1.0 rtspsrc location=rtsp://localhost:8554/mystream name=s s. ! application/x-rtp,media=video ! decodebin ! autovideosink s. ! application/x-rtp,media=audio ! decodebin ! audioconvert ! audioresample ! autoaudiosink
    

    or FFmpeg:

    ffmpeg -i rtsp://localhost:8554/mystream -c copy output.mp4
    

Advanced usage and FAQs

Configuration

All the configuration parameters are listed and commented in the configuration file.

There are two ways to change the configuration:

  • By editing the rtsp-simple-server.yml file, that is

    • included into the release bundle

    • available in the root folder of the Docker image (/rtsp-simple-server.yml); it can be overridden in this way:

      docker run --rm -it --network=host -v $PWD/rtsp-simple-server.yml:/rtsp-simple-server.yml aler9/rtsp-simple-server
      
  • By overriding configuration parameters with environment variables, in the format RTSP_PARAMNAME, where PARAMNAME is the uppercase name of a parameter. For instance, the rtspPort parameter can be overridden in the following way:

    RTSP_RTSPPORT=8555 ./rtsp-simple-server
    

    Parameters in maps can be overridden by using underscores, in the following way:

    RTSP_PATHS_TEST_SOURCE=rtsp://myurl ./rtsp-simple-server
    

    This method is particularly useful when using Docker; any configuration parameter can be changed by passing environment variables with the -e flag:

    docker run --rm -it --network=host -e RTSP_PATHS_TEST_SOURCE=rtsp://myurl aler9/rtsp-simple-server
    

The configuration can be changed dinamically when the server is running (hot reloading) by writing to the configuration file. Changes are detected and applied without disconnecting existing clients, whenever it's possible.

Encryption

Incoming and outgoing streams can be encrypted with TLS (obtaining the RTSPS protocol). A self-signed TLS certificate is needed and can be generated with openSSL:

openssl genrsa -out server.key 2048
openssl req -new -x509 -sha256 -key server.key -out server.crt -days 3650

Edit rtsp-simple-server.yml, and set the protocols, encrypt, serverKey and serverCert parameters:

protocols: [tcp]
encryption: optional
serverKey: server.key
serverCert: server.crt

Streams can then be published and read with the rtsps scheme and the 8555 port:

ffmpeg -i rtsps://ip:8555/...

If the client is GStreamer, disable the certificate validation:

gst-launch-1.0 rtspsrc location=rtsps://ip:8555/... tls-validation-flags=0

If the client is VLC, encryption can't be deployed, since VLC doesn't support it.

Authentication

Edit rtsp-simple-server.yml and replace everything inside section paths with the following content:

paths:
  all:
    publishUser: myuser
    publishPass: mypass

Only publishers that provide both username and password will be able to proceed:

ffmpeg -re -stream_loop -1 -i file.ts -c copy -f rtsp rtsp://myuser:[email protected]:8554/mystream

It's possible to setup authentication for readers too:

paths:
  all:
    publishUser: myuser
    publishPass: mypass

    readUser: user
    readPass: userpass

If storing plain credentials in the configuration file is a security problem, username and passwords can be stored as sha256-hashed strings; a string must be hashed with sha256 and encoded with base64:

echo -n "userpass" | openssl dgst -binary -sha256 | openssl base64

Then stored with the sha256: prefix:

paths:
  all:
    readUser: sha256:j1tsRqDEw9xvq/D7/9tMx6Jh/jMhk3UfjwIB2f1zgMo=
    readPass: sha256:BdSWkrdV+ZxFBLUQQY7+7uv9RmiSVA8nrPmjGjJtZQQ=

WARNING: enable encryption or use a VPN to ensure that no one is intercepting the credentials.

Encrypt the configuration

The configuration file can be entirely encrypted for security purposes.

An online encryption tool is available here.

The encryption procedure is the following:

  1. NaCL's crypto_secretbox function is applied to the content of the configuration. NaCL is a cryptographic library available for C/C++, Go, C# and many other languages;

  2. The string is prefixed with the nonce;

  3. The string is encoded with base64.

After performing the encryption, it's enough to put the base64-encoded result into the configuration file, and launch the server with the RTSP_CONFKEY variable:

RTSP_CONFKEY=mykey ./rtsp-simple-server

Proxy mode

rtsp-simple-server is also a RTSP and RTMP proxy, that is usually deployed in one of these scenarios:

  • when there are multiple users that are receiving a stream and the bandwidth is limited; the proxy is used to receive the stream once. Users can then connect to the proxy instead of the original source.
  • when there's a NAT / firewall between a stream and the users; the proxy is installed on the NAT and makes the stream available to the outside world.

Edit rtsp-simple-server.yml and replace everything inside section paths with the following content:

paths:
  proxied:
    # url of the source stream, in the format rtsp://user:[email protected]:port/path
    source: rtsp://original-url

After starting the server, users can connect to rtsp://localhost:8554/proxied, instead of connecting to the original url. The server supports any number of source streams, it's enough to add additional entries to the paths section:

paths:
  proxied1:
    source: rtsp://url1

  proxied2:
    source: rtsp://url1

It's possible to save bandwidth by enabling the on-demand mode: the stream will be pulled only when at least a client is connected:

paths:
  proxied:
    source: rtsp://original-url
    sourceOnDemand: yes

RTMP protocol

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, doesn't support most RTSP codecs, doesn't support feedback mechanism). It is used when there's need of publishing or reading streams from a software that supports only RTMP (for instance, OBS Studio and DJI drones).

At the moment, only the H264 and AAC codecs can be used with the RTMP protocol.

Streams can be published or read with the RTMP protocol, for instance with FFmpeg:

ffmpeg -re -stream_loop -1 -i file.ts -c copy -f flv rtmp://localhost/mystream

or GStreamer:

gst-launch-1.0 -v flvmux name=s ! rtmpsink location=rtmp://localhost/mystream filesrc location=file.mp4 ! qtdemux name=d d.video_0 ! queue ! s.video d.audio_0 ! queue ! s.audio

Credentials can be provided by appending to the URL the user and pass parameters:

ffmpeg -re -stream_loop -1 -i file.ts -c copy -f flv rtmp://localhost:8554/mystream?user=myuser&pass=mypass

Publish from OBS Studio

In Settings -> Stream (or in the Auto-configuration Wizard), use the following parameters:

  • Service: Custom...
  • Server: rtmp://localhost
  • Stream key: mystream

If credentials are in use, use the following parameters:

  • Service: Custom...
  • Server: rtmp://localhost
  • Stream key: mystream?user=myuser&pass=mypass

Publish a webcam

Edit rtsp-simple-server.yml and replace everything inside section paths with the following content:

paths:
  cam:
    runOnInit: ffmpeg -f v4l2 -i /dev/video0 -f rtsp rtsp://localhost:$RTSP_PORT/$RTSP_PATH
    runOnInitRestart: yes

If the platform is Windows:

paths:
  cam:
    runOnInit: ffmpeg -f dshow -i video="USB2.0 HD UVC WebCam" -f rtsp rtsp://localhost:$RTSP_PORT/$RTSP_PATH
    runOnInitRestart: yes

Where USB2.0 HD UVC WebCam is the name of your webcam, that can be obtained with:

ffmpeg -list_devices true -f dshow -i dummy

After starting the server, the webcam can be reached on rtsp://localhost:8554/cam.

Publish a Raspberry Pi Camera

Install dependencies:

  1. Gstreamer

    sudo apt install -y gstreamer1.0-tools gstreamer1.0-rtsp
    
  2. gst-rpicamsrc, by following instruction here

Then edit rtsp-simple-server.yml and replace everything inside section paths with the following content:

paths:
  cam:
    runOnInit: gst-launch-1.0 rpicamsrc preview=false bitrate=2000000 keyframe-interval=50 ! video/x-h264,width=1920,height=1080,framerate=25/1 ! h264parse ! rtspclientsink location=rtsp://localhost:$RTSP_PORT/$RTSP_PATH
    runOnInitRestart: yes

After starting the server, the camera is available on rtsp://localhost:8554/cam.

Convert streams to HLS

HLS is a media format that allows to embed live streams into web pages, inside standard HTML tags. To generate HLS whenever someone publishes a stream, edit rtsp-simple-server.yml and replace everything inside section paths with the following content:

paths:
  all:
    runOnPublish: ffmpeg -i rtsp://localhost:$RTSP_PORT/$RTSP_PATH -c copy -f hls -hls_time 1 -hls_list_size 3 -hls_flags delete_segments -hls_allow_cache 0 stream.m3u8
    runOnPublishRestart: yes

The resulting files (stream.m3u8 and a lot of .ts segments) can be served by a web server.

The example above makes the assumption that published streams are encoded with H264 and AAC, since they are the only codecs supported by HLS; if streams make use of different codecs, they must be converted:

paths:
  all:
    runOnPublish: ffmpeg -i rtsp://localhost:$RTSP_PORT/$RTSP_PATH -c:a aac -b:a 64k -c:v libx264 -preset ultrafast -b:v 500k -f hls -hls_time 1 -hls_list_size 3 -hls_flags delete_segments -hls_allow_cache 0 stream.m3u8
    runOnPublishRestart: yes

Remuxing, re-encoding, compression

To change the format, codec or compression of a stream, use FFmpeg or Gstreamer together with rtsp-simple-server. For instance, to re-encode an existing stream, that is available in the /original path, and publish the resulting stream in the /compressed path, edit rtsp-simple-server.yml and replace everything inside section paths with the following content:

paths:
  all:
  original:
    runOnPublish: ffmpeg -i rtsp://localhost:$RTSP_PORT/$RTSP_PATH -c:v libx264 -preset ultrafast -b:v 500k -max_muxing_queue_size 1024 -f rtsp rtsp://localhost:$RTSP_PORT/compressed
    runOnPublishRestart: yes

On-demand publishing

Edit rtsp-simple-server.yml and replace everything inside section paths with the following content:

paths:
  ondemand:
    runOnDemand: ffmpeg -re -stream_loop -1 -i file.ts -c copy -f rtsp rtsp://localhost:$RTSP_PORT/$RTSP_PATH
    runOnDemandRestart: yes

The command inserted into runOnDemand will start only when a client requests the path ondemand, therefore the file will start streaming only when requested.

Redirect to another server

To redirect to another server, use the redirect source:

paths:
  redirected:
    source: redirect
    sourceRedirect: rtsp://otherurl/otherpath

Fallback stream

If no one is publishing to the server, readers can be redirected to a fallback path or URL that is serving a fallback stream:

paths:
  withfallback:
    fallback: /otherpath

Start on boot with systemd

Systemd is the service manager used by Ubuntu, Debian and many other Linux distributions, and allows to launch rtsp-simple-server on boot.

Download a release bundle from the release page, unzip it, and move the executable and configuration in the system:

sudo mv rtsp-simple-server /usr/local/bin/
sudo mv rtsp-simple-server.yml /usr/local/etc/

Create the service:

sudo tee /etc/systemd/system/rtsp-simple-server.service >/dev/null << EOF
[Unit]
After=network.target
[Service]
ExecStart=/usr/local/bin/rtsp-simple-server /usr/local/etc/rtsp-simple-server.yml
[Install]
WantedBy=multi-user.target
EOF

Enable and start the service:

sudo systemctl enable rtsp-simple-server
sudo systemctl start rtsp-simple-server

Monitoring

There are multiple ways to monitor the server usage over time:

  • The current number of clients, publishers and readers is printed in each log line; for instance, the line:

    2020/01/01 00:00:00 [2/1/1] [client 127.0.0.1:44428] OPTION
    

    means that there are 2 clients, 1 publisher and 1 reader.

  • A metrics exporter, compatible with Prometheus, can be enabled with the parameter metrics: yes; then the server can be queried for metrics with Prometheus or with a simple HTTP request:

    wget -qO- localhost:9998/metrics
    

    Obtaining:

    rtsp_clients{state="idle"} 2 1596122687740
    rtsp_clients{state="publishing"} 15 1596122687740
    rtsp_clients{state="reading"} 8 1596122687740
    rtsp_sources{type="rtsp",state="idle"} 3 1596122687740
    rtsp_sources{type="rtsp",state="running"} 2 1596122687740
    rtsp_sources{type="rtmp",state="idle"} 1 1596122687740
    rtsp_sources{type="rtmp",state="running"} 0 1596122687740
    

    where:

    • rtsp_clients{state="idle"} is the count of clients that are neither publishing nor reading
    • rtsp_clients{state="publishing"} is the count of clients that are publishing
    • rtsp_clients{state="reading"} is the count of clients that are reading
    • rtsp_sources{type="rtsp",state="idle"} is the count of rtsp sources that are not running
    • rtsp_sources{type="rtsp",state="running"} is the count of rtsp sources that are running
    • rtsp_sources{type="rtmp",state="idle"} is the count of rtmp sources that are not running
    • rtsp_sources{type="rtmp",state="running"} is the count of rtmp sources that are running
  • A performance monitor, compatible with pprof, can be enabled with the parameter pprof: yes; then the server can be queried for metrics with pprof-compatible tools, like:

    go tool pprof -text http://localhost:9999/debug/pprof/goroutine
    go tool pprof -text http://localhost:9999/debug/pprof/heap
    go tool pprof -text http://localhost:9999/debug/pprof/profile?seconds=30
    

Command-line usage

usage: rtsp-simple-server []

rtsp-simple-server v0.0.0

RTSP server.

Flags:
  --help     Show context-sensitive help (also try --help-long and --help-man).
  --version  print version

Args:
  []  path to a config file. The default is rtsp-simple-server.yml.

Compile and run from source

Install Go 1.15, download the repository, open a terminal in it and run:

go run .

You can perform the entire operation inside Docker:

make run

Links

Related projects

IETF Standards

Conventions

Issues
  • No sound from rtsp when push from rtmp

    No sound from rtsp when push from rtmp

    Which version are you using?

    v0.18.3

    Which operating system are you using?

    • [x] Linux amd64 standard
    • [x] Linux amd64 Docker
    • [ ] Linux arm64 standard
    • [ ] Linux arm64 Docker
    • [ ] Linux arm7 standard
    • [ ] Linux arm7 Docker
    • [ ] Linux arm6 standard
    • [ ] Linux arm6 Docker
    • [ ] Windows amd64 standard
    • [ ] Windows amd64 Docker (WSL backend)
    • [ ] macOS amd64 standard
    • [ ] macOS amd64 Docker
    • [ ] Other (please describe)

    Describe the issue

    No sound in RTSP when delivered from RTMP

    Describe how to replicate the issue

    I'm sorry, I'm Japanese and I'm not good at English, so I'm using translation.

    1. start the server (linux)
    2. Publish RTMP stream on OBS(rtmp://192.168.1.231/live/test)
    3. Read RTSP stream with VLC player ( no sound )
    4. (But if I watch hls in a browser, I can hear the sound)

    Screen Record

    Did you attach the server logs?

    $ ./rtsp-simple-server
    2022/05/11 00:47:51 INF rtsp-simple-server v0.18.3
    2022/05/11 00:47:51 INF [RTSP] listener opened on :8554 (TCP), :8000 (UDP/RTP), :8001 (UDP/RTCP)
    2022/05/11 00:47:51 INF [RTMP] listener opened on :1935
    2022/05/11 00:47:51 INF [HLS] listener opened on :8888
    2022/05/11 00:47:51 INF [RTMP] [conn 192.168.1.233:53136] opened
    2022/05/11 00:47:52 INF [RTMP] [conn 192.168.1.233:53136] is publishing to path 'live/test', 2 tracks
    2022/05/11 00:47:52 INF [HLS] [conn 192.168.1.233:53145] GET /live/test/index.m3u8
    2022/05/11 00:47:52 INF [HLS] [muxer live/test] created
    2022/05/11 00:47:52 INF [HLS] [muxer live/test] is converting into HLS
    2022/05/11 00:47:52 INF [HLS] [conn 192.168.1.233:53145] GET /live/test/stream.m3u8
    2022/05/11 00:47:59 INF [HLS] [conn 192.168.1.233:53179] GET /live/test/
    2022/05/11 00:47:59 INF [HLS] [conn 192.168.1.233:53179] GET /live/test/index.m3u8
    2022/05/11 00:47:59 INF [HLS] [conn 192.168.1.233:53179] GET /live/test/stream.m3u8
    2022/05/11 00:48:09 INF [HLS] [conn 192.168.1.233:53179] GET /live/test/1652230080.ts
    2022/05/11 00:48:17 INF [HLS] [conn 192.168.1.233:53179] GET /live/test/stream.m3u8
    2022/05/11 00:48:17 INF [HLS] [conn 192.168.1.233:53179] GET /live/test/1652230089.ts
    2022/05/11 00:48:17 INF [HLS] [conn 192.168.1.233:53179] GET /live/test/1652230080.ts
    2022/05/11 00:48:17 INF [HLS] [conn 192.168.1.233:53179] GET /live/test/1652230089.ts
    2022/05/11 00:48:17 INF [HLS] [conn 192.168.1.233:53179] GET /live/test/1652230080.ts
    2022/05/11 00:48:17 INF [HLS] [conn 192.168.1.233:53179] GET /live/test/1652230089.ts
    2022/05/11 00:48:17 INF [HLS] [conn 192.168.1.233:53179] GET /favicon.ico
    2022/05/11 00:48:25 INF [HLS] [conn 192.168.1.233:53179] GET /live/test/stream.m3u8
    2022/05/11 00:48:25 INF [HLS] [conn 192.168.1.233:53179] GET /live/test/1652230097.ts
    2022/05/11 00:48:34 INF [HLS] [conn 192.168.1.233:53179] GET /live/test/stream.m3u8
    2022/05/11 00:48:34 INF [HLS] [conn 192.168.1.233:53179] GET /live/test/1652230105.ts
    2022/05/11 00:48:39 INF [RTSP] [conn 192.168.1.233:57461] opened
    2022/05/11 00:48:39 INF [RTSP] [session 672451322] created by 192.168.1.233:57461
    2022/05/11 00:48:39 INF [RTSP] [session 672451322] is reading from path 'live/test', 2 tracks with UDP
    2022/05/11 00:48:42 INF [HLS] [conn 192.168.1.233:53179] GET /live/test/stream.m3u8
    2022/05/11 00:48:42 INF [HLS] [conn 192.168.1.233:53179] GET /live/test/1652230114.ts
    2022/05/11 00:48:42 INF [HLS] [conn 192.168.1.233:53179] GET /live/test/1652230105.ts
    2022/05/11 00:48:50 INF [HLS] [conn 192.168.1.233:53179] GET /live/test/stream.m3u8
    2022/05/11 00:48:50 INF [HLS] [conn 192.168.1.233:53179] GET /live/test/1652230122.ts
    2022/05/11 00:48:59 INF [HLS] [conn 192.168.1.233:53179] GET /live/test/stream.m3u8
    2022/05/11 00:48:59 INF [HLS] [conn 192.168.1.233:53179] GET /live/test/1652230130.ts
    2022/05/11 00:49:07 INF [HLS] [conn 192.168.1.233:53179] GET /live/test/stream.m3u8
    2022/05/11 00:49:07 INF [HLS] [conn 192.168.1.233:53179] GET /live/test/1652230139.ts
    ^C2022/05/11 00:49:09 INF shutting down gracefully
    2022/05/11 00:49:09 INF [RTMP] [conn 192.168.1.233:53136] closed (terminated)
    2022/05/11 00:49:09 INF [RTSP] [conn 192.168.1.233:57461] closed (terminated)
    2022/05/11 00:49:09 INF [RTSP] [session 672451322] destroyed (terminated)
    2022/05/11 00:49:09 INF [HLS] [muxer live/test] destroyed (terminated)
    2022/05/11 00:49:09 INF [RTSP] listener is closing
    2022/05/11 00:49:09 INF [HLS] listener is closing
    2022/05/11 00:49:09 INF [RTMP] listener is closing
    2022/05/11 00:49:09 INF waiting for external commands
    

    Did you attach a network dump?

    no

    opened by masudayasuto 0
  • RTSP audio backchannel support

    RTSP audio backchannel support

    As mentioned here already: https://github.com/aler9/gortsplib/issues/101

    Some details with SDP examples: https://www.happytimesoft.com/knowledge/audio-back-channel.html

    opened by nanosonde 0
  • RTSP stream shows black screen

    RTSP stream shows black screen

    Really cool software! I'm reporting an issue with one of my IP cameras.

    Which version are you using?

    v0.18.2

    Which operating system are you using?

    • [ ] Linux amd64 standard
    • [ ] Linux amd64 Docker
    • [ ] Linux arm64 standard
    • [ ] Linux arm64 Docker
    • [ ] Linux arm7 standard
    • [ ] Linux arm7 Docker
    • [ ] Linux arm6 standard
    • [ ] Linux arm6 Docker
    • [x] Windows amd64 standard
    • [ ] Windows amd64 Docker (WSL backend)
    • [ ] macOS amd64 standard
    • [ ] macOS amd64 Docker
    • [ ] Other (please describe)

    (Windows 11)

    Describe the issue

    I have an RTSP stream for a Reolink E1 Pro camera. I paste it into VLC's "Open Network Stream" and it works. RTSP Simple Server, when proxying this stream, displays only a black screen.

    I have another stream for a Reolink C1 Pro camera. This one works both in VLC and when proxied through RTSP Simple Server.

    Describe how to replicate the issue

    I edited rtsp-simple-server.yml. I deleted the "paths" section and replaced with this:

    paths: e1: source: rtsp://user:[email protected]:554/h264Preview_01_main sourceOnDemand: no c1: source: rtsp://user:[email protected]:554/h264Preview_01_main sourceOnDemand: no

    I then start the server. The proxy for "e1" shows only a black screen when connecting. The proxy for "c1" works fine.

    Additionally I set up capturing with FFMPEG (thanks for including an example) and it records a blank output for the E1. C1 records fine. Removed from config for simplicity.

    Server Logs

    When connecting to the C1

    2022/05/07 02:28:32 INF [RTSP] [session 149983978] is reading from path 'c1', 2 tracks with UDP 2022/05/07 02:28:32 DEB [RTSP] [conn 192.168.1.132:10872] [s->c] RTSP/1.0 200 OK CSeq: 6 RTP-Info: url=rtsp://192.168.1.235:8554/c1/trackID=0;seq=11175;rtptime=1074326760,url=rtsp://192.168.1.235:8554/c1/trackID=1;seq=16116;rtptime=1308019851 Server: gortsplib Session: 3619603012;timeout=60

    When connecting to the E1

    2022/05/07 02:28:59 INF [RTSP] [session 407119759] is reading from path 'e1', 2 tracks with UDP 2022/05/07 02:28:59 DEB [RTSP] [conn 192.168.1.132:11311] [s->c] RTSP/1.0 200 OK CSeq: 6 RTP-Info: url=rtsp://192.168.1.235:8554/e1/trackID=1;seq=52848;rtptime=3698614691 Server: gortsplib Session: 3131233561;timeout=6

    Wireshark Trace

    cameraTrace.zip

    opened by Liam2349 1
  • Implement Low-Latency HLS

    Implement Low-Latency HLS

    Fixes #556

    TODO:

    • [ ] sudden freezes with video+audio and hls.js
    • [ ] iPhone support (probably requires HTTP/2)
    • [ ] fully implement _HLS_skip
    • [ ] block on EXT-X-PRELOAD-HINT requests
    • [ ] dynamic SPS/PPS
    opened by aler9 1
  • Converting RTMP to RTSP is not working

    Converting RTMP to RTSP is not working

    Which version are you using?

    v0.18.1

    Which operating system are you using?

    • [ ] Linux amd64 standard
    • [x] Linux amd64 Docker
    • [ ] Linux arm64 standard
    • [ ] Linux arm64 Docker
    • [ ] Linux arm7 standard
    • [ ] Linux arm7 Docker
    • [ ] Linux arm6 standard
    • [ ] Linux arm6 Docker
    • [ ] Windows amd64 standard
    • [ ] Windows amd64 Docker (WSL backend)
    • [ ] macOS amd64 standard
    • [ ] macOS amd64 Docker
    • [ ] Other (please describe)

    Describe the issue

    If you stream via rtmp and receive via rtsp the stream freezes after three seconds. Receiving with rtmp does work.

    Describe how to replicate the issue

    1. https://github.com/aler9/rtsp-simple-server#from-obs-studio
    2. Watch rtsp stream using mpv
    opened by TKFRvisionOfficial 1
  • DJI Drone streaming issue

    DJI Drone streaming issue

    We try to stream video from DJI Go app running on iOS device connected to DJI Mavic 2s to a rtsp-simple-server running locally in the docker

    2022/04/25 22:46:49 INF [RTMP] [conn 172.17.0.1:63322] opened
    2022/04/25 22:46:50 INF [RTMP] [conn 172.17.0.1:63322] closed (unexpected packet (6))
    2022/04/25 22:46:50 INF [RTMP] [conn 172.17.0.1:63324] opened
    2022/04/25 22:46:50 INF [RTMP] [conn 172.17.0.1:63324] closed (unexpected packet (6))
    2022/04/25 22:46:50 INF [RTMP] [conn 172.17.0.1:63326] opened
    2022/04/25 22:46:50 INF [RTMP] [conn 172.17.0.1:63326] closed (unexpected packet (6))
    2022/04/25 22:46:51 INF [RTMP] [conn 172.17.0.1:63328] opened
    2022/04/25 22:46:51 INF [RTMP] [conn 172.17.0.1:63328] closed (unexpected packet (6))
    2022/04/25 22:46:51 INF [RTMP] [conn 172.17.0.1:63330] opened
    2022/04/25 22:46:51 INF [RTMP] [conn 172.17.0.1:63330] closed (unexpected packet (6))
    2022/04/25 22:46:51 INF [RTMP] [conn 172.17.0.1:63332] opened
    2022/04/25 22:46:52 INF [RTMP] [conn 172.17.0.1:63332] closed (unexpected packet (6))
    2022/04/25 22:46:52 INF [RTMP] [conn 172.17.0.1:63334] opened
    2022/04/25 22:46:52 INF [RTMP] [conn 172.17.0.1:63334] closed (unexpected packet (6))
    2022/04/25 22:46:52 INF [RTMP] [conn 172.17.0.1:63336] opened
    2022/04/25 22:46:52 INF [RTMP] [conn 172.17.0.1:63336] closed (unexpected packet (6))
    2022/04/25 22:46:53 INF [RTMP] [conn 172.17.0.1:63338] opened
    2022/04/25 22:46:53 INF [RTMP] [conn 172.17.0.1:63338] closed (unexpected packet (6))
    2022/04/25 22:46:53 INF [RTMP] [conn 172.17.0.1:63340] opened
    2022/04/25 22:46:53 INF [RTMP] [conn 172.17.0.1:63340] closed (unexpected packet (6))
    2022/04/25 22:46:53 INF [RTMP] [conn 172.17.0.1:63342] opened
    2022/04/25 22:46:54 INF [RTMP] [conn 172.17.0.1:63342] closed (unexpected packet (6))
    2022/04/25 22:46:54 INF [RTMP] [conn 172.17.0.1:63344] opened
    2022/04/25 22:46:54 INF [RTMP] [conn 172.17.0.1:63344] closed (unexpected packet (6))
    2022/04/25 22:46:54 INF [RTMP] [conn 172.17.0.1:63346] opened
    2022/04/25 22:46:54 INF [RTMP] [conn 172.17.0.1:63346] closed (unexpected packet (6))
    2022/04/25 22:46:55 INF [RTMP] [conn 172.17.0.1:63348] opened
    2022/04/25 22:46:55 INF [RTMP] [conn 172.17.0.1:63348] closed (unexpected packet (6))
    2022/04/25 22:46:55 INF [RTMP] [conn 172.17.0.1:63350] opened
    2022/04/25 22:46:55 INF [RTMP] [conn 172.17.0.1:63350] closed (unexpected packet (6))
    2022/04/25 22:46:55 INF [RTMP] [conn 172.17.0.1:63352] opened
    2022/04/25 22:46:56 INF [RTMP] [conn 172.17.0.1:63352] closed (unexpected packet (6))
    2022/04/25 22:46:56 INF [RTMP] [conn 172.17.0.1:63354] opened
    2022/04/25 22:46:56 INF [RTMP] [conn 172.17.0.1:63354] closed (unexpected packet (6))
    2022/04/25 22:46:56 INF [RTMP] [conn 172.17.0.1:63356] opened
    2022/04/25 22:46:57 INF [RTMP] [conn 172.17.0.1:63356] closed (unexpected packet (6))
    2022/04/25 22:46:57 INF [RTMP] [conn 172.17.0.1:63358] opened
    2022/04/25 22:46:57 INF [RTMP] [conn 172.17.0.1:63358] closed (unexpected packet (6))
    2022/04/25 22:46:57 INF [RTMP] [conn 172.17.0.1:63360] opened
    2022/04/25 22:46:57 INF [RTMP] [conn 172.17.0.1:63360] closed (unexpected packet (6))
    2022/04/25 22:46:57 INF [RTMP] [conn 172.17.0.1:63362] opened
    2022/04/25 22:46:58 INF [RTMP] [conn 172.17.0.1:63362] closed (unexpected packet (6))
    2022/04/25 22:46:58 INF [RTMP] [conn 172.17.0.1:63364] opened
    2022/04/25 22:46:58 INF [RTMP] [conn 172.17.0.1:63364] closed (unexpected packet (6))
    2022/04/25 22:46:58 INF [RTMP] [conn 172.17.0.1:63366] opened
    2022/04/25 22:46:59 INF [RTMP] [conn 172.17.0.1:63366] closed (unexpected packet (6))
    2022/04/25 22:46:59 INF [RTMP] [conn 172.17.0.1:63368] opened
    2022/04/25 22:46:59 INF [RTMP] [conn 172.17.0.1:63368] closed (unexpected packet (6))
    2022/04/25 22:46:59 INF [RTMP] [conn 172.17.0.1:63370] opened
    2022/04/25 22:46:59 INF [RTMP] [conn 172.17.0.1:63370] closed (unexpected packet (6))
    2022/04/25 22:46:59 INF [RTMP] [conn 172.17.0.1:63372] opened
    2022/04/25 22:47:00 INF [RTMP] [conn 172.17.0.1:63372] closed (unexpected packet (6))
    2022/04/25 22:47:00 INF [RTMP] [conn 172.17.0.1:63374] opened
    ^C2022/04/25 22:47:01 INF shutting down gracefully
    2022/04/25 22:47:01 INF [RTSP] [session 834561455] destroyed (terminated)
    2022/04/25 22:47:01 INF [RTMP] [conn 172.17.0.1:63374] closed (terminated)
    2022/04/25 22:47:01 INF [RTSP] listener is closing
    2022/04/25 22:47:01 INF [HLS] listener is closing
    2022/04/25 22:47:01 INF [RTMP] listener is closing
    2022/04/25 22:47:01 INF waiting for external commands
    
    bug 
    opened by darvin 4
Releases(v0.18.3)
Owner
Alessandro Ros
Software and robotics engineer, i deal with ML-based services, unmanned vehicles and anything that can be modeled and controlled. MSc @ PoliMi
Alessandro Ros
CasaOS - A simple, easy-to-use, elegant open-source home server system.

CasaOS - A simple, easy-to-use, elegant open-source home server system. CasaOS is an open-source home server system based on the Docker ecosystem and

IceWhale 3.6k May 11, 2022
A proxy server than converts JSON request bodies to protocol buffers

Welcome to Protoxy ?? What is Protoxy? Protoxy allows you to test your REST APIs that use Protocol Buffer serialization through Postman and other API

null 23 Apr 4, 2022
OpenAPI specs for your Go server, generated at server runtime. No CLI, no code generation, and no HTTP

Overview "oas" is short for "OpenAPI Spec". Go package for generating OpenAPI docs at runtime. Non-features: No code generation. No CLI. No magic comm

Nelo Mitranim 0 Dec 3, 2021
Go web server - A web server that can accept a GET request and serve a response.

go_web_server A web server that can accept a GET request and serve a response. Go is a great language for creating simple yet efficient web servers an

Gilbert Ngeno 0 Jan 3, 2022
a simple http server as replacement of python -m http.server

ser a simple http server as replacement of python -m http.server

Changkun Ou 4 Feb 16, 2022
A Language Server Protocol (LSP) server for Jsonnet

Jsonnet Language Server A Language Server Protocol (LSP) server for Jsonnet. Features Jump to definition self-support.mp4 dollar-support.mp4 Error/War

Grafana Labs 53 May 16, 2022
Reverse proxy with automatically obtains TLS certificates from Let's Encrypt

Русскоязычное описание ниже (Russian below). English description Home page: https://github.com/rekby/lets-proxy2 Features: http-01 and tls-alpn-01 val

Timofey Koolin 62 Apr 21, 2022
Fully featured and highly configurable SFTP server with optional FTP/S and WebDAV support - S3, Google Cloud Storage, Azure Blob

SFTPGo Fully featured and highly configurable SFTP server with optional FTP/S and WebDAV support, written in Go. Several storage backends are supporte

Nicola Murino 4.2k May 18, 2022
⚡ A fast, lightweight, and secure chat protocol, client and server, written in Go.

⚡ A fast, lightweight, and secure chat protocol, client and server, written in Go.

Bolt 16 Jan 19, 2022
RBTI Golang Server uses PostgreSQL and for its main database and uses Elasticsearch

RBTI Golang Server This server is used for my thesis project, it uses PostgreSQL and for its main database and uses Elasticsearch for faster query spe

Haikal Ikhwan 0 Jan 17, 2022
✨ A lightweight HTTP server based on GO, will try to detect your OS and architecture and return as SHELL script. ✨

✨ A lightweight HTTP server based on GO, will try to detect your OS and architecture and return as SHELL script. ✨

Salvydas Lukosius 6 May 5, 2022
:tophat: Small self-contained pure-Go web server with Lua, Markdown, HTTP/2, QUIC, Redis and PostgreSQL support

Web server with built-in support for QUIC, HTTP/2, Lua, Markdown, Pongo2, HyperApp, Amber, Sass(SCSS), GCSS, JSX, BoltDB (built-in, stores the databas

Alexander F. Rødseth 2k May 19, 2022
A feature flag solution, with only a YAML file in the backend (S3, GitHub, HTTP, local file ...), no server to install, just add a file in a central system and refer to it. 🎛️

??️ go-feature-flag A feature flag solution, with YAML file in the backend (S3, GitHub, HTTP, local file ...). No server to install, just add a file i

Thomas Poignant 424 May 11, 2022
High-performance PHP application server, load-balancer and process manager written in Golang

[RR2-BETA] RoadRunner is an open-source (MIT licensed) high-performance PHP application server, load balancer, and process manager. It supports runnin

Spiral Scout 6.4k May 11, 2022
Oogway is a simple web server with dynamic content generation and extendability in mind supporting a Git based workflow.

Oogway Oogway is a simple web server with dynamic content generation and extendability in mind supporting a Git based workflow. It's somewhere in betw

Emvi 5 Mar 9, 2022
Opinionated boilerplate Golang HTTP server with CORS, OPA, Prometheus, rate-limiter for API and static website.

Teal.Finance/Server Opinionated boilerplate HTTP server with CORS, OPA, Prometheus, rate-limiter… for API and static website. Origin This library was

teal.finance 7 Mar 26, 2022
HTTP server receives events and publishes them to STAN

Publishes events to Nats Streaming(STAN) synchornously and asynchronously. Cache events's publish-state using Redis and Store events using MongoDB.

Mehdi 15 Jan 24, 2022
GRPC And REST Server Code challenge

Code challenge This repo contains 2 entry points. 1. GRPC Server (cmd/grpcserver/main.go) The grpc server exposes two rpcs: rpc SaveVLAN (VLAN) return

Net Reply 0 Nov 16, 2021