Low Latency Streaming Meeting Minutes
2026-06-25 09:00:00 to 10:00:00 PT

Attendees

Robin Wilson (Streaming Video Technology Alliance (SME))
Michael Demb (TAG Video Systems)
Rob Roskin (Google)

Minutes

  • Summary

The meeting focused on discussing video streaming latency measurements and issues with player implementation. Robin and Rob discussed findings from a recent player team meeting about different approaches to measuring latency in DASH and HLS protocols, with various implementation methods depending on the specific streaming approach used. The group debated the significant latency variations observed between different devices and reinitializations, with Robin proposing an accountability approach to challenge manufacturers about explaining large latency differences. They also discussed the status of a pending document about low latency protocols and their effects on latency, which appears to be in editing draft status despite being nearly complete.

 

  • Action Items

Rob

  • Post or share the summary/notes on player latency measurement approaches (including CMCDv2 information and relevant URLs) in the main group thread or Google Doc for broader team access.

Robin

  • Send a reply to Hali (copying Rob and relevant group members) requesting the latest link to the "low latency protocols and their effects on latency" document for final review and confirmation of status.
  • Follow up with Nico at Qualabs regarding the implementation and practicality of the player latency reporting key in CMCDv2, and discuss with other player contacts about its real-world usage.

Collaboration

  • Robin/Rob/Lindsey: Confirm the current status of the low latency document (whether editing is truly complete or still in progress) and coordinate with Jason and Hali as needed to finalize and prepare the document for voting.

 

  • Antitrust Statement & Video Streaming Solutions Discussion
  • Rob and Robin discussed a previous meeting about implementing video streaming solutions, where the player team explained there are multiple approaches depending on the technology used (DASH, HLS, low latency versions of each).
  • Robin asked for clarification about how latency measurements would be calculated across different components of the media pipeline, and Rob explained that while the player could access information like M3U8 files and segment lengths, more specific measurements would require additional details about a particular stream.

ATSC Device Latency Strategy

  • Robin discussed a strategy for addressing latency variations in ATSC devices during a plug fest organized by Sinclair Broadcasting.
  • The plan involves conducting multiple tests to gather statistically significant data on latency variations between different receiving devices, then presenting the findings to manufacturers to request explanations for the observed differences.
  • Robin noted that this approach could also apply to streaming devices, as similar latency variations are known to occur in streaming contexts.

Latency Issues Accountability Discussion

  • Robin discussed the need for manufacturers to provide clear explanations for latency issues in their devices, particularly when measurements show significant delays.
  • He proposed holding CE companies accountable by directly asking them to explain latency variations, starting with companies like Samsung, LG, and Sony, and potentially involving CDNs in the discussion to determine responsibility.
  • Robin expressed frustration with the current finger-pointing between different parties without clear ownership of the issues.

Streaming Latency Discussion

  • Michael and Robin discussed latency issues in streaming players, with Robin claiming field measurements show significant discrepancies from expected standards.
  • Michael challenged Robin's claims about specific latency numbers, explaining that 2-second chunks are common for regular latency HLS and DASH protocols rather than the shorter segments Robin mentioned.

Latency Measurement Results Review

  • Robin suggested accounting for 10 seconds in the production pipeline, resulting in about 25 seconds available for other components.
  • Michael noted that when testing directly from the CDN, he observed 26-27 seconds latency, indicating that much of the delay likely comes from intentional elements like the "big red button" rather than technical limitations.

Streaming Latency Issues Discussion

  • Michael discussed latency issues with streaming, noting that while the best part works perfectly with only half a second delay, the player adds an additional 10 seconds.
  • Robin explained that some companies like Reborn and other virtual MVPDs may experience concatenation effects, with streams being re-encoding and repackaged, which can almost double the latency in some cases.
  • Robin also mentioned a survey from Phoenix (now owned by Perform Stats) that showed significant variations in latency between different instances of the same player, with some showing drift of 10-30 seconds.

Latency Testing and Protocol Updates

  • The team discussed latency testing results and methodology, with Michael explaining that consistent testing across different devices and scenarios would help determine if variations in measurements were due to device reconnections or other factors.
  • Robin expressed concern about potential inconsistencies in player latency reporting, particularly for older TV models that might lack necessary libraries for accurate measurement.
  • The group also addressed the status of a document on low latency protocols, with Robin agreeing to follow up with Hallie to obtain a link to the current version and clarify the editing status, as there was confusion about whether the document was complete.

 

Next Meeting: Thursday, July 9, 2026 9 am PDT

Have A Question ABout Membership?

Schedule A Meeting

Send An Email

Don’t want to schedule a face-to-face meeting just now? No problem. Simply send your membership question to info@streamingvideoalliance.org or fill out the form below and someone will get back to you as soon as possible.

"*" indicates required fields

Name*
Email*