Essential video technologies, every block.
Engineered into the one pipeline you need.

A decade of software development, engineering and consulting in encoding, playout, ads, DRM and monitoring. We advise on the whole, combine what fits, deliver and support. Proven to work.

HIDE TEXT
GRID

Trusted by

Google logoSky logoCNN logoCanal+ logoDiscovery logoVodafone logoOrange logoInternational Olympic Committee logoEPIC Video Technologies logoPersonal (Telecom Argentina) logoHotel Innovativ logo

Our transcoding, packaging and content protection have run in production since 2014, at global media companies and hundreds of operators around the world. Since 2022 the same platform has powered 200+ FAST channels on 40+ platforms through fastchannels.tv and myfast.ch.

thousandstranscoding channels
millionsVOD assets processed
billionsDRM-protected playback sessions
hundredscustomers, worldwide

About us

Aerial view of the EPFL Innovation Park with Lake Geneva and the Alps

At the heart of the Swiss innovation ecosystem

Noisypeak is based at the EPFL Innovation Park in Lausanne. Being on the EPFL campus gives us direct access to some of the brightest minds: professors doing fundamental research, and students with ideas that don’t fit a template.

We are a compact, highly professional team. We work globally and go after the hard jobs: complex custom projects that others call unsolvable. We like to be the first.

2014founded
globalclients
Serge Tatarchenko, founder of NoisypeakSerge TatarchenkoCEOLinkedIn ↗

Noisypeak Playoutchannels · FAST

Seven minutes. And the channel is yours.

Turn a library or an archive into a 24/7 TV channel on the platforms viewers already use. You don't need a playout suite, an engineering team or a long contract. It's simple to start with and broadcast-grade underneath.

LaunchAbout seven minutes
SchedulingZero-touch, 24/7
AdsSCTE-35, per viewer
200+channels on the platform
40+distribution platforms
36+content providers
7 minto put a channel on air
  • Seven minutes, and the channel is yoursStart from a YouTube library or a broadcast archive.
  • Zero-touch scheduling24/7 AI-assisted scheduling builds the most favourable timeline for your content and keeps it fresh, without a programming desk.
  • Ads that don't break the storyAd markers are placed by understanding the content, so they avoid dialogue and mid-scene cuts.
  • Deep content understanding: MetaThe Meta engine builds one model of your library (people, places, topics, key moments).
Scenario (8 s): light Playout admin. The 3-day Auto Scheduler fills with program titles; a live slot (6hlive3) drops into Friday; a lower-third "Up Next" slides in over the preview player. Cut to Digital Eye: a job passes Extract → Vision → Audio → Cue → Fusion → Reelgen → Key art in 62 s, tease line appears.

Noisypeak Playoutchannels · FAST

Noisypeak Playoutchannels · FAST

  • Your channel on air in 7 minutes
  • Scheduling runs itself, 24/7
  • Broadcast graphics and lower thirds included
  • AI enrichment of every asset
  • Ads that respect the story
  • 200+ channels, 40+ platforms
More on Playout

Media2Flowmedia workflow platform

Transcoding workflows you can see

Build the media transcoding workflow you mean, from single-purpose blocks on a canvas: ingest, analyse, branch, filter, encode, package, deliver. Every node visible, every job traceable, 2 to 500 transcoders.

WorkflowUp to 250 steps, visual
Nodes53 types, 14 families
Scale2–500 transcoders
250steps per workflow
53node types in 14 families
2–500transcoding nodes
111k+tasks run on the Noisypeak Cloud
  • Build it from blocks, see every stepDrag nodes onto a canvas, connect pins and branch on content.
  • Logic inside the workflowanalyze probes the source; decide branches on codec, raster, fps, aspect; eval and $variables make one graph serve a thousand jobs.
  • From mezzanine to mobilex264 / x265, Intel Quick Sync, NetInt ASIC; ProRes, XDCAM, AVC-Intra masters; AAC, AC-3, E-AC-3; MP4, MOV, MXF, TS, HLS, DASH.
  • Drop files, get deliverablesWatch folders on FTP, SMB or local storage: every matching file becomes a job.
Scenario (8 s): slow drift across the workflow editor showing a real 30-node production graph: download → analyze → decide SW/HW → scale → encode → HLS → upload.

Media2Flowmedia workflow platform

Media2Flowmedia workflow platform

  • Workflows you can see
  • 53 node types, drag and connect
  • Up to 250 steps per workflow
  • Drop a file, get deliverables
  • 2 to 500 transcoders
More on Media2Flow

Noisypeak Celllive encoder · transcoder

Live encoding at rack density

Broadcast-grade live encoding on off-the-shelf Intel Arc hardware. One channel comes in and goes out as HLS, DASH, multicast, SRT, SDI and NDI, at up to 230 SD or 32 UHD multibitrate channels per box, and the boxes are managed as a fleet.

CodecsAV1, HEVC, H.264, MPEG-2, VP9
Inputs12G-SDI, HDMI, SRT, NDI, RTMP, UDP
DensityUp to 230 SD · 32 UHD per X HS
230 / 160 / 32SD / HD / UHD ABR channels per X HS
20 GPUsin one 6U X HS chassis
16KHEVC processing · 4K AV1
55+JSON API methods
  • Density that changes the budgetUp to 230 SD, 160 HD or 32 UHD multibitrate channels in one NP Cell X HS.
  • Encode once, publish everywhereOne channel → HLS, DASH, MSS, RTMP, SRT, SPTS/MPTS multicast, SDI and NDI at the same time, each with its own video and audio templates.
  • Every codec that mattersAV1, HEVC, H.264, MPEG-2, VP9 on Intel oneAPI or Nvidia NVENC; up to 4K AV1 and 16K HEVC.
  • Managed as a fleetCell IMC: one API in front of all cells; new channels land on the least-loaded GPU, a failed cell hands over in 30 s, work moves back on recovery.
Scenario (8 s): a single SDI feed enters from the left; the frame splits into a 4×3 wall of renditions (UHD → 312×176) all playing in perfect sync; a counter ticks "230 SD channels · 1 server".

Noisypeak Celllive encoder · transcoder

Noisypeak Celllive encoder · transcoder

  • Up to 230 SD channels per box
  • AV1, HEVC, H.264 and more
  • SDI, HDMI and IP in one unit
  • One input, every output
  • Managed as a fleet
More on Cell

Prism Xserver-side ad insertion

Every viewer, their own ad mix

Server-side ad insertion for live and VOD. It does what AWS MediaTailor does, in your cloud or ours, and adds what MediaTailor lacks: pre-rolls, VOD that starts instantly while ads are fetched on the fly, and a session dashboard a human can read. Fair CPM means you pay only for ads that reached a viewer.

Latency700 ms first segment
VODInstant start, lazy ad fill
RunsNoisypeak Cloud or yours
700 msto first segment
0 sVOD start-up wait (ads filled during playback)
2–50session nodes · 2–100 transcoders
200+FAST channels monetised
  • SSAI you can run yourselfDoes what AWS MediaTailor does, in the Noisypeak Cloud or on your own servers and cloud accounts.
  • VOD starts instantlyLazy mode: the asset plays at once and ad pods are fetched during playback, so you don't wait for every ad to load before the first frame.
  • Pre-rolls includedThe slot before the first frame is sold too, on live joins and on VOD, targeted and counted like any mid-roll.
  • A dashboard humans can readEvery session, pod and fill rate on one timeline.
Scenario (8 s): a stream with grey gaps flows left to right; coloured ad segments drop into the gaps from above, each a different colour per viewer lane; the lanes fan out to phone, TV and laptop, showing the same program with different ads.

Prism Xserver-side ad insertion

Prism Xserver-side ad insertion

  • Every viewer, their own ad mix
  • 700 ms to first segment
  • VOD starts instantly
  • Pre-rolls included
  • Fair CPM: delivered ads only
  • Your cloud or ours
More on Prism X

Noisypeak DRMlicensing · content protection

Licenses for every screen

Multi-DRM licensing and entitlement infrastructure built on our own FairPlay KSM and Widevine license servers, independent of Google's cloud. Licenses for every device (offline included), and CPIX/SPEKE for any packager and player. Google shuts down the Widevine Cloud License Service on 13 April 2027, and we can migrate you before then.

DRM systemsFairPlay, Widevine
IntegrationCPIX / SPEKE, any packager
13 Apr 2027Google shuts Widevine CLS; migrate before then
2DRM systems: FairPlay, Widevine (own license servers)
CPIX · SPEKEany packager, any player
Offlinepersistent licenses supported
  • Licenses for every screenFairPlay KSM and Widevine license server, both Noisypeak's own implementations.
  • A home before Widevine CLS closesGoogle shuts its Cloud License Service on 13 April 2027.
  • Entitlements as well as keysDuration, renewal, rental and playback windows, device and output constraints, key rotation.
  • Offline includedPersistent licenses for download-and-watch are included in the service.
Scenario (8 s): clean picture passes a dashed line and shatters into dots; dots stream to four device circles. Three re-form into the picture; the fourth stays noise with a red "no license". A faint watermark ID fades up in a corner.

Noisypeak DRMlicensing · content protection

Noisypeak DRMlicensing · content protection

  • FairPlay and Widevine licenses
  • Offline playback included
  • Any packager, any player
  • A watermark that names the leaker
  • Links that expire
More on DRM

Noisypeak Packetizerpackager · origin · DVR

Packager, origin and DVR in one node

The multicast-to-OTT stage: a TS, SRT, RTMP or HLS stream comes in and leaves as HLS, DASH, Smooth and multicast at once, without re-encoding, from a node that is also the origin and the DVR. 2,500 streams, 20 Gb/s per node.

InTS multicast, SRT, RTMP, HLS, NDI
Out, in parallelHLS, DASH, CMAF, MSS, SPTS/MPTS
DVRTime-shift, catch-up, start-over
0re-encodes (video passed through)
4streaming formats from one input, in parallel
2,500parallel streams per node
20 Gb/ssustained delivery per node
  • Any input, every format, no re-encodeTS multicast, SRT, RTMP, HLS, NDI or TS files in; HLS (TS / fMP4), DASH, CMAF, Smooth Streaming and SPTS/MPTS out, in parallel, with the video passed through.
  • Origin and DVR on the same nodeTime-shift, catch-up and start-over from the origin buffer, so you don't need a separate recorder or origin server.
  • 2,500 streams, 20 Gb/s per nodeOrigin mode serves viewers directly over 25 Gb/s or 2×10 Gb/s LACP; JWT (RFC 7519) tokens and access lists checked on every request.
  • SCTE-35 through, ads downstreamCUE-IN / CUE-OUT are detected and either passed into the HLS/DASH manifests or spliced.
Scenario (8 s): four differently-toned streams converge on a junction node; they leave re-coloured and re-sized; two of them roll into a spiral (record), pause, and unwind back out (playback) with a "-02:00 time-shift" badge.

Noisypeak Packetizerpackager · origin · DVR

Noisypeak Packetizerpackager · origin · DVR

  • Any input, every format
  • No re-encoding
  • Origin and DVR in one node
  • 2,500 streams per node
  • SCTE-35 passed through
More on Packetizer

Noisypeak Controlstream verification · coming soon

Watches your streams like a player does

Noisypeak Control (the DigitalEye Stream Verifier) plays your HLS and DASH channels the way a player does, checks what it sees against RFC 8216, DASH-IF and good practice, and tells you what is wrong, with the evidence to reproduce it. Severity is based on playback: red means the stream doesn't play, whatever the spec says. Coming soon.

WatchesHLS (TS, fMP4), DASH
Checks100+, with evidence
StatusComing soon
100+checks: transport, manifest, container, content, ads, alignment
4levels by playback impact (red: not playable)
3tiers per channel: playlist · adaptive-high · full
Soonnext release: accounts, trial and slots
  • Watches like a player, reports like an engineerReloads manifests, downloads and decodes segments and extracts frames, then checks every tag, timing, bit rate, GOP, colour flag, loudness and ad marker against the spec.
  • 100+ checks, each with its ruleRFC 8216, DASH-IF, Apple HLS spec or practice: transport, manifest, container, content, ad markers, rendition alignment.
  • Evidence on every alarmThe manifest and its diff, the segment record, the exact ffprobe output.
  • Red means unplayableSeverity by playback impact: yellow players cope, orange really wrong, red not playable or not reachable.
Scenario (8 s): channel list, health strips scrolling; one strip turns orange, the row opens to Health per rendition with the red bars above 125 %, then the Events tab and an evidence card with the ffprobe line.

Noisypeak Controlstream verification · coming soon

Noisypeak Controlstream verification · coming soon

  • Watches like a player
  • 100+ checks, each with evidence
  • Red means unplayable
  • Ad markers verified
  • Coming soon
More on Control
Up next

Product tourContinuing in 5

Noisypeak / Solutions / Noisypeak PlayoutBrochure · PDF

channels · FAST

Noisypeak Playout

Seven minutes, and the channel is yours. You don't need a playout suite, an engineering team or a long contract.

200+channels on the platform
40+distribution platforms
36+content providers
7 minto put a channel on air

Noisypeak Playout is built for people who have never run a television channel. If you have a library on YouTube, on a drive or in an archive, you have everything it needs. Name the channel, give it a look, add content and check it over. The playout, schedule, guide and stream are built as you finish. It takes about seven minutes and there's no sales call: that is myfast.ch, our self-serve front door, from $249 a month.

The same platform runs 200+ channels on 40+ distribution platforms for broadcasters, rights holders and distributors. Archive channels, themed side channels and event channels are licensed or operated for them, with what their engineers expect underneath: SCTE-35 ad markers, multi-bitrate HLS and DASH, EPG, rule-based overlays and live insertion. Simple to start with, broadcast-grade underneath.

metadatalive slotsmarkersadsIngestupload · MRSS · S3 · FTP ·HTTPMeta · NPPEcontent understanding ·summaries · moments · key…Media processingMedia2Flow · 6 ABRrenditions · HLS & DASHAsset librarypriority by age · yours tooverrideLive sourcesOBS · any encoder · yourbrowserAuto Scheduler3-day timeline · zerotouchOverlays & adslower thirds · badges ·SCTE-35 breaksPrism X SSAIa different ad mix perviewerDistributionSamsung TV Plus · LocalNow· STB · mobile · web…
From your library to the viewer. One platform from content to consumer: ingest, understanding, scheduling, graphics and ads, delivery.
Always already playing

Viewers land mid-programme, so sessions run for hours rather than minutes.

Every hour carries ads

Ad breaks run around the clock, so the archive earns overnight and on weekday mornings.

Shelf space on the TV

A slot in the smart-TV guide beside the broadcasters.

Old content becomes new

An old film in an evening slot is programming; in a list, it is a search result nobody runs.

From a library to a channel, in five steps

You do not need to know how a broadcast playout works. First you name the channel and pick a genre. Then you give it a look: fonts, palette and on-screen graphics. You add content, either a cleared library or your own videos, and check it all on one screen, where everything is still editable. Playout, schedule, guide and stream are built as you finish.

From there each channel has one dashboard: what is on air now, what comes next, live and VOD slots for the day, the last assets that arrived. Sources, assets, graphics and ads are one click away. One person runs it.

  • Name it
  • Give it a look
  • Add content
  • Check it over
  • Plan and account
Playout admin home: every channel with live preview, its sources, assets and hours of content.
Playout admin home: every channel with live preview, its sources, assets and hours of content.

Scheduling that runs itself

The Auto Scheduler fills a rolling three-day timeline from your content, 24/7, with zero touch. Every asset carries a priority from 1 to 10. By default the newest content ranks highest, so the channel leads with what just arrived and still rotates the back catalogue. You can regenerate at any time (after a big upload, say, or before a weekend) and the timeline rewrites itself.

Want a program at a fixed time? Place it; the scheduler flows around it. Programs are timed to the second and the preview shows what is on air with the time remaining.

Auto Scheduler: three-day timeline with fixed live slots and auto-filled programs, priority by asset age.
Auto Scheduler: three-day timeline with fixed live slots and auto-filled programs, priority by asset age.

Content the system actually understands: Meta

Behind enrichment sits Meta, the Noisypeak content-understanding engine. It keeps one model of your whole library, covering every title, scene, face, keyword, place, organisation and topic in six languages, and scheduling, ad targeting and promotion all read from it. NPPE runs every new asset through its nine stages (Extract, Vision, Audio, Cue, Fusion, Reelgen, Refine, Localize, Keyart). It writes back a summary and tease line, keywords, the most interesting moments, three short promo reels, key art and metadata, 100% automatically, in about a minute per asset.

The same understanding drives the rest of the channel end to end: who appears and what is discussed decides where an ad break can go and which ads fit; topics and people cluster the library so the scheduler can build an evening that hangs together; the poster and the short that promote a program come from the frames Meta ranked highest. Subtitles and full language translation are coming soon.

  • Meta: people, places, organisations, topics and keywords across the whole library
  • Summaries, key moments, key art and three promo shorts per asset
  • Metadata in six languages; subtitles and translation coming soon
  • One understanding feeds scheduling, ad targeting and promotion
Meta keyword space for one channel: 27 topic spheres and 3,724 keywords (people, places and organisations) clustered across 866 assets.
Meta keyword space for one channel: 27 topic spheres and 3,724 keywords (people, places and organisations) clustered across 866 assets.

Ads placed where they belong

Ad breaks are placed by understanding the content rather than by a stopwatch. The markers avoid dialogue and mid-scene cuts, so the break lands between thoughts and the viewer stays. Breaks are signalled with SCTE-35 in the output. Prism X, the Noisypeak server-side ad insertion, fills them per viewer against your SSP/DSP, live and VOD, so the same channel carries a different ad mix on every platform and device. Client-side insertion is supported where a platform requires it.

  • Content-aware ad markers, SCTE-35 signalled
  • Prism X SSAI: a different ad mix per viewer
  • Rule-based break patterns per channel

Broadcast-level graphics, by rule

Program announcements, Up Next, lower thirds, advisory and age badges, sponsor reminders and back-from-break bugs are defined once as rules. A rule has a trigger (program start, before or after an ad break, before program end), a repeat, an active period and a template. After that the overlays run themselves for the whole campaign window, and nobody has to sit at a graphics desk.

Overlay rules: trigger, repeat, active period, delay, template length and template per rule.
Overlay rules: trigger, repeat, active period, delay, template length and template per rule.

Live, from a studio or a browser

Want to talk to your audience or host a guest? Register a live source and schedule a live slot at an exact time. VOD programs fill around it and ad breaks run across both. Stream from OBS Studio or any encoder. For the simplest start you can broadcast straight from your browser with no extra software. Live and VOD are interleaved in one channel with one output.

  • Live slots to the minute, fixed in the timeline
  • OBS, any RTMP/SRT encoder, or the browser
  • One continuous output with ads across live and VOD

Any source in, every platform out

Playout runs on Media2Flow, the Noisypeak workflow transcoding platform. Whatever arrives, in any codec, container or resolution, is processed into six multi-bitrate renditions for HLS and DASH, with audio levelling, multiple audio languages and subtitle tracks.

The channel and its always-current EPG (your metadata or the system's) are then delivered to Samsung TV Plus, LocalNow, set-top boxes, mobile, web and smart TVs, with per-platform variants from one schedule.

  • Upload, MRSS, S3, FTP, HTTP, Aspera in
  • 6 ABR renditions, HLS and DASH, levelled audio
  • EPG generated and kept up to date on every platform

Features

Seven minutes, and the channel is yours

Start from a YouTube library or a broadcast archive. Name the channel, give it a look, add content, and it is on air. You don't need a playout suite, an engineering team or a long contract.

Zero-touch scheduling

24/7 AI-assisted scheduling builds the most favourable timeline for your content and keeps it fresh, without a programming desk.

Ads that don't break the story

Ad markers are placed by understanding the content, so they avoid dialogue and mid-scene cuts. Each viewer is monetised with Prism X.

Deep content understanding: Meta

The Meta engine builds one model of your library (people, places, topics, key moments). Scheduling, ad targeting and promotion all read from it, 100% automatically.

Broadcast-level graphics

Program announcements, lower thirds and advisory badges are included, so the channel looks like real TV.

Live when you want it

Talk to your audience or host guests. Stream from OBS Studio or any encoder, or straight from your browser without installing anything.

EPG always up to date

Programme guide generated with full metadata, yours or the system's, published to every platform.

Your content, in every language

Metadata in six languages today, so your content travels. Subtitles and translation are coming soon.

Any source in, it just works

Media2Flow processes any input into 6 multi-bitrate HLS and DASH renditions; audio levelling, multi-language, multi-subtitles.

Delivered where viewers are, proven at scale

Samsung TV Plus, LocalNow, Roku, Fire TV, LG, set-top boxes, mobile and web: 200+ channels on 40+ distribution platforms.

Specifications

Ingest
SourcesMRSS · S3 · Aspera · HTTP · FTP · manual upload
PreparationMedia transcoding and metadata processing (Media2Flow) · visual and AI enrichment (Digital Eye)
Scheduling
Auto SchedulerRolling 3-day timeline · 1-day or 3-day view · regenerate on demand
Priority1–10 per asset; default buckets by age: 0–4 h P10 · 4–24 h P9 · 1–10 d P8 · 10–30 d P5 · older P4
Manual placementManual upload at a fixed time; live slots at exact times
Graphics and ads
Overlay triggersAt program start · before ad break · after ad break · before program end
Overlay optionsRepeat every N programs or ad breaks · active period · start-after seconds or formula · template length · Overlay or Lower Third template
Ad breaksRule-based, e.g. 2 min every 8 min · SCTE-35 markers
Ad insertionPrism X server-side (SSP/DSP e.g. SpringServe, OpenX) · client-side where required
NPPE · Digital Eye
PipelineExtract → Vision → Audio → Cue → Fusion → Reelgen → Refine → Localize → Keyart
Per assetTease line · keywords and ad-targeting markers · 3 reels · key art · 6 languages
Production figures5,184 jobs · 62.8 s per job average
Distribution
OutputHLS channels, variants per platform
PlatformsSamsung TV Plus · LocalNow · set-top boxes · mobile · PC · smart TV
OTT suiteVOD CMS · subscriptions and ads · analytics · DRM and authentication · geo-blocking · iOS, Android, web, Roku, smart TV, Apple TV, Android TV, Fire TV

Where it is used

Creators with a back catalogue

A second revenue stream from existing videos: the catalogue becomes a 24/7 channel in the smart-TV guide.

Broadcasters: archive as a side channel

Archive and themed content next to the main brand, with SCTE-35, EPG and broadcast graphics the engineers expect.

Rights holders and studios

Earn in the gaps between licensing deals; every hour carries ads.

Sports and event organisers

Year-round presence with live blocks at fixed times and VOD around them, instead of spikes on event days.

Brands, publishers, archives and communities

TV reach with measurable ad economics; a permanent public home for a collection.

Talk to us about Noisypeak Playout

We handle evaluation in the Noisypeak cloud, deployment on premises or in a public cloud, integration and support. One team covers the whole pipeline.

Works with

Noisypeak / Solutions / Media2FlowBrochure · PDF

media workflow platform

Media2Flow

Build the media transcoding workflow you mean. Every node visible, every job traceable, any scale.

250steps per workflow
53node types in 14 families
2–500transcoding nodes
111k+tasks run on the Noisypeak Cloud

Media2Flow is a visual media workflow platform for people who want to know exactly what happens to their files. A workflow is a graph of single-purpose nodes (download, analyse, map, filter, encode, package, upload), drawn on a canvas and connected pin to pin. A job is one input run through one workflow. What you drew is what runs, and every job shows the timing of every node.

Jobs arrive by hand, from watch folders on FTP, SMB or local storage, or by URL from S3 and HTTPS. The same platform encodes live channels against templates and exposes them per audience through distributions. It runs in the Noisypeak Cloud, on AWS, Google Cloud, Azure, Kubernetes or Docker on your own servers, and scales from two transcoders to five hundred.

metadatabranchSourceswatch folder FTP/SMB/local· S3 · HTTPS · manual jobWorkflowdownload → map → filters →encode → package → uploadLogicanalyze · decide · mdecide· eval · setvarEncodersx264 · x265 · qsv264 ·ni264 · ProRes · XDCAM…PackagingMP4 · MOV · MXF · TS · HLSv3/v5 · DASHLive channelsUDP · RTMP · SRT · HTTP ·HLS pull → templatesUploadS3 · HTTPS · storage URL ·notify email/webhookDistributionsPoP · whitelist ·third-party HLSDashboardper-node timing ·success/issues/failed…
One job through a Media2Flow workflow. Sources go in, run through a visible graph of nodes and come out as deliverables, with a dashboard that times every step.

Build it from blocks, see every step

Every workflow starts with an input and ends with an output. Between them you drop nodes from the palette and connect their pins. The palette has Input/Output, Logic, Audio Filter, Video Filter, Audio Encode, Video Encode, Package, Misc and reusable Fragments. Node options can reference workflow variables such as $In and $Out, so one graph serves many jobs. Fragments are sub-graphs saved once and dropped into a parent workflow as a single tile.

The editor shows the live graph of a production workflow: download → analyze → decide between software and hardware paths → scale, frame rate, letterbox and aspect-ratio filters → H.264 encode → HLS and MP4 packaging → upload, with Python nodes for custom logic. Workflows are grouped by folder, imported, exported and versioned by name.

Workflow editor: playout_profile_forced_aspect_ratio_v5_sw, a 30-node production graph with a software/hardware decision branch.
Workflow editor: playout_profile_forced_aspect_ratio_v5_sw, a 30-node production graph with a software/hardware decision branch.

Logic inside the workflow

Workflows adapt to the source. The analyze node probes codec, raster, frame rate, duration and channels, and decide / mdecide branch on what it finds. Interlaced sources go through deinterlace, odd aspect ratios through letterbox, and anything above a size threshold goes to the hardware encoder. eval runs expressions and setvar writes $variables, so one graph serves a thousand different inputs and still produces the same deliverable.

When a chain needs something the palette does not have, a Python node runs your code inside the workflow with the same inputs and outputs as any other block. You always see what the workflow does, and nothing is decided behind your back.

  • analyze → decide / mdecide: branch on codec, raster, fps, aspect, size
  • eval expressions and $variables: one graph, many jobs
  • Python nodes for custom logic, inline
  • concat up to 16 sources; copy for pass-through without re-encode

The node catalogue: 53 nodes in 14 families

Each node does one thing; chains do the rest. Stream mapping (map/video, map/audio, map/text, map/timecode) splits a package into tracks right after the source. Video filters cover scale, crop, dar, deinterlace, fieldorder, format, fps, hwupload, letterbox and overlay; audio filters aformat, aresample, join and stereo.

Video encoders: x264 and x265 in software, qsv264 on Intel Quick Sync and ni264 on NetInt hardware, plus AVC-Intra, DV, ProRes and XDCAM MXF OP1a mezzanines. Audio: AAC, Dolby Digital AC-3, Dolby Digital Plus E-AC-3 and PCM. Containers MP4, MOV, MXF and TS; streaming packagers hls3 (TS segments), hls5 (fMP4) and dash, with optional subtitle tracks.

  • Logic: analyze probes codec, raster, frame rate, duration, channels; decide / mdecide branch; eval runs Jinja-style expressions; setvar writes $Variables; delay holds a package
  • Stream processing: concat stitches up to 16 sources into one timeline; copy passes through with no re-encode
  • Subtitles: ccinject adds caption tracks without re-encoding; whisper transcribes speech to captions
  • File operations: move and delete on storage URLs; notify sends e-mail or webhooks

Jobs, watch folders and logs

Watch folders poll an FTP, SMB or local folder on a schedule; every file matching a name mask becomes a job through the chosen workflow. One-off jobs are submitted by hand with a priority and workflow variables. The Jobs list finds any task by ID, title, workflow, state or date and shows outputs and per-node timing; Job Logs is a chronological stream of every per-node event, filterable by workflow, watch folder, phase and time range.

Dashboard on the Noisypeak Cloud: file-transcoding throughput by date, last workflows, last tasks and watch folders.
Dashboard on the Noisypeak Cloud: file-transcoding throughput by date, last workflows, last tasks and watch folders.

Dashboard and reporting

The dashboard is the control centre: total tasks with success, issues and failed counts, a monthly throughput chart with date range, an execution-outcome pie, job count by workflow, a hot-nodes treemap that shows which node types consume the processing time, and a filter by run-time option values such as codec, container or HEVC preset. Every chart exports as SVG, PNG or CSV; Prometheus and Grafana carry the same metrics to your monitoring.

  • Per-node execution time and call count in a treemap
  • File-size-versus-time scatter plot across the account
  • Status dots on last workflows, tasks and watch folders
  • Prometheus and Grafana with the same metrics

Live channels, templates and distributions

A live channel binds an input stream (UDP, RTMP, SRT, HTTP/HTTPS or HLS pull) to an encoder template and an availability zone, with DVR depth and a passthrough toggle per channel. Templates hold the audio block and one or more video streams for ABR. One template can serve many channels, and a change propagates on the next restart.

Distributions expose a bundle of origin and live channels through a chosen point-of-presence, optionally restricted by a network whitelist. Each distribution is one audience, one PoP and one set of channels. Third-party HLS feeds are registered by URL and forwarded through the edge without re-encoding, side by side with platform-encoded channels.

  • Inputs: UDP · RTMP · SRT · HTTP/HTTPS · HLS pull
  • Per-channel DVR depth, passthrough and availability zone
  • Encoder templates with multi-stream ABR ladders
  • PoP selection and network whitelist per distribution
  • Third-party HLS channels forwarded without re-encoding

Features

Build it from blocks, see every step

Drag nodes onto a canvas, connect pins and branch on content. The graph is the pipeline, so nothing is hidden or guessed.

Logic inside the workflow

analyze probes the source; decide branches on codec, raster, fps, aspect; eval and $variables make one graph serve a thousand jobs. Python nodes when you need more.

From mezzanine to mobile

x264 / x265, Intel Quick Sync, NetInt ASIC; ProRes, XDCAM, AVC-Intra masters; AAC, AC-3, E-AC-3; MP4, MOV, MXF, TS, HLS, DASH. 53 nodes, 14 families.

Drop files, get deliverables

Watch folders on FTP, SMB or local storage: every matching file becomes a job. S3, HTTPS and manual submission too.

Reuse, version, share

Fragments: a sub-graph saved once, dropped as one tile. Workflows grouped in folders, imported, exported, versioned by name.

Captions without re-encoding

Whisper speech-to-text; ccinject adds caption tracks to existing files in seconds.

Scale when the queue says so

2–500 transcoding nodes, 1–100 processing nodes; software or hardware path chosen per job by the workflow itself.

Live, too

UDP, RTMP, SRT, HTTP, HLS-pull channels on encoder templates; distributions per audience with PoP and whitelist; third-party HLS forwarded as-is.

Every job explains itself

Per-node timing, hot-node treemap, job logs by phase; SVG / PNG / CSV export; Prometheus and Grafana built in.

Runs where you run

Noisypeak Cloud, AWS, Google Cloud, Azure, Kubernetes or Docker on-premise. Delivered as containers with Ansible playbooks.

Specifications

Platform
Host OSUbuntu · Amazon Linux
EnvironmentsNoisypeak Cloud · AWS · Google Cloud · MS Azure · Kubernetes · Docker
DeliveryDockerized software · Ansible playbook setup and update
Media processing nodes1 to 100, auto-scaling
Transcoding nodes2 to 500
Workflow complexityUp to 250 processing steps per workflow
Inputs
FilesWatch folders on FTP, SMB or local storage · signed S3 · HTTPS · manual submission with priority and variables
LiveUDP · RTMP · SRT · HTTP/HTTPS · HLS pull
FormatsAll major video and audio codecs, live streams and file-based content
Processing nodes
Stream mappingmap/video · map/audio · map/text · map/timecode
Video filtersscale · crop · dar · deinterlace · fieldorder · format · fps · hwupload · letterbox · overlay
Audio filtersaformat · aresample · join · stereo
Video encodersx264 · x265 · qsv264 (Intel QSV) · ni264 (NetInt) · avcintra · dv · prores · xdcam
Audio encodersaac · ac3 · eac3 · pcm
Logicanalyze · decide · mdecide · eval · setvar · delay
Stream processingconcat (up to 16 sources) · copy
Subtitlesccinject · whisper (OpenAI Whisper)
Files and notificationsdownload · upload · move · delete · notify (e-mail, webhook)
Outputs
ContainersMP4 · MOV · MXF · TS · WebM · AVI
StreamingHLS v3 (TS) · HLS v5 (fMP4) · MPEG-DASH, optional subtitle tracks
DestinationsAny storage URL: S3, HTTPS and other supported schemes
Integration and monitoring
APIsRESTful API · GraphQL · webhook notifications
MonitoringPrometheus · Grafana
ReportsEvery dashboard chart exports as SVG, PNG or CSV

Where it is used

VOD library processing

Watch folders and workflows turn every delivered file into mezzanines, MP4 ladders, HLS and DASH packages with captions. This is the asset library behind Noisypeak Playout.

Broadcast mezzanines

AVC-Intra and XDCAM MXF OP1a, ProRes and DV masters, MPEG-TS pre-encodes and 5.1 AC-3 deliverables from one graph.

Conditional pipelines

analyze and decide route interlaced, odd-aspect or oversized sources to the right filter chain and to software or hardware encoders, by your rules and visible in the graph.

Live channels at the edge

Contribution feeds encoded on templates and exposed per audience through distributions and points of presence, next to third-party HLS channels.

Talk to us about Media2Flow

We handle evaluation in the Noisypeak cloud, deployment on premises or in a public cloud, integration and support. One team covers the whole pipeline.

Works with

Noisypeak / Solutions / Noisypeak CellBrochure · PDF

live encoder · transcoder

Noisypeak Cell

Live encoding at rack density. One input to every output, in AV1, HEVC and H.264 on off-the-shelf Intel Arc.

230 / 160 / 32SD / HD / UHD ABR channels per X HS
20 GPUsin one 6U X HS chassis
16KHEVC processing · 4K AV1
55+JSON API methods

Noisypeak Cell is our X series of live encoders and transcoders (NP Cell XS, X, X2 and X HS). They run on off-the-shelf servers with Intel Arc GPUs instead of proprietary silicon, and that density changes the budget: more channels per rack unit, a lower cost per channel, and hardware you can buy anywhere. Cell captures SDI, HDMI and IP sources and produces multibitrate output for OTT, IPTV and cable, on premise or as a cloud service.

Every model runs UEN2, the same uniform encoding engine. One channel feeds HLS, DASH, SPTS/MPTS, SRT, RTMP, SDI and NDI in parallel, with SCTE-35, closed captions and DRM carried through, up to 4K AV1 and 16K HEVC. Cells are managed as a fleet: Cell IMC puts one API in front of all of them, places channels on the least-loaded GPU and fails over in seconds. Monitoring is Zabbix, Prometheus and SNMP, as a head-end expects.

Input12G/HD-SDI · HDMI ·UDP/RTP · SRT · RTMP · HL…UEN2 decodeMPEG-TS demux · dynamiccodec and protocol…Filtersscaling · cropping ·deinterlacing…GPU encodeAV1 · HEVC · H.264 · MPEG2· VP9 · Intel oneAPI /…PackagingHLS v3–v7 · DASH · MSS ·SPTS/MPTS · SCTE-35 · DRMOTTHLS · DASH · MSS · originmodeIP contributionSPTS/MPTS multicast · SRT· RTMPBasebandSDI playout · NDI playoutPublishingCDN · WebDAV · FTP · SMB ·YouTube · Facebook
How Noisypeak Cell turns one input into every output. Single input to multi-stream output: every rendition and every format comes from the same UEN2 pipeline.

UEN2: one engine from capture to packaging

UEN2, the uniform encoding engine, is the software core of every Cell model. It decodes any supported input, applies video post-processing and encodes AV1, HEVC/H.265, AVC/H.264, MPEG2 and VP9 with Intel oneAPI or Nvidia NVENC acceleration. Framerate is fixed to the source; linear time-code is generated; a look-ahead buffer is available.

Encoding parameters are exposed down to the bitstream: Baseline, Main and High profiles, CABAC/CAVLC, HRD buffer length and initial delay, frame-accurate closed GOP length, B-frame and reference frame counts, IDR interval and slice count. H.264 is accepted as AVCC or Annex B at the input and emitted as Annex B for multicast and HLS or AVCC for RTMP.

  • Video post-processing: scaling, cropping, deinterlacing, letterboxing
  • Logotype and text string overlays
  • Picture in picture, up to 4 streams
  • Static image preview generation
  • Video and audio passthrough per output
  • Different audio templates for each output of a single channel

Inputs: baseband and IP in the same box

Capture up to 12G-SDI and 4K HDMI through Magewell or Blackmagic add-on modules, or take IP sources directly: RTP/UDP SPTS and MPTS, HLS and HTTP progressive, RTSP, RTMP, SRT, NDI, SHOUTcast and UVC 1.5 webcams. SDP/Onvif covers IP security cameras. TS files run as file2live or file2vod. Input codec and protocol are adjusted dynamically; audio is accepted as AAC/AAC-LATM, MP2/MP3, AC3, EAC3 and Opus.

Outputs, captions and protection

Each channel publishes in several formats at once: HLS up to v7 with multi-language support, MPEG-DASH live and VOD with timelined manifests, Microsoft Smooth Streaming, RTMP with Akamai support, UDP unicast or multicast SPTS and MPTS, SRT, SDI and NDI playout, and TS or MP4 files to WebDAV, Windows share (Samba) or FTP. An HLS secondary destination point and WebDAV authorisation cover publishing redundancy.

SCTE-35 CUE-In/CUE-Out messages are detected, passed through or spliced. Closed captions are carried as CEA-708, EIA-608 and WebVTT; DVB subtitles can be burnt in; DVB PIDs pass through. DRM covers Apple FairPlay, Widevine via CENC and AES-128 static key.

Origin mode

In origin mode a Cell serves four streaming types in parallel from the same channel: HLS with separate audio and video TS renditions, HLS3 with muxed TS, HLS7 with separate fMP4 renditions, and MPEG-DASH with separate fMP4 renditions. Links can be tokenised with JWT (RFC 7519). In-memory start-over, content protection and access lists are configured per channel.

  • Up to 2500 parallel streams over a 25 Gb/s interface
  • Up to 20 Gb/s sustained delivery over 25 Gb/s or 2×10 Gb/s LACP

Fleet API: Cell IMC

Cell IMC serves one HTTP API in front of a fleet of cells, at /api/10/. Clients work with cluster-wide channel, output, template and overlay ids; a cell's own numbering is never exposed. Channel, output and overlay calls keep the node API's grammar, so no key is renamed or removed. Configuration writes are stored in the IMC first and then pushed to the cell, so the intent survives a cell that is down; writes to an offline cell are parked and applied when it returns.

New channels are placed on the cell with the lowest score, computed from free GPU load, average GPU load and channel count over the last 30 monitoring samples. A cell confirmed offline is failed over after failover_after_seconds (default 30 s); auto_recover moves work back when it returns. Per-cell channel and output ceilings are set manually or measured by a built-in capacity test. The IMC applies to Cell IMC 1.2.51 and later.

  • Outputs: HLS, DASH, RTMP or UDP, each with its own video and audio template
  • Overlays: image, text or picture-in-picture, with position and size
  • Primary and backup source per channel, MPEG-TS service and PID selection
  • Failover priority 1–10 per channel and per output
  • One call starts or stops every channel in the cluster
  • Cluster-wide and per-cell backup and restore
  • Per-cell health: reachability, version, uptime, licence verdict

Management and high availability

Up to 50 encoders are managed in one web interface with real-time monitoring, statistics and video templates. Zabbix, Prometheus/Grafana and SNMP integrations and more than 55 JSON API methods expose the same data to external systems. Clustering services provide n+1, 1+1 and n+m redundancy, with input source redundancy and publishing server redundancy in the standard image; see Noisypeak Control for the NP-RFS failover software.

Features

Density that changes the budget

Up to 230 SD, 160 HD or 32 UHD multibitrate channels in one NP Cell X HS. Off-the-shelf Intel Arc, not proprietary silicon: more channels per rack unit, less per channel.

Encode once, publish everywhere

One channel → HLS, DASH, MSS, RTMP, SRT, SPTS/MPTS multicast, SDI and NDI at the same time, each with its own video and audio templates.

Every codec that matters

AV1, HEVC, H.264, MPEG-2, VP9 on Intel oneAPI or Nvidia NVENC; up to 4K AV1 and 16K HEVC.

Managed as a fleet

Cell IMC: one API in front of all cells; new channels land on the least-loaded GPU, a failed cell hands over in 30 s, work moves back on recovery. Up to 50 encoders in one console.

Baseband and IP in the same unit

12G-SDI and 4K HDMI via Magewell / Blackmagic; UDP/RTP, SRT, RTMP, HLS, RTSP, NDI, UVC, Onvif over IP. TS files as file2live / file2vod.

Broadcast signalling carried through

SCTE-35 detect / pass / splice; CEA-708, EIA-608, WebVTT captions; DVB subtitle burn-in or PID pass-through.

Protected at the encoder

FairPlay, Widevine (CENC) and AES-128 on the same box.

Bitstream-level control

Profiles, CABAC/CAVLC, HRD, closed GOP, B/ref frames, IDR interval, slice count: tuned per output, not per vendor preset.

Origin built in

HLS v3/v7 and DASH from the same channel; JWT-tokenised links; 2,500 parallel streams, 20 Gb/s per node.

Monitored your way

Zabbix, Prometheus/Grafana, SNMP, 55+ JSON API methods; n+1 / 1+1 / n+m redundancy with Noisypeak Control.

Specifications

Inputs
Baseband4K HDMI · 12G-SDI · HD-SDI · HDMI through Magewell and Blackmagic add-on modules · UVC 1.5 webcams
IPRTP/UDP SPTS and MPTS · HLS · HTTP progressive · HTTP TS · RTSP · RTMP · SRT · NDI · SHOUTcast · SDP/Onvif for IP security cameras
FilesTS files (file2live, file2vod)
Audio inAAC/AAC LATM · MP2/MP3 · AC3 · EAC3 · Opus
BehaviourDynamic input adjustment for codec and protocol · h.264 AVCC or Annex B at the input
Outputs
OTTHLS up to v7 with multi-language support · MPEG-DASH live and VOD, timelined manifest · Microsoft Smooth Streaming
TransportUDP unicast/multicast SPTS and MPTS · SRT · RTMP with Akamai support · SHOUTcast
BasebandSDI playout · NDI playout
Files and publishingTS and MP4 files · WebDAV, Windows share (Samba), FTP · direct to CDNs · YouTube · Facebook · multi-format simultaneous publishing
SignallingSCTE-35 detection, pass-through and splicing (CUE-In/CUE-Out) · DVB PID pass-through · HLS/SPTS stream selection
CaptionsCEA-708 · EIA-608 · WebVTT · DVB burn-in subtitles
DRMApple FairPlay · Widevine (CENC) · AES-128 static key
Video encoding
CodecsAV1 · HEVC/H.265 · AVC/H.264 · MPEG2 · VP9
ResolutionUp to 4K AV1 · up to 16K HEVC video processing
AccelerationIntel oneAPI · Nvidia NVENC
ProfilesBaseline, Main and High · CABAC/CAVLC
GOP controlFrame-accurate closed GOP length · B-frames count · reference frames count · IDR interval · slice count
HRDNAL HRD conformance: buffer length, initial delay · look-ahead buffer
Post-processingScaling · cropping · deinterlacing · letterboxing
GraphicsLogotype and text string overlays · picture in picture up to 4 streams · static image preview generation
TimingFramerate fixed to source · linear time-code generation
Audio encoding
CodecsAAC-LC up to 512 kb/s · HE-AAC up to 128 kb/s · multi-audio MP2/MP3 · audio passthrough
ProcessingGain control · audio levelling · advanced sample rate transform
ModesAudio-only transcoding (radio) · SHOUTcast output · different audio templates per output of a single channel
Origin mode
Formats in parallelHLS (separate TS renditions) · HLS3 (muxed TS) · HLS7 (separate fMP4) · MPEG-DASH (separate fMP4)
FeaturesJWT RFC 7519 link tokenisation · in-memory start-over · content protection · access lists
Target performanceUp to 2500 parallel streams over 25 Gb/s · up to 20 Gb/s sustained over 25 Gb/s or 2×10 Gb/s LACP
Management
Web UIUp to 50 encoders in one uniform web interface · real-time monitoring and statistics · video templates
IntegrationsZabbix · Prometheus/Grafana · SNMP · more than 55 JSON API methods
Fleet APICell IMC at /api/10/ · cluster-wide ids · GPU-aware placement · failover_after_seconds (default 30) · auto_recover · capacity ceilings 1–1000 per cell
High availabilityn+1 · n+m · 1+1 · input source redundancy · publishing server redundancy
Models
NP Cell XSMainstream · single PSU · up to 2 GPUs · 20 SD / 12 HD / 4 UHD multibitrate channels
NP Cell X / X2Advanced · single or dual PSU · up to 3 GPUs · 35 SD / 24 HD / 6 UHD multibitrate channels
NP Cell X HSHyperscale transcoder · up to 4 PSUs · up to 20 GPUs · 230 SD / 160 HD / 32 UHD multibitrate channels
PlatformIntel 14th Gen / Intel Core Ultra 200 CPU · Intel Arc A-Series / B-Series GPU (e.g. Intel Arc A40)
DeliverySoftware licence · subscription licence · cloud service under the NP X Connected brand
Typical ABR ladder: 4K/UHD (AV1, HEVC)
18000 kb/s · 3840×2160
24500 kb/s · 1920×1080
32500 kb/s · 1280×720
41600 kb/s · 1024×576
51100 kb/s · 720×404
6700 kb/s · 640×360
Typical ABR ladder: HD
16000 kb/s · 1920×1080
24500 kb/s · 1280×720
32500 kb/s · 1024×576
41600 kb/s · 720×404
51100 kb/s · 640×360
6700 kb/s · 480×270
Typical ABR ladder: SD
11600 kb/s · 720×404
21100 kb/s · 640×360
3700 kb/s · 480×270
4400 kb/s · 312×176

Models and licences

NPXS

Noisypeak Cell XS 1U · 1×CPU/iGPU · 2×GbE · 16 GB RAM · Windows or Ubuntu · includes NPXS-SW

NPX

Noisypeak Cell X 1U · 1×CPU/iGPU · 2×10GbE · 1×Intel Arc GPU · 32 GB RAM · Windows or Ubuntu · includes NPXS-SW and NPX-SW-A

NPX2

Noisypeak Cell X2 2U · 1×CPU/iGPU · 2×10GbE · 2×Intel Arc GPU · 64 GB RAM · 2×250 GB SSD · redundant PSU · Windows or Ubuntu · includes NPXS-SW and two NPX-SW-A licences

NPX HS

Noisypeak Cell X HS · Supermicro MicroBlade, 20 blades × 1 Intel Arc GPU in 6U · up to 230 SD / 160 HD / 32 UHD ABR channels · for hyperscale head-ends

NPXS-SW

Noisypeak Cell software licence · MPEG2/H.264/HEVC/AV1 · HLS/DASH packetising · WebDAV · DRM · SCTE-35 · for one Intel integrated GPU (e.g. UHD770, Xe2)

NPX-SW-A

Noisypeak Cell software licence enabling transcoding on one Intel Arc PCIe card (e.g. Intel Arc A40 Pro)

Where it is used

Live TV to multiscreen OTT

Encode a channel once and publish HLS, DASH and MSS ladders with DRM and SCTE-35 to CDNs or in origin mode.

Live TV to multicast IPTV and cable TV

SPTS and MPTS multicast output with DVB PID pass-through and burnt-in subtitles for IPTV head-ends and cable platforms.

External camera broadcasting

Capture SDI, HDMI, UVC or Onvif cameras and stream to RTMP, SRT, YouTube or Facebook from one unit.

Cloud and file encoding

Run the same engine as a cloud service, or process TS files as file2live and file2vod with TS and MP4 file output.

Broadcast, telco, medical, education, enterprise, sports venues

Content distribution, head-end solutions, live surgery streaming, classroom recording, surveillance monitoring, arena IPTV and digital signage.

Talk to us about Noisypeak Cell

We handle evaluation in the Noisypeak cloud, deployment on premises or in a public cloud, integration and support. One team covers the whole pipeline.

Works with

Noisypeak / Solutions / Prism XBrochure · PDF

server-side ad insertion

Prism X

Server-side ad insertion you can actually run: pre-rolls, VOD that starts instantly, a dashboard humans can read.

700 msto first segment
0 sVOD start-up wait (ads filled during playback)
2–50session nodes · 2–100 transcoders
200+FAST channels monetised

Prism X stitches VAST ads into HLS and DASH streams on the server, per viewer, live and on demand. If you know AWS MediaTailor, you know the job: markers go in, personalised manifests come out, ad blockers can’t remove the ads and the player doesn’t stall at ad breaks. Prism X does it in the Noisypeak Cloud or on your own infrastructure (bare metal, VMware, Hyper-V, AWS, Google Cloud, Azure) and bills a fair CPM: only ads that actually reached a viewer count.

It does three things the big-cloud alternative doesn't. It runs pre-rolls, so the first impression is sold too. It has a VOD lazy mode: the asset starts immediately and ad pods are requested while the viewer watches, instead of pre-fetching every ad before the first frame. And it has a session dashboard a human can read, with every viewer, pod and fill rate on one timeline. Prism X is the monetisation stage behind 200+ FAST channels on fastchannels.tv and myfast.ch.

ad markersVAST responsepod fill-inads conformed to sourcestitched manifestsession logsTV channel(s)HLS/DASH with ad markers ·SCTE-35 · CUE-OUT/IN…Prism X session nodesper-viewer session ·manifest stitching · 2–50…Primary SSP/DSPVAST / VPAID · e.g.SpringServe, OpenXSecondary VASTbackup pod source · e.g.AdbutlerTranscoding nodesUEN2 · CPU / QSV / NVEnc /Netint · ad cache 0–500 TBViewersHLS/DASH with DRM ·targeted ads per sessionLogs and metricsClickHouse · Prometheus ·Grafana
How Prism X stitches ads into a stream. Ads are requested per session, transcoded once to match the source and stitched into each viewer's manifest.

How stitching works

Prism X sits between the origin and the viewer. The source channel arrives as HLS or DASH with ad markers (EXT-X-CUE-OUT/EXT-X-CUE-IN, EXT-X-SCTE35 or EXT-X-DATERANGE). Each viewer gets a session; the session node rewrites the manifest for that viewer, replacing the marked ad break with ad segments. Content segments and ad segments are served as one continuous stream, so the player sees no break and ad blockers have nothing to block.

Ad creatives are transcoded by the integrated UEN2 engine to strictly match the source signal: audio and video codecs, frame size, frame rate, bitrate, codec level and GOP structure. The conformed ad is kept in the ad-content cache (0 to 500 TB) so the same creative is not processed twice. The minimal first segment delivery latency is 700 ms.

  • Markers: EXT-X-CUE-OUT/IN · EXT-X-SCTE35 · EXT-X-DATERANGE
  • Per-session manifest with per-viewer ad pods
  • Ads conformed to source codecs, frame size, fps, bitrate, GOP
  • Transcoding on CPU, Intel QSV, NVEnc or Netint
  • Output as HLS/DASH, with DRM

Targeting and personalisation

Targeting runs in real time per session. The ad request carries viewer demographics, location, device type and content preferences, so two viewers of the same channel receive different ad pods. The session view shows the session data for each stream: user IP and country, user agent, origin URL and the rendition ladder of the master playlist.

  • Demographics, location, device type, content preferences
  • Each session identified and traceable in the dashboard
  • Prefixes configure many channels over one SSAI config

Live and VOD, with VOD that starts at once

On live channels the ad break is triggered by the marker in the stream and filled as it happens. On VOD, most SSAI systems first resolve every ad pod of the asset (pre-roll and every mid-roll) and only then let playback begin, so the viewer stares at a spinner while the ad server answers. Prism X runs VOD in lazy mode: the asset starts immediately, the pre-roll is served, and later pods are requested while the viewer watches.

Pre-rolls are first-class: the slot before the first frame is a sold slot, on live joins and on VOD, with the same targeting and the same counting as mid-rolls.

  • Live: breaks driven by SCTE-35 / CUE / DATERANGE markers
  • VOD lazy mode: instant start, pods fetched on the fly
  • Pre-rolls on live joins and VOD, counted like any pod
  • Same session nodes for live and on-demand

Ad decisioning: VAST, primary and secondary

Prism X speaks VAST and VPAID upstream to the SSP/DSP of your choice; in the Noisypeak FAST pipeline this is typically SpringServe or OpenX. A secondary VAST/VPAID source fills pods the primary leaves empty. The datasheet gives Adbutler as the example backup source, and Adbutler integration is available for evaluation out of the box.

  • Upstream protocols: VAST, VPAID
  • Primary SSP/DSP plus secondary fill-in source
  • Adbutler integration as reference SSP/DSP

A readable dashboard and fair CPM

The SSAI dashboard lists every session with start time, duration, last activity, ad time and average fill rate, and opens a per-session timeline: content in blue, ad pods in red, origin URL, rendition ladder, viewer IP and user agent. When a sales house asks why a pod was empty at 21:14, you answer with one click instead of a log query. Billing follows fair CPM: an ad is counted only when it was actually delivered to the viewer. Every session is logged to ClickHouse; run-time metrics go to Prometheus and Grafana.

  • Fair CPM: delivered ads only
  • Logs to ClickHouse, metrics to Prometheus/Grafana
  • Per-session fill rate, pod count, viewed share
Sessions list: ID, viewer IP and country, start, duration, last activity, ad time and average fill rate for each session.
Sessions list: ID, viewer IP and country, start, duration, last activity, ad time and average fill rate for each session.

Scaling and deployment

Prism X is delivered as dockerised software with Ansible playbooks for setup and updates. A deployment runs 2 to 50 session processing nodes and 2 to 100 content transcoding nodes on Ubuntu or Amazon Linux, in the Noisypeak Cloud, on bare metal, VMware, Hyper-V, AWS, Google Cloud or Microsoft Azure. The cloud option gives managed scaling; on-premise gives full cost control for operators who want the lowest CPM overhead.

  • Docker delivery, Ansible setup and update
  • Ubuntu, Amazon Linux
  • Noisypeak Cloud, bare metal, VMware, Hyper-V, AWS, GCP, Azure
  • Trial from the Noisypeak Cloud with fastchannels.tv playout channels
Session view: timeline of content (blue) and ad pods (red), origin URL, rendition ladder, viewer IP and user agent.
Session view: timeline of content (blue) and ad pods (red), origin URL, rendition ladder, viewer IP and user agent.

Features

SSAI you can run yourself

Does what AWS MediaTailor does, in the Noisypeak Cloud or on your own servers and cloud accounts. Docker and Ansible, 2–50 session nodes, 2–100 transcoders.

VOD starts instantly

Lazy mode: the asset plays at once and ad pods are fetched during playback, so you don't wait for every ad to load before the first frame.

Pre-rolls included

The slot before the first frame is sold too, on live joins and on VOD, targeted and counted like any mid-roll.

A dashboard humans can read

Every session, pod and fill rate on one timeline. Finding out why a pod was empty at 21:14 takes one click instead of a log query.

Real-time targeting per session

Demographics, location, device and content preferences. Two viewers of the same channel get two different ad mixes.

Fair CPM

An ad is counted only when it reached the viewer. ClickHouse logs, Prometheus / Grafana metrics to prove it.

Primary + secondary VAST

VAST / VPAID to your SSP/DSP (SpringServe, OpenX or any other), with a backup source filling the pods the primary leaves empty.

Ads that match the stream

Integrated UEN2 transcoding conforms every creative to source codec, size, fps, bitrate, level and GOP; cached up to 500 TB. 700 ms to first segment.

Markers in, DRM out

EXT-X-CUE-OUT/IN, SCTE-35, DATERANGE in; HLS / DASH with DRM out. Ad blockers can’t remove the ads and the player doesn’t stall at ad breaks.

Many channels, one config

Prefixes configure hundreds of channels over one SSAI configuration. This is how we run 200+ FAST channels.

Specifications

Formats
Stream formatsHLS · MPEG-DASH, in and out
OutputHLS/DASH with DRM, targeted ads per session
Source complianceStrict: audio/video codecs, frame size, fps, bitrate, codec level, GOP structure
Ad markers
Supported markersEXT-X-CUE-OUT / EXT-X-CUE-IN · EXT-X-SCTE35 · EXT-X-DATERANGE
Ad standards
Upstream protocolsVAST · VPAID
Secondary sourceYes, pod fill-in from an alternative/backup VAST/VPAID source (e.g. Adbutler)
VODOptimised: pod requests handled over the duration of playback
CountingFair CPM: ads actually delivered to end users
Scaling
Session processing nodes2 to 50
Content transcoding nodes2 to 100
Content transcodingCPU · Intel QSV · NVEnc · Netint
Ad-content cache0 to 500 TB
First segment latency700 ms minimal
Mass deploymentPrefixes to configure many channels over one SSAI config
Integrations
SSP/DSPAny VAST/VPAID source · SpringServe, OpenX in the FAST pipeline · Adbutler reference integration
LoggingVisual logging · ClickHouse
MetricsPrometheus · Grafana dashboards
Transcoding engineNoisypeak UEN2 (Noisypeak Cell)
Deployment
Host OSUbuntu · Amazon Linux
EnvironmentsNoisypeak Cloud · bare metal · VMware · Hyper-V · AWS · Google Cloud · Microsoft Azure
DeliveryDockerised software · Ansible playbook setup and update
EvaluationFrom the Noisypeak Cloud, with fastchannels.tv playout channels for trial

Where it is used

FAST channel monetisation

Ad breaks from Noisypeak Playout filled per viewer through SpringServe / OpenX. This is how our 200+ channels on 40+ platforms are monetised.

Live TV with targeted ads

Broadcast channels with SCTE-35 markers, re-monetised per device, location and audience on OTT, pre-roll on join included.

VOD libraries that start instantly

Pre-roll and mid-roll pods on on-demand catalogues, filled during playback instead of before the first frame.

Leaving the big-cloud SSAI bill

Operators who want cost control run the same stack on their own hardware or cloud account, with fair CPM and no surprise per-request fees.

Talk to us about Prism X

We handle evaluation in the Noisypeak cloud, deployment on premises or in a public cloud, integration and support. One team covers the whole pipeline.

Works with

Noisypeak / Solutions / Noisypeak DRMBrochure · PDF

licensing · content protection

Noisypeak DRM

Licenses for every screen. Multi-DRM licensing and entitlements on the pipeline that already encodes and watermarks your content.

13 Apr 2027Google shuts Widevine CLS; migrate before then
2DRM systems: FairPlay, Widevine (own license servers)
CPIX · SPEKEany packager, any player
Offlinepersistent licenses supported

Noisypeak DRM is the licensing and entitlement layer of the Noisypeak platform. Its license servers decide, per request, whether this viewer on this device may play this content: a FairPlay Streaming KSM for Apple devices and a Widevine license server for Android, Chrome, smart TVs and set-top boxes. Both are Noisypeak's own implementations, independent of Google's cloud. It's the service BuyDRM or EZDRM would sell you, with one difference: the encoder, the packager and the ad inserter that produce the encrypted streams are ours too. For everyone else's, CPIX / SPEKE or a custom integration plugs in any third-party packager and player.

Policies follow the industry model and cover the full range each DRM system allows: license duration and renewal, rental and playback windows, persistent licenses for offline viewing, output and device constraints, key rotation. Around the license sits the rest of the protection: JWT (RFC 7519) link tokens and access lists validated at the origin, AES-128 for the simple cases, and an inaudible forensic audio watermark per channel, territory or viewer, for the day a copy leaks.

audiomarked copyleaked copyrequestlicense + policySourcelive feed or VOD assetEncoder / packagerUEN2 · CENC encryption ·HLS fMP4 · DASH · keysWatermark embeddingper channel · territory ·user copyOriginJWT tokens · access lists· start-overCDNtokenised linksLicense serversFairPlay KSM · Widevineproxy · entitlement…Playerslicense required todecrypt · offlineForensicswatermark detection · leaksource
Noisypeak DRM: from source to licensed player. One encrypted packaging feeds FairPlay and Widevine; the license servers decide per request; the origin validates tokens; the watermark traces a leaked copy.
Widevine CLS ends 13 April 2027

Google is shutting down its Cloud License Service and the Proxy SDK path. Noisypeak's Widevine server does not depend on it; we migrate direct customers, and users of any other hosted or self-hosted CLS-based solution, before the date.

Any packager, any player

CPIX and SPEKE for third-party packagers and encoders; custom integration schemes where needed. Cell, Packetizer and Prism X are wired in already.

Every screen the audience owns

FairPlay covers iPhone, iPad, Mac, Apple TV, Safari; Widevine covers Android, Chrome, Android TV, Fire TV, Roku, Samsung, LG and most set-top boxes.

Offline included

Persistent licenses for download-and-watch are part of the service.

License delivery: FairPlay and Widevine

A player asks for a license and Noisypeak DRM answers. For Apple devices that is a FairPlay Streaming key security module with your FPS certificate. For everything else it is a Widevine license server: Android, Chrome, Edge, Android TV, Fire TV, Roku, Samsung Tizen, LG webOS and set-top boxes. Both are Noisypeak's own implementations and make no call to Google's Cloud License Service, which Google retires on 13 April 2027. They run as a service in the Noisypeak Cloud, behind one API, with content keys generated and stored for every asset and channel.

The streams they unlock can come from the Noisypeak platform: Cell and Packetizer encrypt HLS (FairPlay) and DASH (Widevine via CENC) from one encode, and Prism X delivers ad-stitched streams with the protection intact. They can also come from any third-party packager and player, through CPIX / SPEKE key exchange or a custom integration scheme.

  • FairPlay Streaming KSM (own implementation)
  • Widevine license server (own implementation, no Google CLS dependency)
  • CPIX / SPEKE for third-party packagers; custom schemes on request
  • Content keys generated, stored and rotated per asset and channel
  • AES-128 static key where full DRM is not required

Entitlements and policies

Entitlement is decided at license time, per request. The customer sets the rules within the range each DRM system supports, following industry practice: license duration and renewal, rental and playback windows, persistent licenses for offline viewing, output protection and device-type constraints, and key rotation on live channels. Playback links themselves are tokenised with JWT (RFC 7519) and checked at the origin, with access lists and start-over configured in memory. A leaked URL expires, and a revoked account stops at the next request.

  • License duration, renewal, rental and playback windows
  • Persistent (offline) licenses
  • Output protection and device constraints as the DRM allows
  • Key rotation on live channels
  • JWT-tokenised links, access lists, start-over at the origin

Leaving Widevine CLS before April 2027

Google has announced that the Widevine Cloud License Service will be permanently shut down on 13 April 2027. Many platforms and vendors built on this free hosted endpoint, directly or through the Proxy SDK. After that date, license requests to it fail and Widevine playback stops. Noisypeak DRM never depended on it.

We move you across before the deadline: our direct customers, and operators on any other hosted or self-hosted solution that still calls CLS underneath. Keys and policies are carried over, packagers and players re-pointed through CPIX / SPEKE or the integration already in place, and both services run in parallel until the switch is verified.

  • Shutdown date: 13 April 2027 (Google)
  • Affected: CLS users, Proxy SDK and CAS Proxy SDK users
  • Noisypeak Widevine server: independent of CLS
  • Migration for direct customers and users of other CLS-based solutions
  • Parallel run until verified

Forensic watermarking

Noisypeak's digital watermarking applies inaudible encrypted packets to the content so that a copy can later be identified per channel, per territory or down to a specific end-user. It can be applied to an existing content item, to a specific stream, or to an individual user copy during delivery, and can be combined with the transcoding and DRM steps of the Noisypeak Cloud. The mark is not lost when the signal is converted or compressed, and it is robust to copying including camripping.

Compared with usual embedding procedures: generating individual copies takes less time and compute; the secret watermark key is not needed to produce individually marked copies; the unmarked original can be retrieved; and because watermarks are encrypted, unauthorised third parties cannot check for their presence. Noisypeak provides the forensic tools and services to identify the source of a leak.

  • Audio watermark, applied in the cloud or on premises
  • Granularity: VOD asset · stream · individual user copy
  • Content: HLS v2/3 · HLS v5 · DASH · Google Classic DRM (WVM)
  • Survives conversion, compression and camripping
  • Encrypted mark, undetectable without the key

Watermark quality

Audibility was assessed with the commercial OPERA tool implementing the PEAQ model, on 180 audio tracks: pop, classical, audio book, interview and camera recordings. The objective difference grade (ODG) scale runs from 0 (inaudible) to −4 (very annoying); the watermarked set scores a median ODG of −1.5.

  • OPERA / PEAQ objective difference grades
  • 180 test tracks across five content types
  • Median ODG −1.5

Where it sits in the pipeline

Protection is the stage between encoding and distribution: Cell or Media2Flow encode, Packetizer or the Cell origin package and encrypt, Prism X stitches ads without breaking the encryption, and Noisypeak DRM hands out the licenses to B2B2C OTT platforms, set-top boxes, mobile, PC and smart TV. The origin serves up to 2,500 parallel streams and 20 Gb/s per node, tokens validated on every request.

Features

Licenses for every screen

FairPlay KSM and Widevine license server, both Noisypeak's own implementations. One API covers every device your audience owns.

A home before Widevine CLS closes

Google shuts its Cloud License Service on 13 April 2027. Our Widevine server never depended on it, and we migrate you whichever solution you are on today.

Entitlements as well as keys

Duration, renewal, rental and playback windows, device and output constraints, key rotation. You set them within what each DRM allows, and they're decided per request.

Offline included

Persistent licenses for download-and-watch are included in the service.

Any packager, any player

CPIX / SPEKE key exchange for third-party packagers and encoders, plus custom integration schemes where needed, so it works beyond Noisypeak outputs.

Already wired to the pipeline

Cell, Packetizer and Prism X encrypt for these license servers out of the box; everyone else connects over CPIX / SPEKE.

A watermark that names the leaker

Inaudible, encrypted audio mark per channel, territory or viewer; survives re-encoding and camripping. Forensic tools identify the source.

Links that expire, lists that decide

JWT (RFC 7519) validated at the origin on every request; access lists, start-over, time-boxed URLs.

Marked copies at scale

Individual watermarked copies cost less time and compute than usual embedding, need no secret key to produce; the original is recoverable.

Measured, not claimed

Watermark audibility tested with OPERA / PEAQ on 180 tracks across five content types: median ODG −1.5.

Specifications

License delivery
AppleFairPlay Streaming (HLS), own KSM implementation
GoogleWidevine via CENC (MPEG-DASH), own license server, independent of Google CLS
Key exchangeCPIX · SPEKE · custom integration schemes
Key-onlyAES-128 static key
OfflinePersistent licenses supported
PoliciesLicense duration and renewal · rental and playback windows · output and device constraints · key rotation (within each DRM system's range)
DeliveryAs a service from the Noisypeak Cloud
Widevine CLS migrationBefore 13 April 2027, for direct customers and users of other CLS-based solutions
Encryption and packaging
EncryptionCENC for MPEG-DASH · FairPlay for HLS · AES-128
PackagingHLS (TS) · HLS3 · HLS7 fMP4 · MPEG-DASH from one channel
WhereNoisypeak Cell / UEN2 origin · Noisypeak Packetizer (NP-RPK-EMB) · Prism X output
Tokenization and access
Link tokensJWT, RFC 7519
Access controlAccess lists · content protection · start-over, in-memory configuration
Publishing authWebDAV authorization
Origin performanceUp to 2,500 parallel streams over 25 Gb/s · up to 20 Gb/s sustained over 25 Gb/s or 2×10 Gb/s LACP
Forensic watermarking
TypeAudio watermark, inaudible and encrypted
GranularityPer channel · per territory · per end-user (VOD asset, stream or individual user copy)
Content typesHLS v2/3 (audio muxed in TS) · HLS v5 (separate audio track) · DASH · Google Classic DRM (WVM)
RobustnessNot lost through conversion or compression · robust to copying including camripping
PayloadEncrypted identifying information (channel, territory or user), not detectable by unauthorised parties
DetectionContent owner deciphers the mark; Noisypeak forensic tools and services identify the leak source
QualityOPERA / PEAQ, 180 tracks · median ODG −1.5
DeploymentNoisypeak Cloud or on premises; with or without Noisypeak transcoding and DRM steps

Where it is used

Migrating off Widevine CLS

Platforms and vendors that call Google's Cloud License Service, directly or through the Proxy SDK, move to Noisypeak license servers before 13 April 2027. Both run in parallel during the move, and keys and policies are carried over.

Premium live and SVOD on OTT

One encrypted HLS/DASH packaging, FairPlay and Widevine licenses for every device, policies per plan.

Download-and-watch

Persistent licenses with rental or playback windows for offline viewing on phones and tablets.

Token-gated catch-up and start-over

JWT links and access lists control who can open a protected stream at the origin.

Tracing a leak

Per-user watermarked copies identify the account behind a pirated stream, even after camripping.

Talk to us about Noisypeak DRM

We handle evaluation in the Noisypeak cloud, deployment on premises or in a public cloud, integration and support. One team covers the whole pipeline.

Works with

Noisypeak / Solutions / Noisypeak PacketizerBrochure · PDF

packager · origin · DVR

Noisypeak Packetizer

Packager, origin and DVR in one node. Any compressed stream comes in and leaves in every format, without re-encoding.

0re-encodes (video passed through)
4streaming formats from one input, in parallel
2,500parallel streams per node
20 Gb/ssustained delivery per node

Noisypeak Packetizer sits between a broadcast head-end and the internet. A compressed stream arrives (DVB/IPTV multicast TS, SRT, RTMP, HLS, NDI or a TS file) and leaves as HLS (TS and fMP4), MPEG-DASH, Microsoft Smooth Streaming and SPTS/MPTS multicast, all at the same time, with the video untouched. With no transcoder in the path there is no quality loss and no GPU, and a channel costs a fraction as much.

The same node is the origin and the DVR: it serves the streams itself with time-shift, catch-up and start-over, validates JWT tokens and access lists on every request, and sustains 2,500 parallel streams and 20 Gb/s. SCTE-35 cues survive the trip for Prism X to monetise; DVB subtitles are burnt in or turned into WebVTT by OCR; CEA-708 / EIA-608 captions are carried. It runs on Noisypeak Cell hardware, as a software licence, or in the Noisypeak Cloud.

cuesDVB / CCsegmentsmarkersWebVTT / burn-intime-shiftedservepushInputsTS multicast · SRT · RTMP· HLS · NDI · TS filesDemux / selectstream selection · DVB PIDpass-through · video…SCTE-35detection · pass-through ·splicingSubtitlesDVB burn-in · DVB → WebVTTOCR · CEA-708 / EIA-608DVR buffertime-shift · catch-up ·start-overPacketizerHLS TS · HLS3 · HLS7 fMP4· DASH · MSS · multicastOriginJWT tokens · access lists· 2,500 streamsPublishingCDN · WebDAV · FTP · SMB ·RTMP · YouTube · Facebook…
How Noisypeak Packetizer repacks a channel. One input is demuxed once and written to every output format in parallel; the origin serves them with DVR and tokens.
No re-encoding

Video passes through bit-exact. The picture your head-end made is the picture the viewer gets.

Three boxes become one

Packager, origin and DVR buffer on one node. That means one licence, one thing to monitor and one place to look when a stream misbehaves.

Every player, one input

HLS for Apple, DASH for Android and TVs, Smooth for legacy players and multicast for the STB fleet, all at the same time.

Head-end signalling intact

SCTE-35, DVB subtitles, closed captions and PIDs come through, so downstream ad insertion and accessibility keep working.

One input, every output, in parallel and without re-encoding

Packetizer is the origin mode of the UEN2 engine. From a single input it produces four streaming types at once: HLS with audio and video renditions as separate TS tracks, HLS3 with audio and video muxed in TS, HLS7 with separate fMP4 renditions, and MPEG-DASH with separate fMP4 renditions and a timelined manifest. It also emits Microsoft Smooth Streaming, SPTS/MPTS over UDP unicast or multicast, RTMP (Akamai support) and TS or MP4 files. HLS goes up to version 7 with multi-language support and a secondary destination point.

  • HLS (TS, separate renditions) · HLS3 (muxed TS) · HLS7 (fMP4)
  • MPEG-DASH Live and VOD, timelined manifest
  • Microsoft Smooth Streaming
  • UDP unicast/multicast SPTS and MPTS
  • RTMP with Akamai support · TS and MP4 files
  • Video passthrough

DVR: time-shift, catch-up, start-over

The origin keeps a recording buffer per channel, so the same node that packages the live stream also serves it time-shifted, as catch-up, or from the start of the current programme (start-over). Start-over, content protection and access lists are advanced configurations held in memory on the origin. When Packetizer is used behind Media2Flow, the DVR depth is set per live channel when the channel is created.

  • Time-shift and catch-up from the origin buffer
  • Start-over on live channels
  • Thumbnail generator (NP-RPK-EMB)

SCTE-35 and captions

SCTE-35 CUE-IN/CUE-OUT messages are detected in the input and either passed through to the HLS/DASH manifests, where Prism X picks them up for ad insertion, or used to splice the stream. DVB subtitles are either burnt into the picture or converted by OCR into WebVTT tracks; closed captions are carried as CEA-708, EIA-608 or WebVTT. DVB PIDs can be passed through unchanged, and individual streams of an HLS or SPTS source can be skipped.

  • SCTE-35 detection, pass-through and splicing
  • DVB subtitles burn-in · DVB → WebVTT OCR
  • Closed captions CEA-708 · EIA-608 · WebVTT
  • DVB PID pass-through · HLS/SPTS stream selection

Origin performance and protection

In origin mode a node delivers up to 2,500 parallel streams over a 25 Gb/s interface and up to 20 Gb/s sustained traffic over 25 Gb/s or 2×10 Gb/s LACP interfaces. Links are tokenised with JWT (RFC 7519); access lists and content protection are applied in memory. The NP-RPK-EMB licence adds Widevine (CENC) and FairPlay encryption to the repacked HLS/DASH output; the full DRM set is covered by Noisypeak DRM.

  • Up to 2,500 parallel streams over 25 Gb/s
  • Up to 20 Gb/s sustained over 25 Gb/s or 2×10 Gb/s LACP
  • JWT RFC 7519 link tokenization · access lists
  • Widevine (CENC) and FairPlay with NP-RPK-EMB

Publishing and integration

Multiple formats are published simultaneously: direct to CDNs, to WebDAV (with authorization) or Windows shares (Samba), FTP, HTTP, RTMP, YouTube Live and Facebook Live. In Media2Flow, Packetizer channels show up as live channels (input UDP, RTMP, SRT, HTTP/HTTPS or HLS pull, bound to an encoder template, availability zone and DVR depth). They reach audiences through Distributions, which give one point of presence, one set of origin and live channels and one network whitelist. Externally encoded HLS feeds can be registered as third-party channels and served from the same edge.

  • CDNs · WebDAV · Samba · FTP · HTTP · RTMP
  • YouTube Live · Facebook Live
  • Media2Flow Distributions: PoP, channel bundle, whitelist
  • Third-party HLS feeds forwarded unchanged

Features

Any input, every format, no re-encode

TS multicast, SRT, RTMP, HLS, NDI or TS files in; HLS (TS / fMP4), DASH, CMAF, Smooth Streaming and SPTS/MPTS out, in parallel, with the video passed through.

Origin and DVR on the same node

Time-shift, catch-up and start-over from the origin buffer, so you don't need a separate recorder or origin server.

2,500 streams, 20 Gb/s per node

Origin mode serves viewers directly over 25 Gb/s or 2×10 Gb/s LACP; JWT (RFC 7519) tokens and access lists checked on every request.

SCTE-35 through, ads downstream

CUE-IN / CUE-OUT are detected and either passed into the HLS/DASH manifests or spliced. Prism X picks them up for per-viewer ad insertion.

Subtitles that survive the internet

DVB subtitles burnt in or converted to WebVTT by OCR; CEA-708, EIA-608 and WebVTT closed captions carried.

Publish everywhere at once

CDNs, WebDAV, Samba, FTP, HTTP, RTMP, YouTube Live and Facebook Live from the same channel.

Protected on the way out

Widevine (CENC) and FairPlay encryption with the NP-RPK-EMB licence; AES-128; thumbnail generation included.

Fits the fleet

Appears as a live channel in Media2Flow with DVR depth per channel; distributions per audience with PoP and whitelist; third-party HLS forwarded unchanged.

Runs where the head-end is

On Noisypeak Cell hardware, as a software licence on your servers, or in the Noisypeak Cloud.

Specifications

Inputs
TransportRTP/UDP SPTS and MPTS multicast · SRT · RTMP · RTSP · HLS · HTTP progressive · HTTP TS
Baseband / IP videoNDI · SDI · HDMI (via Noisypeak Cell capture)
FilesTS files (file2live, file2vod)
AudioAAC / AAC LATM · MP2 / MP3 · AC3 · EAC3 · Opus
Outputs
HLSUp to v7, multi-language · HLS (TS, separate renditions) · HLS3 (muxed TS) · HLS7 (fMP4) · secondary destination point
MPEG-DASHLive and VOD · fMP4 · timelined manifest
CMAFfMP4 (HLS7 and MPEG-DASH)
Smooth StreamingMicrosoft Smooth Streaming
Transport streamsUDP unicast/multicast SPTS · MPTS · DVB PID pass-through
OtherRTMP (Akamai support) · TS and MP4 files · SDI · NDI · video passthrough
ParallelMulti-format simultaneous publishing · HLS/SPTS stream selection
DVR
FunctionsTime-shift · catch-up · start-over
ConfigurationAdvanced in-memory configuration: start-over, content protection, access lists
Media2FlowDVR depth set per live channel
Captions and subtitles
DVBBurn-in subtitles · DVB to WebVTT OCR
Closed captionsCEA-708 · EIA-608 · WebVTT
SCTE-35
HandlingDetection · pass-through of CUE-IN/CUE-OUT · splicing
Origin performance
StreamsUp to 2,500 parallel streams over a 25 Gb/s interface
ThroughputUp to 20 Gb/s sustained over 25 Gb/s or 2×10 Gb/s LACP interfaces
TokensJWT RFC 7519 link tokenization
ProtectionAccess lists · content protection · Widevine (CENC) and FairPlay (NP-RPK-EMB)
Publishing
TargetsCDNs · WebDAV (with authorization) · Windows share (Samba) · FTP · HTTP · RTMP · YouTube · Facebook
Licences
NP-RPK-EMBNoisypeak Repack: MCAST/HLS in, HLS/DASH out, TS and MP4 media, DVB to WebVTT OCR, Widevine (CENC) and FairPlay, thumbnail generator, start-over
NPXS-SWNoisypeak Cell software licence incl. HLS/DASH packetizing, WebDAV, DRM, SCTE-35

Models and licences

NP-RPK-EMB

Noisypeak Repack · multi-protocol repacketizer for integrated solutions · MCAST/HLS in, HLS/DASH out · DVB→WebVTT OCR · Widevine (CENC), FairPlay · thumbnails · start-over

NPXS-SW

Noisypeak Cell software licence · MPEG2 / H.264 / HEVC / AV1 · HLS/DASH packetizing · WebDAV · DRM · SCTE-35 · one Intel integrated GPU

Where it is used

IPTV head-end to OTT, cheaply

The existing multicast line-up repacked to HLS and DASH for apps and smart TVs. No transcoders are needed, quality stays as it was and SCTE-35 is preserved.

Broadcast multicast to OTT

A DVB/IPTV multicast TS repacked to HLS and DASH for web, mobile and smart TV, SCTE-35 cues preserved.

Catch-up and start-over TV

Live channels served time-shifted or from programme start from the same origin node.

Multi-CDN and social simulcast

One channel pushed at once to CDNs, WebDAV/FTP targets, YouTube Live and Facebook Live.

Accessibility on OTT

DVB subtitles converted to WebVTT by OCR, CEA-708/EIA-608 captions carried into HLS and DASH.

Talk to us about Noisypeak Packetizer

We handle evaluation in the Noisypeak cloud, deployment on premises or in a public cloud, integration and support. One team covers the whole pipeline.

Works with

Noisypeak / Solutions / Noisypeak ControlBrochure · PDF

stream verification · coming soon

Noisypeak Control

Watches your streams the way a player does and tells you what is wrong, with the evidence. Coming soon.

100+checks: transport, manifest, container, content, ads, alignment
4levels by playback impact (red: not playable)
3tiers per channel: playlist · adaptive-high · full
Soonnext release: accounts, trial and slots

Noisypeak Control is the DigitalEye Stream Verifier, now in its final release before production. Give it a master playlist or an MPD and it does what a player does: it reloads the manifests, downloads the segments, probes and decodes them and extracts a frame per chunk. Then it tells you what a player never will: whether every tag, timing, bit rate, GOP, colour flag, loudness level and ad marker is what the specification and your platforms expect. When a check fails, it raises an alarm with the evidence: the manifest as it was, the segment record, the exact ffprobe command and its output.

Severity follows playback, not pedantry: a stream that plays fine on real players is never red. Yellow is a deviation players cope with, orange is really wrong, red is not playable or not reachable. One compact row per channel, a window per channel for the long watch, tiers per channel so a hundred channels cost what a hundred channels should. Launching soon as a hosted service with a 14-day trial; custom locations, SLA and on-premise on request.

Your channelmaster .m3u8 or .mpd · HLSTS / fMP4 · DASHManifestsreload rhythm · sequence ·PDT · ladder · ad markersSegmentsdownload · TS / fMP4structure · timing · bit…Decodecodecs · GOP · colour ·A/V sync · black · freeze…100+ checksRFC 8216 · DASH-IF · AppleHLS spec · practiceEvidencemanifest + diff · segment· ffprobe outputChannel windowsummary · preview ·renditions · health…Alarmswarning · major ·critical, by playback…
What the verifier does with a channel. Playlist tier reads manifests only; adaptive-high adds segments and decoding like a player on a good link; full checks every rendition and proves the ladder is aligned.
It sees what the viewer sees

It checks manifests, segments, decoded frames and audio levels, which goes well beyond pinging a URL.

Evidence, not opinions

Every raise keeps the manifest, the diff, the segment and the ffprobe output. Reproduce the finding yourself.

Red means unplayable

Severity by playback impact. Spec deviations that players tolerate stay yellow; nobody is paged for a missing tag.

Pays per channel, not per rack

Three tiers per channel; paused channels free the slot; boost a channel to full inspection for a launch and back.

One row per channel, one window for the long watch

The channel list shows one compact row per stream: name, what it plays (HLS v3 TS, HLS v7 fMP4, DASH fMP4 $Time$), tier, the tags the verifier detected (codecs, HDR, captions, DRM, ad markers), the health strip over the selected range, the ladder with its live-edge lag, and the last event. Filter by text or by tag logic, sort worst-first, act on many channels at once. Groups are saved filters.

Click a channel and it opens in its own window with Summary (what the stream is and who is behind it: packager, origin, CDN and ad stitcher, recognised from signatures), Preview (the latest frame of every rendition side by side), Renditions, Health, Stats and Events. To watch a few channels for hours, put several windows side by side.

Channel list: protocol badge, tier, detected tags, health strip over the range, ladder and lag, last event.
Channel list: protocol badge, tier, detected tags, health strip over the range, ladder and lag, last event.

100+ checks, each with its rule

Every check states what it verifies, what a failure means for viewers, where the rule comes from (RFC 8216, the DASH-IF timing model, Apple's HLS authoring specification or operational practice) and how it is evaluated: raised after N failing polls, cleared after M passing ones, with a start-up phase so a restarting channel isn't red for a minute. Groups: transport and HTTP, live manifest, HLS playlist, DASH MPD, segment download, MPEG-TS and fMP4/CMAF container, stream probe, video content, audio content, ad markers, rendition alignment, verifier health.

Among them: publish jitter and stale playlists, PDT gaps and drift, bit rate against BANDWIDTH and AVERAGE-BANDWIDTH, GOP and IDR regularity, colour signalling, interlaced sources, A/V skew, black and frozen pictures, silence and loudness (ATSC A/85 or EBU R 128 targets), SCTE-35 CUE-OUT/IN consistency and alignment to IDR frames, DASH timeline and UTC timing, AES-128 key fetch, and whether all renditions show the same moment.

  • Thresholds per channel: tolerances, expected colour, loudness target
  • Shun an alarm you know about: still recorded, no longer colours the channel
  • Change-type alarms stay visible for an hour so a one-off change cannot pass unseen
Health per rendition: measured peak and average bit rate against the declared BANDWIDTH, with the exact threshold that raised the alarm.
Health per rendition: measured peak and average bit rate against the declared BANDWIDTH, with the exact threshold that raised the alarm.

Evidence you can reproduce

An alarm without evidence is an argument; an alarm with evidence is a ticket. Every raise and clear is an event; click it and you get the manifest as it was and the previous one with the difference, the segment record, and for segment-level alarms the exact ffprobe and ffmpeg commands that were run and their output. Send it to the encoder vendor or the CDN as it is.

Events: alarms in range with share of raises and active renditions; each row opens its evidence.
Events: alarms in range with share of raises and active renditions; each row opens its evidence.

Tiers, slots and boosts

Playlist reads every manifest on every reload and downloads nothing: availability and manifest hygiene for many channels at low cost. Adaptive-high also downloads the segments one at a time, like a player on a good link (mostly the top rendition, now and then a lower one), and probes and decodes them. Full does everything on every rendition and compares the first frame of each segment across the ladder. It is the only tier that proves the ladder is aligned. A slot licenses one active channel of its tier; pausing a channel frees the slot. Every period includes boost hours to lift any channel to a higher tier for a launch or a hunt.

  • Playlist · Adaptive-high · Full, set per channel
  • Slots per tier, prorated changes, paused channels free the slot
  • Boost hours included; boost packs on top
  • VOD playlists and static MPDs played once, twice or in a loop

Encoder fleet redundancy: NP-RFS

For Noisypeak Cell fleets, Control also carries NP-RFS: 1+1, n+1 and n+m redundancy for clusters of 2 to 100 devices, up to 20 clusters per instance. Each primary's configuration is replicated to central storage; when a primary fails its standby takes the channels, a publishing gate ensures primary and backup never publish the same output at once, and return to the primary is automatic or manual. Zabbix, Prometheus/Grafana and SNMP see the whole fleet.

Features

Watches like a player, reports like an engineer

Reloads manifests, downloads and decodes segments and extracts frames, then checks every tag, timing, bit rate, GOP, colour flag, loudness and ad marker against the spec.

100+ checks, each with its rule

RFC 8216, DASH-IF, Apple HLS spec or practice: transport, manifest, container, content, ad markers, rendition alignment.

Evidence on every alarm

The manifest and its diff, the segment record, the exact ffprobe output. Reproduce it, or forward it to the vendor as is.

Red means unplayable

Severity by playback impact: yellow players cope, orange really wrong, red not playable or not reachable. Shun what you already know.

Ad markers verified

SCTE-35 in HLS tags, MPD events and emsg: CUE-OUT/IN pairs, durations, PDT alignment, IDR alignment. You see the problem before Prism X has to find out.

Loudness and silence

ATSC A/85 or EBU R 128 targets, true peak and silence, per rendition, continuously.

Ladder alignment proven

Full tier compares the first frame of each segment across renditions: the only way to know all renditions show the same moment.

Who is behind the stream

Packager, origin, CDN and ad stitcher recognised from signatures, which helps when the stream isn't yours.

Per-channel tiers

Playlist, adaptive-high, full; slots, boosts, pause. A hundred channels cost what a hundred channels should.

Fleet redundancy for Cell

NP-RFS: 1+1, n+1, n+m failover for clusters of 2–100 encoders, config replicated, Zabbix / Prometheus / SNMP.

Specifications

Streams
ProtocolsHLS (MPEG-TS, fMP4/CMAF, EXT-X-MAP) · MPEG-DASH (SegmentTemplate $Time$ / $Number$, SegmentTimeline)
Live and VODLive channels · VOD playlists and static MPDs played at real time or download speed, once or looped
EncryptionAES-128 HLS (key fetch and decryption checked) · DRM streams observed at manifest and container level
Ad markersSCTE-35 via EXT-X-CUE-OUT/IN, EXT-X-DATERANGE, MPD Events, emsg
Checks
Catalogue100+ checks in 13 groups, each with spec reference, raise/clear counts, evidence kind
Profilesplaylist · download · full · optimized built in; clone to customise
Levelsinfo · warning · major · critical, by playback impact
Per-channel settingspoll interval, tolerances, expected colour, loudness target, start-up phase, request headers
Evidence and history
EvidenceManifest + previous + diff · segment record · ffprobe/ffmpeg commands and output · segment bytes for major alarms
RetentionSamples 7 d · 1-minute rollups 90 d · events 90 d · long-term statistics kept
Service
TiersPlaylist · Adaptive-high · Full, per channel; slots per tier; boost hours
AccessHosted at smon.noisypeak.com: e-mail or Google sign-in, 14-day trial (coming soon)
CustomCustom locations, SLA, invoicing and on-premise on request
NP-RFS (Cell fleets)
Redundancy1+1 · n+1 · n+m; clusters of 2–100 devices, up to 20 clusters
BehaviourConfig replication · publishing gate · automatic or manual return · Stay on Slave
MonitoringZabbix · Prometheus/Grafana · SNMP · JSON API; up to 50 encoders in one console

Where it is used

FAST channel operator

Every delivered channel watched 24/7 at playlist tier; adaptive-high on the money-makers; ad markers verified before the platform complains.

Launch and acceptance

Full tier for a day: ladder alignment proven, every rendition decoded, evidence attached to the acceptance report.

Chasing a vendor fault

Bit rate over BANDWIDTH on two renditions since Tuesday, with the segments and the ffprobe output to send to the encoder vendor.

Monitoring streams that are not yours

Platform feeds and partner channels: the Summary tells you who packages and delivers them, and when they break.

Talk to us about Noisypeak Control

We handle evaluation in the Noisypeak cloud, deployment on premises or in a public cloud, integration and support. One team covers the whole pipeline.

Works with

Noisypeak / Solutions / Legacy products

Legacy products

Loudness, quality assessment, audio watermarking, earlier encoders and CDN.

Alongside the current product line, Noisypeak maintains a set of specialised tools and earlier encoder generations: loudness control, perceptual quality assessment, audio watermarking, previous NP Cell platforms supported under NP-RFS, and the Noisypeak CDN for content-aware distribution.

ListenPerfect

Loudness control software for hundreds of linear streams: ITU-R BS.1770 with EBU R128, ATSC A/85, TR-B32 and OP-59; SPTS/MPTS in, SPTS out; 200+ channels on one dual-Xeon server.

DigitalEye QA

Perceptual visual quality assessment: PSNR, SSIM, VMAF and the DigitalEye deep-neural-network metric, benchmarking encoders across 496+ renditions; developed with EPFL's Multimedia Signal Processing Group.

AWM watermarking

Encrypted, imperceptible audio watermarks for live and VOD content, per channel, territory or user; HLS v2/3, HLS v5, DASH and Google Classic DRM; forensic tools to trace leaks.

NP Cell EX / Blade / One LT

Earlier encoder generations, supported under NP-RFS.

Noisypeak CDN

Content-aware distribution layer of the Noisypeak platform, deployed in the Swiss cloud, public cloud or on-premise.

Still running one of these?

They are supported under NP-RFS. Talk to us about maintenance, migration to the current products, or keeping them exactly as they are.