NeoKadrix Player
A white-label playback engine built for live operations
NeoKadrix Player brings live, DVR and on-demand playback into one controlled integration surface, with resilient delivery policies, consumer-grade controls and telemetry for engineering teams.
Private preview. Platform coverage, protocol combinations and third-party integrations are qualified per deployment.
Build or integrate
Choose where your engineering effort belongs
The comparison describes typical delivery models. Exact capability and commercial scope depend on the selected player, devices and integration requirements.
| Capability | Open-source player | In-house build | Traditional commercial player | NeoKadrix Player |
|---|---|---|---|---|
| Core delivery footprint | Library dependent | Application defined | Package dependent | Published per release profile |
| Time to a controlled deployment | Integration required | Longest | Shorter | Staged private preview |
| Brand control | High | Complete | Varies by licence | White-label by design |
| Broadcast headend readiness | Custom qualification | Custom work | Vendor matrix | Deployment qualification path |
| Low-latency live | Extension dependent | Custom work | Package dependent | HLS, DASH and WHEP scope |
| Live and DVR workflows | Requires assembly | Custom work | Package dependent | One playback surface |
| Delivery failover policy | Custom extension | Custom work | Package dependent | Integrated policy layer |
| TV and mobile interaction | Custom UI work | Custom work | SDK dependent | Unified UX scope |
| AI-assisted operations | Add separately | Build and operate | Package dependent | Qualified extension roadmap |
| Operational telemetry | Add separately | Build and operate | Package dependent | Playback-aware diagnostics |
Product direction
Playback, delivery and diagnostics in one product boundary
The product is designed to reduce separate integration layers without hiding operational evidence from engineering teams.
Lean integration surface
A modular player boundary intended to keep the application integration small and explicit.
Resilient delivery policies
Origin and CDN switching policies distinguish transport failures from entitlement and DRM rejections.
Broadcast-to-OTT workflows
Integration targets include workflows built around Harmonic, Ateme and MediaKind environments, subject to qualification.
Cross-screen experience
A shared interaction model for browser, touch and 10-foot television interfaces.
Playback-aware diagnostics
QoE signals, an engineering HUD and diagnostic snapshots connect viewer symptoms to technical evidence.
Developer platform
One deterministic contract across playback engines and product surfaces
Application teams integrate with one versioned control and event boundary while engine-specific behaviour stays behind the player core.
Standardized unified developer API
A single interface normalizes HLS, MPEG-DASH, Safari native playback and qualified WHEP adapters, reducing engine-specific SDK code.
Deterministic state machine
Strict transitions across idle, loading, playing, buffering, stalled and destroyed states make lifecycle behaviour predictable and testable.
Generation fencing and fast channel zapping
Each source change advances a generation token so stale asynchronous network and decoder work can no longer mutate the active playback session.
Strictly typed EventBus
UI-independent TypeScript event contracts support React, Vue and Svelte integrations, with explicit adapter boundaries for native iOS and Android bridges.
OpenAPI 3.1 cloud backend gateway
A predefined NeoKadrix Cloud contract covers licence verification, multi-screen concurrency policy and usage-metering integrations within the agreed private-preview scope.
Playback and interoperability
One playback surface across live and on-demand workflows
Each deployment is qualified against its device matrix, packaging profile, latency target and security requirements.
Streaming formats
HLS and LL-HLS, including byte-range and chunked-transfer workflows; MPEG-DASH Multi-Period and CENC profiles; CMAF low-latency, WHEP integrations and progressive VOD.
Timeline and codec changes
Controlled AVC, HEVC and AV1 transitions where the target browser, hardware decoder and presentation timeline support a continuous switch.
Live timing and drift
Latency targets, live-edge recovery and drift handling are qualified against the selected packaging profile, network path and device class.
Headend qualification
Deployment-specific interoperability testing for manifests and streams produced by Harmonic VOS360, Ateme TITAN, MediaKind or the selected packaging stack.
Live DVR & sliding-window timeshift
Pause, scrub and rewind live HLS and MPEG-DASH streams within the available DVR window. Precision timeline synchronization, one-click Back to Live latency recovery and Catch-up TV workflows use HLS Program Date Time metadata or the corresponding DASH presentation timeline.
Monetization and ad control
Ad signalling and playback policy stay on the same timeline
The player coordinates cue interpretation, ad playback and viewer controls with the selected server-side or client-side advertising stack.
SCTE-35 signalling
Integration paths for cues transported through MPEG-TS workflows or ISOBMFF emsg events, validated against the selected packager output.
SSAI and HLS Interstitials
Server-side ad insertion and EXT-X-DATERANGE interstitial workflows reduce dependence on client-side ad scripts; behaviour still depends on the delivery profile.
Google IMA client advertising
Client-side advertising integration targets for VAST 4.x and VMAP workflows using the Google IMA SDK.
Ad-break conditioning
Configurable seek restrictions, control lockouts, tracking events and loudness-handling hooks during qualified ad breaks.
No player can guarantee universal ad-block avoidance. Delivery behaviour is verified against the complete advertising and distribution chain.
Broadcast accessibility
Caption, subtitle and audio workflows treated as primary playback tracks
Accessibility scope is qualified per stream format, device platform, regulatory target and application experience.
Broadcast caption ingestion
Qualification paths for in-band CEA-608/708 captions carried in supported broadcast-to-OTT packaging workflows.
Multi-format subtitles
WebVTT, IMSC1 and TTML/SMPTE-TT workflows, including forced narratives and language selection.
Viewer customization
Font, size, colour, background opacity and positioning controls designed to support WCAG- and FCC-aligned application requirements.
Audio language and surround
Persistent language preference and multi-track selection, with 5.1/7.1 pass-through where the source, browser, device and output chain support it.
Revenue and content protection
Security controls stay aligned with the playback session
Player-side controls complement the entitlement, packaging, licence and watermarking services selected for the deployment.
Multi-DRM integrations
Integration paths for Apple FairPlay Streaming, Google Widevine Modular and controlled ClearKey test profiles; security level is determined by device and licence policy.
Watermarking workflows
Support boundaries for server-assisted forensic watermarking and visible session watermark overlays.
Session enforcement
Playback hooks for entitlement, concurrent-session and device-policy decisions made by the service backend.
Credential-sharing controls
Cloud policy hooks for real-time screen and session limits, with enforcement decisions owned by the entitlement backend.
DRM robustness, watermark resistance and advertising behaviour depend on the complete delivery chain and cannot be guaranteed by the player alone.
High availability and delivery resilience
Failover decisions preserve the session without masking authorization failures
Source switching is governed by explicit health evidence, recovery policy and deployment-specific continuity tests.
Redundant source pool
Policy-controlled selection across a qualified pool of origins or CDNs, with the supported pool size defined by the deployment profile.
Continuity-aware recovery
Preserve playback position when replacement manifests expose compatible media timelines and the target device can continue safely.
Anti-flap isolation
Cooldown, recovery thresholds and per-origin token or cookie boundaries prevent unstable routes from repeatedly re-entering service.
Safe error discrimination
Transport failures and 5xx outcomes can trigger recovery policy; entitlement 4xx and DRM rejections remain visible to the application.
Continuity depends on aligned manifests, keys, timelines and authorization across the delivery pool; zero interruption is verified, not assumed.
Viewer experience
Familiar controls on touch, web and television screens
The experience layer is designed for white-label products rather than a fixed NeoKadrix skin.
Touch gestures
Double-tap seeking, edge controls, temporary playback-speed boost and an optional control lock.
10-foot navigation
D-pad interaction patterns for Smart TV applications, qualified against each target platform and application shell.
Continuous viewing
Skip Intro and Credits, Up Next countdowns, thumbnail scrubbing, picture-in-picture and casting integration points.
Picture-in-picture and casting
Native and Document PiP paths plus AirPlay and Chromecast integration points where the platform permits them.
Extension roadmap
AI-assisted video features under qualification
These capabilities describe planned investigation and are not part of the current private-preview commitment.
Predictive adaptation
Evaluate network forecasting as an input to bitrate selection, with results measured against representative sessions.
Highlights and chapters
Explore assisted scene segmentation and candidate highlight generation for editorial review.
Contextual metadata
Investigate time-aligned object and topic metadata for interactive video experiences.
Client-side enhancement
Assess speech enhancement and device-side image processing only where performance and battery impact are acceptable.
Assisted root-cause analysis
Correlate diagnostic evidence and prepare incident drafts for review before submission to a support system.
No performance, traffic-saving or quality-improvement percentage is claimed until a repeatable benchmark and test matrix are published.
Quality of experience
Playback telemetry that operations teams can act on
Measure the session from start-up through delivery changes, decoder behaviour and viewer-visible interruptions.
Session QoE
Time to first frame, rebuffering, bitrate changes, dropped frames, live-edge distance and fatal playback outcomes.
CDN real-user monitoring
Origin and CDN TTFB, request outcomes, recovery events, ISP context and available cache evidence correlated with the active playback session.
Fleet views
Aggregate TTFF, latency drift, rebuffering, dropped frames and fatal outcomes by application version, device, network, geography and content profile.
Incident routing
Webhook-based alerting and integration targets for operational tools such as Slack and PagerDuty.
Engineering command centre
Expose the evidence without exposing the product internals
Operational tooling is separated from the viewer interface and can be restricted to engineering roles.
On-screen engineering HUD
Inspect buffer health, active bitrate, rendered frames, latency and decoder information during a session.
Frame and timeline inspection
Controlled frame stepping and timecode display for qualified review and control-room workflows.
Headless integration model
A UI-independent playback boundary with typed events for product-specific interfaces and workflows.
Diagnostic snapshots and assisted triage
Capture a structured snapshot, correlate likely causes and prepare a reviewable incident draft for Zendesk, Freshdesk, Intercom or Jira Service Management integrations.
Enterprise FAQ
Questions for product and engineering teams
The final delivery scope is agreed against a device, stream, security and operations matrix.
How would we migrate from our current player?
We begin with a stream and device qualification, map the existing event and analytics contracts, then move one controlled audience segment before wider rollout.
What service level is available?
Availability and support targets are defined in the commercial agreement after the deployment architecture and operational ownership are agreed.
How is security and compliance scoped?
We map entitlement, DRM, watermarking, session policy and audit requirements across the complete delivery chain. Certifications and regulatory commitments are stated only in the signed deployment scope.
How are EPG, captions and subtitles handled?
EPG and Catch-up timing are mapped to HLS Program Date Time or the corresponding DASH timeline. Caption, subtitle and audio support is qualified against the source format and target devices.
Which Smart TV platforms are supported?
Support is declared per tested application and device matrix. We do not infer platform coverage from browser playback alone.
Bring your stream, device matrix and operational requirements
We will map the playback path, identify the qualification work and define a private-preview plan with measurable acceptance criteria.