The Bug Hunter's Guide: Unraveling Video Players CMCD implementation in a month
summary
A CMCD Validator is built in a month with one‑week sprints and public planning, released an npm library in three weeks, a web validator for Shaka/Dash/Bitmovin/VideoJS, an extractor that acts as a proxy for mobile and stores data for analysis. The team finds and reports real implementation bugs — reported implementation bugs in Dash.js Bitmovin Shaka — proposes clarifying changes to the CMCD spec, and wires an analyzer into Elastic/Kibana to compare player behavior.
AI-written summary · about
chapters (12)
- 0:00CMCD community project intro
- 2:08Summer Camp coding challenge
- 3:32CMCD validation tools design
- 4:33Open methodology and teamwork
- 5:15Month-long sprint results
- 6:19Web validator for players
- 7:02CMCD data extractor
- 7:43Fixing player implementations
- 8:26Team and community impact
- 9:06External bug reporting impact
- 10:11CMCD standard clarifications
- 10:53Conclusion and future
related talks
12mRise of the Planet of CMCD v2: Building the next-gen player data interface with...
20mDistributed Request Tracing for the Streaming Video Ecosystem
08mHow Big Buck Bunny helped track down bugs
24mIt's time to rebuild your player with web components
39mBuild a kick-🍑 video player
58mModern & secure adaptive streaming on the Web
20mStreaming video in the browser without patents
43mMedia Source Extensions
