A streaming server: it receives the stream from the streamer's PC and hands it to viewers in different forms โ to a browser, to VLC, with under a second of latency or in a way that survives a mobile network.
In Peregovorka, MediaMTX takes the stream in over SRT and delivers it over HLS, WHEP and RTSP. The server does not re-encode video: the streamer's graphics card encodes both qualities, so a powerful machine is not needed.
When you need your own private broadcast: a stream from one computer watched by people in a browser and in a player, on phones and on desktops.
In Peregovorka MediaMTX takes the stream in over SRT and delivers it over HLS (stable, 6โ8 seconds of latency), WHEP (under a second) and RTSP for VLC. Video is not re-encoded on the server: both qualities, 3440ร1440 and 1720ร720, are encoded by the streamer's graphics card, and only the audio track is converted to AAC for Safari, which costs a few percent of one CPU core.
auth_request check in nginx, and external players use a separate secret.If broadcasts are public and aimed at a wide audience, ready-made platforms are simpler.
Terms explained โ now let's get to work: tell us about the task and we'll turn it into a clear work plan.