Vucos Logo

Origin & Media Server

The headend that turns camera feeds, satellite acquisitions, and file deliveries into clean, packaged, DRM-protected streams across every device — with broadcast-grade reliability and cloud-native elasticity.

40+
Concurrent live encodes per tenant
< 2 s
Encoder failover on frame loss
4K HDR
Supported live ladder peak
99.99%
Origin availability SLO

From Ingest to Origin, Engineered for Scale

Vucos Origin & Media Server is the transcoding and packaging spine of the platform. It ingests live signals over SRT, RTMP, RIST, or SDI, runs them through parallel adaptive bitrate encoding ladders, handles SCTE-35 ad markers faithfully, and writes out HLS and DASH manifests with multi-DRM packaging in a single pass. The same pipeline handles VOD mezzanine files through accelerated transcoding, with automated QC, subtitle burn-in, and thumbnail generation built into the workflow.

Why this matters

Everything viewers see begins here. A dropped SCTE-35 cue means a missed ad break and lost revenue. A misaligned audio track means thousands of complaints. An encoding ladder that is wrong for the content type costs rebuffers, data, and churn. Most operators end up with a patchwork of encoders from the broadcast era bolted to cloud packaging tools — and the seams show up as incidents the support team can never fully explain.

Vucos runs the whole headend as one system. The same platform handles 24/7 linear channels, cloud playout schedules, live event bursts, and bulk VOD transcoding — all emitting to the same origin and manifest contract. That unification is what allows the rest of the stack (ad insertion, DRM, analytics) to actually work predictably.

What the headend does

Live encoding & transcoding

Adaptive bitrate ladders up to 4K HDR (HEVC, AV1, H.264), hardware-accelerated GPU encoding, and redundant encoder pairs with automatic failover on frame loss.

Cloud playout

Linear channel scheduling, graphics overlays, logo bug insertion, live-to-VOD recording, and 24/7 simulcast — managed through a scheduler API and a visual timeline.

Packaging & manifest

Just-in-time HLS and DASH packaging, CMAF low-latency profiles, DVB-DASH compliance, and multi-period manifests for ad insertion and blackout handling.

Multi-DRM packaging

Widevine, FairPlay, and PlayReady keys written in a single pass. CPIX-compliant key exchange with external key providers and per-title rotation.

SCTE-35 & ad markers

Faithful SCTE-35 pass-through and translation into HLS #EXT-X-DATERANGE and DASH EventStream, with de-bouncing for noisy upstream feeds.

VOD transcoding workflows

Accelerated mezzanine ingest, parallel encoding ladders, automated QC, subtitle burn-in, chapter marker extraction, and hash-based dedupe.

How operators use it

National broadcaster

24/7 linear playout to OTT

Six linear channels — including two 4K HDR sports channels — are scheduled, branded, and distributed from a cloud playout that replaced an aging SDI playout suite. Live-to-VOD recording produces catch-up assets automatically, with metadata inherited from the EPG.

Sports streaming service

Concurrent live event encoding

On match days the headend scales to 40+ concurrent live encodes, each with redundant primary/backup encoder pairs. SCTE-35 markers from the outside broadcast truck are preserved end-to-end, so SSAI at the edge always stitches correctly.

SVOD catalog operator

Bulk VOD reprocessing

When the codec strategy moves to include AV1, 140,000 hours of existing catalog are reprocessed in parallel across transient compute, with automated QC gating publication. The DRM and manifest contract stays identical, so no player update is needed.

Technical details

Ingest protocols
  • SRT
  • RTMP / RTMPS
  • RIST
  • Zixi
  • MPEG-TS over UDP
  • SDI via gateway
Codecs
  • H.264 / AVC
  • H.265 / HEVC
  • AV1
  • VP9
  • AAC, HE-AAC, AC-4, Dolby Digital Plus
Packaging
  • HLS (TS & fMP4/CMAF)
  • MPEG-DASH
  • Low-Latency HLS
  • CMAF chunked transfer
  • DVB-DASH
DRM
  • Widevine
  • FairPlay
  • PlayReady
  • CPIX key exchange
  • Per-title rotation
Ad markers
  • SCTE-35 pass-through
  • HLS #EXT-X-DATERANGE
  • DASH EventStream
  • Manifest manipulation for SSAI
Resolutions & HDR
  • Up to 4K / UHD
  • HDR10, HDR10+, Dolby Vision
  • Atmos immersive audio
  • Configurable ABR ladders

Key Takeaways

  • Live encoding over SRT, RTMP, RIST with redundant encoder pairs and sub-2s failover
  • Adaptive bitrate ladders to 4K HDR with HEVC, AV1, H.264 support
  • Cloud playout with scheduling, graphics, logo bug, and live-to-VOD recording
  • Just-in-time HLS, DASH, and LL-HLS packaging with CMAF
  • Widevine, FairPlay, and PlayReady in a single packaging pass
  • Faithful SCTE-35 handling for SSAI and blackout compliance

Frequently Asked Questions

Do you run encoders in the cloud or on metal?
Both. Vucos deploys transcoding on cloud GPU instances, bare-metal appliances, or customer-provided infrastructure, depending on SLA and economics. For 24/7 linear with strict latency SLOs, operators typically pin a primary encoder to dedicated hardware and burst to cloud for event peaks. The same build targets every option.
How is SCTE-35 handled end to end?
Cues from SRT, RTMP, or SDI ingest are preserved in the internal pipeline, translated into HLS #EXT-X-DATERANGE and DASH EventStream on output, and made available to the SSAI stitcher at the edge. De-bouncing logic filters noisy upstream feeds that emit duplicate cues; every cue is observable and auditable in the operations console.
What's the latency floor for live?
Standard HLS deployments sit at 8-20 seconds glass-to-glass. LL-HLS and LL-DASH with CMAF chunked transfer bring that to 3 seconds consistently. For interactive formats the platform supports WebRTC pipelines under 2 seconds, typically with smaller ABR ladders and tighter buffer profiles.
Can we bring our own DRM license service?
Yes. Vucos speaks CPIX, the industry-standard key exchange, so any Widevine, FairPlay, or PlayReady license backend can plug in. Operators who already pay for a DRM service keep it; the packaging pipeline just consumes the keys and writes them into the manifest.
How does cloud playout work?
Linear channels are defined as scheduled timelines of assets, live feeds, promos, and graphics. The playout engine renders the timeline in real time, handles graceful transitions, and emits a continuous stream to the encoder. Schedules are edited through an API and a visual timeline; changes propagate without restarting the channel.
What about subtitles and multiple audio tracks?
Closed captions (608/708), TTML, and WebVTT are carried through ingest, normalized, and published as side-car tracks. Multiple audio languages, descriptive audio, and immersive formats (AC-4, Dolby Atmos) are packaged as alternate renditions and selectable from every supported player SDK.

Related

Ready to learn more?

Talk to an architect about how this fits your deployment.