The reason is pretty obvious: this project started as a RTSP server but has evolved into a much more versatile media server (i like to call it a 'media broker', a message broker for media streams), that is not tied to the RTSP protocol anymore. Rtsp-simple-server is being rebranded as MediaMTX. Compatible with Linux, Windows and macOS, does not require any dependency or interpreter, it's a single executable.Natively compatible with the Raspberry Pi Camera.Run external commands when clients connect, disconnect, read or publish streams.Reload the configuration without disconnecting existing clients (hot reloading).Query and control the server through an HTTP API.Redirect readers to other RTSP servers (load balancing).Authenticate users use internal or external authentication.Serve multiple streams at once in separate paths.For instance, it's possible to publish a stream with RTSP and read it with HLS Streams are automatically converted from a protocol to another.Proxy streams from other servers or cameras, always or on-demand.

Low-Latency HLS, MP4-based HLS, legacy HLSĪnd can be read from the server with: protocol H264, MPEG-2 Audio (MP3), MPEG-4 Audio (AAC)

H264, H265, VP8, VP9, AV1, MPEG-2 Video, M-JPEG, MPEG-4 Video (H263, Xvid), MPEG-2 Audio (MP3), MPEG-4 Audio (AAC), Opus, G711, G722, LPCM and any RTP-compatible codec

Live streams can be published to the server with: protocol MediaMTX / rtsp-simple-server is a ready-to-use and zero-dependency server and proxy that allows users to publish, read and proxy live video and audio streams.

Raspberry pi network bandwidth monitor