Overview
All features
KRZN Live brings the live feeds of the satellite locations to one main location, instead of a video call: each site sends its own clean, high-quality feed, and the central team watches, records, talks to and uses every feed in production (vMix, OBS). It's one program (krznlive.exe), with a dashboard in its own window.
This page lists everything it does. Each section links to the detailed documentation when there is one.
At a glance
| Area | What you get |
|---|---|
| Receiving the sites | One stream path per site, SRT or RTMP, through the VPS edge, the tunnel or the home address, with an optional stream key |
| Watching | Multiviewer of up to 9 feeds, TV mode on a second screen, audio meters, feed info (resolution, frame rate, codec, bitrate, 4K) |
| Production | Every feed as an NDI® source for vMix, with tally, backup feed, slate and fixed format |
| Inputs | Cameras and capture cards (USB, HDMI, SDI), NDI sources, media files in a loop |
| Recording | One click per source or all at once, timeline with instant replay, clips, exports, share links, compression, automatic cleanup |
| Communication | Intercom: voice call and text chat between central and the sites, from a link |
| Reliability | VPS edge, reconnecting slate, feed health, alerts on the phone, cluster of central computers (standby, load balancing) |
| Operation | History of 120 days, events, logs, presets, signed automatic updates, download page |
Receiving the sites
- Stream paths: one path per site (for example
north), with a label shown everywhere ("North Region"). Add, rename and remove them in Stream Paths; they're saved inkrznlive.yml, keeping its comments. - Publish fields for each encoder: for each path, the exact server and stream key to type into OBS or vMix, for RTMP or SRT, with copy buttons.
- Routes: VPS (through the VPS, nothing to open on the router), Home (the public IP of the main location, with port forwarding) and LAN (same network). See Dashboard.
- VPS edge: a second KRZN Live on the VPS receives the sites directly with SRT or RTMP, and central pulls each feed with its own SRT connection: a loss on one feed never delays the others. See VPS edge.
- Tunnel: the embedded frp client exposes this computer through the VPS without opening ports on the router, with end-to-end checks every 30 seconds and a restart when it's stuck. See Tunnel.
- Stream keys (optional, per path): a path can require a key; without one, the path name identifies the site.
- SRT latency per site, from the measured round trip.
- Every protocol of KRZN Live: SRT, RTMP, RTSP, WebRTC, HLS, MoQ, with automatic conversion from one to another. See Publish and Read.
Watching
- Multiviewer: up to 9 feeds at once, WebRTC (under a second) or HLS, per tile; each tile shows the feed and the status of its site.
- TV mode: the multiviewer in its own window, on a second screen or a TV, full screen with F; it follows the layout of the dashboard.
- Audio meters of every feed.
- Feed info: resolution, frame rate, codec, bitrate and sound of each source, with a 4K badge, in Stream Paths, Recordings, NDI Inputs and the Multiviewer.
- Viewers: who watches each feed, with which protocol.
- External player: open a feed in ffplay or VLC from this computer.
- Watch URLs for each protocol and route, with copy buttons.
Production: NDI®
- NDI output per path: each feed becomes an NDI source on the network ("KRZN Live - North Site") that vMix, OBS, TriCaster and NDI Studio Monitor find by name. Decoded once with the graphics card, sent as full NDI.
- Never freezes: when a site drops, its source keeps the last picture, then shows a "reconnecting" slate (standard or your own image): vMix inputs never disappear.
- Fixed format (1080p30, 1080p25, 720p30, 2160p30, ...): every site matches the vMix project, with black bars when needed.
- Backup feed: another path is used while the main one is offline, and the source switches back by itself.
- Tally: the dashboard shows when a source is LIVE or in preview in vMix.
- Lip sync correction per path (±500 ms).
- Discovery server and groups for larger networks.
- Test button: publishes color bars and a beep, and checks that NDI works on this computer.
- See NDI output.
Inputs
- Cameras and capture cards plugged into this computer (USB, HDMI, SDI cards through DirectShow), with the format (size, frame rate) and the audio device.
- NDI inputs: receive an NDI source of the network (a PTZ camera, another vMix) as a stream path, in its own tab.
- Media files in a loop (a bumper, a countdown), from the media folder.
- Encoding of the inputs: quality, H.264 or H.265, size and frame rate; graphics card first, then the CPU.
- Every input is a stream path like a site: watched, recorded, sent as NDI, shown in the Multiviewer.
Recording
- Recordings console: every source in one place, REC / PAUSE / STOP, the time recorded, the file being written, Record all / Stop all.
- Timeline: the recording of the selected source with its frames, zoom, gaps; click to replay that moment, LIVE to go back.
- Instant replay: Space or ← goes back a few seconds while live.
- Marks and clips: Mark In / Out, preview, save a clip; quick clips of the last 30 seconds, 2 or 5 minutes in one click.
- Clips library: rename, delete, export (several formats) and share links (a page that plays the clip, on a separate port, without access to the dashboard).
- Record settings per source or for all: how long files are kept (1 day to forever), length of a file (15 minutes to 2 hours), format (MP4 or MPEG-TS).
- Compression of finished files with the graphics card, in the background, to save disk space (the file being recorded is never touched).
- Storage: free space and recording time left; the oldest recordings are deleted when the disk is almost full (saved clips are never deleted).
- Library: play, download, show in folder, delete.
- See Record and Playback.
Intercom
- Voice call between central (the director, at the dashboard) and every site, like a Discord call: push-to-talk (button or Space) or open mic, who's speaking, deafen, volume per person.
- Director and Open modes: in Director mode central has priority; central mutes a site or everyone.
- Text chat and status buttons for the sites ("ready", "problem", ...), shown on the Multiviewer tiles.
- Site pages: each site gets one link, tied to its stream path: its page shows its feed status and "Join the call". No account, nothing to install, any browser, phone or laptop. Over HTTPS through the VPS.
- Very light: about 25 kbit/s while someone talks, nothing when the mics are closed. The voices never go into the feeds or the recordings.
- The Intercom tab can pop out into its own window.
Reliability
- Reconnecting slate: viewers and vMix stay connected while a site drops and comes back.
- Feed health: bitrate, round trip, loss and dropped packets of each SRT feed (also between the site and the edge), a score, the SRT latency to use, a sparkline.
- Bitrate alert: a warning when a feed receives more than a limit (default 12 Mbit/s); the feed is never changed.
- Alerts on the phone: Telegram, or a webhook (Discord, Slack, WhatsApp gateways), for feeds going offline or unhealthy, tunnel problems, errors; bursts are grouped.
- Events: streams online / offline, encoder reconnections, corrupted frames, bitrate drops, tunnel ports, public IP changes, NDI and cluster events; new errors are notified on every page.
- Crash supervisor: the app restarts by itself if it stops; it keeps the computer awake while streams are online.
- Cluster of central computers:
- Standby: a second computer takes over in about 8 seconds when the main one stops (tunnel, site pages, intercom, recordings, NDI outputs), with the same NDI names, so vMix keeps its inputs.
- Load balancing: the NDI outputs, inputs and recordings are spread over the computers; a computer that stops hands its work to the others.
- Join with a code or a QR, configuration copied to every computer, Test failover, update of the whole cluster without stopping it.
- See Cluster.
- Go Live: the program is sent once to a Go Live server on a VPS, that sends it to Facebook, YouTube and other platforms. It goes live and ends by itself on a schedule (even with the central computer off), shows a slate when the program is missing so the live never stops, never cuts a live program at the end time, and sends its own alerts. See Go Live.
Operation
- Status page: uptime, online streams, viewers, bandwidth, errors, tunnel, home public IP, NDI, the cluster, servers and latest events.
- History: bitrate, viewers and packet loss of every feed, sampled every minute and kept for 120 days, one chart per measure, one color per site.
- Logs: the full log in real time, with filters, search, pause and download.
- Ports & URLs: every port, its URL for each route, and whether it's reachable through the VPS.
- Settings: applied at once and saved into
krznlive.yml(comments kept): servers, tunnel, VPS edge, NDI, alerts, bitrate, storage, cluster, general. - Presets: save and restore whole setups (addresses, tunnel, paths); export and import them. The dashboard password and the tunnel token are never exported.
- Import of an old frpc / KRZN Live setup.
- Dashboard password (stored as a hash, lockout after 5 wrong passwords); without one, the dashboard opens only on this computer.
- Windows app: its own window, tray icon, single instance (it never starts by itself: open it when needed), a question before closing while streams are live.
- Automatic updates: new versions are downloaded from the KRZN Live update server and checked with a signature; they're installed only when you click (never in the middle of a live event).
- Download page (password protected) with the whole app folder, and
Install NDI and FFmpeg.batto set up a new computer. - Control API and metrics for advanced use. See Control API and Metrics.
Limits to know
- Sites that send to the home address (Home route) are not covered by the cluster failover: the router sends them to one computer.
- Cameras plugged into a computer stay on that computer.
- NDI needs a wired gigabit network: about 100 Mbit/s per receiver at 1080p30.
- The voice call for sites outside the main location needs the HTTPS address of the intercom on the VPS.
- Email alerts and bonding of several connections (SRTLA) are not built yet.