The engine runs on a 64-bit Linux host, on bare metal or in a VM. Plan the machine around the work you want it to do — mostly the number of inputs and the transcode load.
Operating system
- 64-bit Debian, Ubuntu or CentOS.
- Root access for the installer.
Transcoding hardware (optional)
Only needed if you plan to transcode. If you simply restream or pass sources through untouched, no transcoding hardware is required — see Codecs and passthrough.
- A GPU accelerates transcoding and lets one machine carry far more channels at a lower CPU cost: Intel QuickSync, NVIDIA NVENC and AMD VAAPI are supported, and can run in parallel across cards.
- Without a GPU, the engine can transcode on the CPU (x264/x265).
CPU transcoding can overload the CPU quickly and is not recommended — use a GPU for any real transcoding load. See Hardware acceleration.
Input hardware (optional)
- DVB-S/S2, DVB-T/T2, DVB-C and ATSC tuner cards.
- SAT>IP network tuner pools.
No tuner hardware? You can still ingest over the network — SRT, RTMP, RTSP, HLS, DASH and multicast — see Inputs and Ingest › IP sources.
Check what the host sees
# GPUs on the host
lspci | grep -Ei "vga|display|nvidia|amd"
# DVB adapters, if any
ls /dev/dvb
Ports the engine uses
- 22 / TCP — SSH (admin, and the master installs and syncs each node over SSH)
- 80 / TCP and 443 / TCP — control panel and media delivery (HTTP / HTTPS)
- 1935 / TCP — RTMP publish and playback
- 4327 / TCP — database (edge nodes reach the master’s database in a cluster)
- 8443 / TCP — cluster control channel (encrypted)
The full table with direction and the single-server vs. cluster notes is on Installation and Updates › Firewall and networking.
Firewall note. The installer takes over the host firewall so the engine ports are reachable. Read Installation and Updates › Firewall and networking before installing on a shared host.