What the engine does Print

  • overview, streaming engine, self-hosted, ingest, transcode, cdn, getting started
  • 0

Medusa Streaming Engine is a single, self-hosted application that runs an entire live-TV and video-on-demand operation on hardware you own — from pulling in a source to billing the person who watches it. There is no mandatory cloud and no per-stream fee: one engine ingests, decrypts, transcodes, packages, protects, delivers and monetises.

The signal path

Every channel follows the same path through the engine:

Source → Ingest → Transcode → Package → Protect → Deliver → Play

  • Ingest — take in a satellite, terrestrial, cable, capture or network source, and decrypt it if needed.
  • Transcode — re-encode the picture and sound, on the GPU, into the codecs and resolutions you need (or pass it through untouched).
  • Package — cut the result into HLS and DASH (and other output formats) for players.
  • Protect — optionally encrypt the output and filter who may watch.
  • Deliver — serve it through the built-in CDN to players, apps and other servers.
You run all of this from the web Medusa Panel, and everything in the panel is also available through a full REST API for automation.

What it can ingest

  • Broadcast tuners — DVB-S / S2, DVB-T / T2, DVB-C, ATSC and ISDB-T via a DVB PCIe card, with DiSEqC, Unicable and multistream / PLS. See DVB tuners.
  • SAT>IP network tuners. See SAT>IP.
  • IP sources over UDP / RTP multicast, HTTP / HLS, SRT, RTMP and RTSP. See IP sources.
  • HDMI / SDI capture cards. See HDMI capture.
  • Web and VOD — pull YouTube and other web sources into the video library. See YouTube and VOD.
  • Encrypted inputs — descramble at ingest with SoftCAM or a CAM module. See ClearKey and SoftCAM.

What it does to the picture

  • Transcode in H.264, HEVC or MPEG-2, with hardware acceleration on Intel Quick Sync, NVIDIA NVENC / NVDEC (with AV1) and AMD (VAAPI). See Hardware acceleration.
  • Adaptive bitrate ladders — produce many renditions from one source and store them as reusable profiles. See Bitrate ladders.
  • Filters — deinterlace, scale, logo and text overlays, privacy blur. See Filters and overlays.
  • Colour, HDR and audio — BT.709 and BT.2020, PQ and HLG; audio in AAC, AC3, MP2 or MP3; subtitles in DVB, TTML or WebVTT, including burn-in. See Codecs and passthrough.
  • Or pass through — copy a stream untouched when no re-encoding is needed.

How it delivers

  • Output formats — HLS, MPEG-DASH, HTTP-TS, RTMP and RTMP push, RTSP, RTP, UDP, TCP, SRT and file. See Packaging and caching.
  • Built-in CDN — edge servers with live prefetch, in-memory (tmpfs) cache and automatic load balancing. See Built-in CDN and edge nodes.

How it protects content

  • Output DRM on DASH through a key service. See Output DRM.
  • Access control — output-encryption checks, GeoIP country whitelists, HTTP referer and user-agent filters, trusted proxies and an RTMP-push allowlist.

How it monetises

  • Subscribers with connection limits and playback access rules.
  • Bouquets and packages to group and sell channels. See Bouquets, prices and limits.
  • Sub-resellers with their own credit balance and API. See Sub-resellers and API.
  • Playback analytics and an audit log to see what is watched.

Video on demand and the guide

  • Movies, series and episodes with metadata from TMDB, plus file and storage management.
  • EPG from an XMLTV source for the programme guide.

How it scales

  • Multi-server clustering — one master plus CDN and transcode servers, with deploy-and-sync, capacity assessment, monitoring and scheduled database backups. See Master and slave nodes and Adding nodes.
New here? Start with System requirements, then run the trial quick start.

Was this answer helpful?

« Back