98ab3009ea
It is now possible to define forward destinations for each path configuration. For each destination, the server will create a client that will forward the stream to the intended destination. Supported protocols are RTSP, RTMP, SRT. API and metrics have also been improved to allow monitoring the new forwarding system. --------- Co-authored-by: aler9 <46489434+aler9@users.noreply.github.com>
48 lines
3.4 KiB
Markdown
48 lines
3.4 KiB
Markdown
<h1 align="center">
|
|
<a href="https://mediamtx.org">
|
|
<img src="logo.png" alt="MediaMTX">
|
|
</a>
|
|
|
|
<br>
|
|
<br>
|
|
|
|
[](https://mediamtx.org)
|
|
[](https://github.com/bluenviron/mediamtx/actions/workflows/test.yml?query=branch%3Amain)
|
|
[](https://github.com/bluenviron/mediamtx/actions/workflows/lint.yml?query=branch%3Amain)
|
|
[](https://app.codecov.io/gh/bluenviron/mediamtx/tree/main)
|
|
[](https://github.com/bluenviron/mediamtx/releases)
|
|
[](https://hub.docker.com/r/bluenviron/mediamtx)
|
|
|
|
</h1>
|
|
|
|
<br>
|
|
|
|
_MediaMTX_ is a ready-to-use and zero-dependency live media server and media proxy that allows to publish, read, proxy, record and playback real-time video and audio streams. It has been conceived as a "media router" that routes media streams from one end to the other, with a focus on efficiency and portability.
|
|
|
|
<div align="center">
|
|
|
|
| [Install](https://mediamtx.org/docs/kickoff/install) | [Documentation](https://mediamtx.org/docs/kickoff/introduction) |
|
|
| ---------------------------------------------------- | --------------------------------------------------------------- |
|
|
|
|
</div>
|
|
|
|
<h3>Features</h3>
|
|
|
|
- [Publish streams](https://mediamtx.org/docs/features/publish) to the server with Media-over-QUIC, SRT, WebRTC, RTSP, RTMP, HLS, MPEG-TS, RTP, using FFmpeg, GStreamer, OBS Studio, Python , Golang, Unity, Web browsers, Raspberry Pi Cameras and more.
|
|
- [Read streams](https://mediamtx.org/docs/features/read) from the server with Media-over-QUIC, SRT, WebRTC, RTSP, RTMP, HLS, using FFmpeg, GStreamer, VLC, OBS Studio, Python , Golang, Unity, Web browsers and more.
|
|
- Streams are automatically converted from a protocol to another
|
|
- Serve several streams at once in separate paths
|
|
- Reload the configuration without disconnecting existing clients (hot reloading)
|
|
- [Serve always-available streams](https://mediamtx.org/docs/features/always-available) even when the publisher is offline
|
|
- [Record streams](https://mediamtx.org/docs/features/record) to disk in fMP4 or MPEG-TS format
|
|
- [Playback recorded streams](https://mediamtx.org/docs/features/playback) from disk
|
|
- [Authenticate](https://mediamtx.org/docs/features/authentication) users with internal, HTTP or JWT authentication
|
|
- [Forward streams](https://mediamtx.org/docs/features/forward) to other servers
|
|
- [Proxy requests](https://mediamtx.org/docs/features/proxy) to other servers
|
|
- [Control](https://mediamtx.org/docs/features/control-api) the server through the Control API
|
|
- [Extract metrics](https://mediamtx.org/docs/features/metrics) from the server in a Prometheus-compatible format
|
|
- [Monitor performance](https://mediamtx.org/docs/features/performance) to investigate CPU and RAM consumption
|
|
- [Run hooks](https://mediamtx.org/docs/features/hooks) (external commands) when clients connect, disconnect, read or publish streams
|
|
- Compatible with Linux, Windows and macOS, does not require any dependency or interpreter, it's a single executable
|
|
- ...and many [others](https://mediamtx.org/docs/kickoff/introduction).
|