B
bluenviron/mediamtx
Mediamtx
MediaMTX is a multi-protocol media server designed for routing, proxying, and recording real-time audio and video streams. It functions as a programmable media router and a gateway between streaming standards such as RTMP, RTSP, and WebRTC, enabling the conversion of live media between different protocols.
The server distinguishes itself through on-the-fly format transmuxing and protocol-agnostic routing, which decouples input and output protocols via an internal media bus. It features a programmable automation system that executes external shell commands via event hooks triggered by client connections or disconnections.
The platform includes capabilities for disk-buffered stream recording, in-memory stream multiplexing, and stateless proxy forwarding. Administrative management is handled through an HTTP-based control interface and a REST API, while security is managed via token-based authentication and identity validation.
The server also supports the export of performance metrics to external monitoring systems to track health and resource consumption.
Features
- Live Media Streaming - Broadcasting real-time audio and video streams from one source to multiple viewers across various protocols.
- Programmable Media Routers - Combines a streaming server with event hooks and a control interface to automate media flow.
- Live Streaming Servers - Functions as a high-performance server for relaying and broadcasting real-time audio and video traffic.
- On-the-fly Media Streaming - Performs real-time conversion of media containers between different protocols without re-encoding the data.
- Realtime Media Routing - Routes real-time audio and video across multiple protocols with low-latency delivery.
- Media Streaming Proxies - Acts as a transparent intermediary that proxies and relays live media traffic between clients and external servers.
- Media Protocol Servers - Provides a multi-protocol server for routing, proxying, and recording real-time audio and video streams.
- Streaming Protocol Gateways - Converts live media between RTMP, RTSP, and WebRTC standards to ensure compatibility.
- Media Streaming Protocol Bridging - Bridges diverse media streaming protocols like RTMP, RTSP, and WebRTC via an internal media bus.
- Stream Recorders - Provides capabilities to capture and save live audio and video streams directly to local storage.
- Event Automation Hooks - Automatically triggers external shell commands based on media stream events such as client connectivity.
- Server Management APIs - Ships a REST API and HTTP control interface for programmatic management of server settings and active streams.
- Server Administration APIs - Exposes a REST API for modifying server configuration and managing active streams in real time.
- Authenticated Media Access - Implements token-based and HTTP-driven authentication to restrict access to private live media streams.
- Media Proxies - Acts as an intermediary for live media traffic to manage flow and bypass network restrictions.
- Live Stream Recorders - Captures incoming real-time video and audio feeds and saves them to disk for archiving.
- Media Stream Recording - Saves incoming live streams to disk using specific container formats for later playback.
- Media Server Automation - Executes external scripts and commands automatically based on stream events like client connections.
- Stateless Media Proxies - Relays incoming stream requests to external remote endpoints as a transparent, stateless intermediary.
- Request Access Restrictions - Restricts access to live streams using token-based authentication and identity validation via HTTP requests.
- Event-Driven Hooks - Implements mechanisms to execute custom shell scripts in response to server events like client connections.
- Media and Communication - Media server for video and audio streaming.
Star history
How this analysis was created: This summary and feature list were written by an AI model that read the project's README and public documentation pages. Each feature links to the documentation it came from; stars, license and language come straight from the GitHub API. The model does not read the source code, and the analysis is refreshed when the project is re-analysed. Learn more on our About page.
