The Low Latency Streaming WG Call discussed key insights from the Mile High Video conference, highlighting that half of the discussions focused on latency. Robin shared details about a panel he chaired, which included experts from ATM, Comcast, Adobe, and Vindral. The panel emphasized the importance of low latency, particularly in gaming and betting, where precise latency targets are crucial. The group debated the effectiveness of their current focus on low latency versus expanding to a broader live streaming mandate. They also discussed the need for statistical analysis to measure latency accurately and the potential for a survey to identify key industry issues.
- Publish the summary and recording in the Slack channel, and ask members to review and provide feedback.
- Draft and run an industry survey to gather priorities and technical issues related to live streaming (including but not limited to latency) and report findings back to the group
- Revisit the group’s latency measurement paper to add statistical/real-world testing guidance (e.g., repeatable network play loops and sample-size guidance) and propose updates for the document
- Collect or request open-source playback/play-loop links (examples used by BBC and others), compile them, and distribute the list to the working group for use in lab testing and measurement
- Antitrust Statement & Mile High Video Conference Recap
- Robin discusses the Mile High Video conference, noting that half of the discussions focused on latency, both general and low latency.
- Robin chaired a group on low latency, which included experts from various companies like ATM, Comcast, Adobe, and Vindral.
- The panel discussed low latency streaming, including specific use cases like 4K HDR streaming and low latency for gaming and gambling.
- Robin highlights the importance of setting specific latency targets, such as 3.2 seconds in Hong Kong, for applications like betting.
BBC’s Latency Reduction Efforts
- Robin mentions the BBC’s work on reducing latency to be similar or better than broadcast, aiming for under 10 seconds.
- The BBC is conducting an opt-in trial with 20,000 participants, using low latency HLS with a segment size of slightly under two seconds.
- The trial includes a well-scripted 20-minute network loop emulated on Linux servers to stress test under real conditions.
- The BBC discovered and fixed bugs in the dash.js player, which affected latency and quality significantly.
Challenges in Measuring Latency
- Robin discusses the challenges in measuring latency, noting that it varies based on network conditions and player settings.
- The discussion highlights the need for statistical analysis to account for these variations, as a single measurement can be misleading.
- Robin suggests that the group should focus on helping the player team with these statistical challenges.
- The group discusses the importance of having a separate, independent group to ensure accountability and address latency issues effectively.
Potential Directions for the Group
- Michael questions the group’s direction, suggesting a broader focus on live streaming rather than just low latency.
- Robin and Christopher discuss the benefits of maintaining a focus on low latency while also considering broader live streaming issues.
- The group considers the possibility of conducting a survey to understand the main technical issues in live streaming, beyond just latency.
- Robin emphasizes the need for a disciplined approach to measuring latency, using well-thought-out play loops to emulate real-world conditions.
Geographical Latency Challenges
- Christopher suggests characterizing different geographical latency challenges, noting that latency varies significantly by region.
- Robin agrees, highlighting the need to define specific benchmarks for latency in different countries and regions.
- The discussion includes considerations for various distribution methods, such as OTT, cable, satellite, and IP TV.
- The group acknowledges the complexity of measuring latency in different geographical contexts and the need for accurate benchmarks.
Next Steps and Action Items
- Michael proposes summarizing the discussion and publishing it through the Slack channel for broader input.
- Robin suggests maintaining the group’s focus on low latency while also providing input to other working groups.
- Christopher emphasizes the importance of expanding the group’s mandate to include broader live streaming issues.
- The group agrees to continue the discussion and develop specific action items, including conducting a survey and providing input to other SVTA groups.
Next Meeting: Thursday, February 19, 2026 9am PST