At IBC 2026, we’ll demonstrate a joint proof of concept with Fastly (13.D301) and Hydrolix (14.C47) that connects player-side QoE, CDN delivery data and automated investigation in one workflow.
The setup uses dash.js v5.2.1 with CMCD v2 support for live playback delivered through Fastly. Fastly streams its CDN logs in real time into Hydrolix, providing a full-fidelity data foundation for delivery analysis.
From player and CDN signals to investigation
The demo shows different levels of player telemetry: From playback without CMCD, through CMCD v1, to CMCD v2 including event mode.
With CMCD request mode, player context travels with the media requests and becomes part of the CDN data flowing through Fastly into Hydrolix. CMCD v2 event mode additionally allows selected player events to be sent directly to EINBLIQ.IO.
This richer client-side context is valuable, but CMCD is not a prerequisite. Where no CMCD is available, EINBLIQ.IO can reconstruct session context from CDN logs and derive additional QoE and behavioral signals. With CMCD, those inferred signals can be complemented by explicit player-side information.
ML finds what deserves attention. Agents investigate it.
Hydrolix provides EINBLIQ.IO with normalized, full-fidelity delivery data. EINBLIQ.IO correlates this with session and QoE context and uses purpose-built machine learning to identify patterns and clusters worth investigating.
Specialized agents then work through the selected evidence to assess viewer impact, affected dimensions and likely causes, rather than trying to search the entire raw dataset themselves.
The resulting investigation context is written back into Hydrolix, where it can be viewed alongside QoS and QoE data and used to drill directly into the relevant time ranges, sessions and delivery evidence.
End-to-end workflow of the PoC. See it live at EINBLIQ.IO’s booth at 3.B48c
The PoC demonstrates an end-to-end workflow across:
dash.js player → Fastly delivery → Hydrolix full-fidelity data → EINBLIQ.IO ML + agentic investigation → investigation context back in Hydrolix
It also shows the additional possibilities opened up by CMCD v2 and event mode, while retaining support for the large number of streaming workflows where CMCD v1 (or no CMCD at all) is available today.
See it live at IBC 2026
See the joint demo live at IBC and talk to us about connecting player QoE, CDN data and automated investigation.