The QoE Working Group discussed finalizing the error code proposal, focusing on standardizing player error codes to improve reliability and traceability. Tony Stott introduced the proposal, which uses a four-digit code format, with the thousands digit denoting the error domain and the last three denoting the error type. Key feedback from Apple included adding error codes for content steering manifests, interstitials, and low latency issues. The group also debated whether to include beacon errors, ultimately deciding to defer it for future revisions. The meeting concluded with plans to update the spec and continue discussions in two weeks.
- Review DASH/HLS interstitial/alternative-content naming and related specs (interop docs) and propose canonical term and wording for the error-code draft for the next meeting – Casey.
- Share the proposal link so participants can access and comment on the latest error-code draft, here: https://docs.google.com/document/d/1UckqiXlx1c0Ay039qrqxfDO3JoelyfwjCe_dvqMCznQ/edit?pli=1&tab=t.0.
- Update the error-code proposal to include the agreed changes: content-steering load/pause errors, alternative/interstitial (asset-list) load/parse codes, a low-latency fallback error, and clearer stall guidance (e.g., use video code if track unknown)
- Incorporate meeting feedback into the spec and circulate the updated draft to the group
- Antitrust Statement and WG Discussion
Introduction and Meeting Purpose
- Tony Stott initiates the meeting, apologizing for the scheduling issues from the previous session.
- Tony outlines the agenda, focusing on reviewing the error code proposal and finalizing it.
- Tony welcomes new members, including Rob Walsh from Apple and Slavik Lozben from VeoVera, who introduce themselves and their interests in the QoE working group.
- Tony provides an overview of the QoE work stream, mentioning the two major projects: error codes and MQA.
Error Code Proposal Overview
- Tony explains the goal of standardizing error codes to improve reliability and traceability of errors across different disciplines.
- The proposed error code system uses a four-digit format.
- Tony provides examples of how the error codes can provide context for engineers, such as network issues and buffer starvation.
- The proposal aims to avoid technology-specific details and keep the error codes open and granular.
Detailed Discussion on Error Codes
- Tony shares his screen to present the error code proposal, including the abstract, objectives, and design principles.
- The error categories are explained, such as playback issues, subtitles and captions, and advertising errors.
- Tony provides examples of specific error types, like bandwidth drops and missing segments, and how they can be reported.
- The discussion includes the importance of providing context for engineers to understand the root cause of errors.
- The team propose monitoring bespoke error codes being introduced in the custom codes category for possible inclusion in future spec revisions.
Feedback and Clarifications
- Rob Walsh from Apple raises questions about the difference between segments and fragments, which is explained in the document now.
- The team discusses the terminology used in the CMAF spec and how it applies to HLS and DASH.
- Rob suggests adding error codes for content steering manifests and interstitials, which are used in both HLS and DASH.
- The team considers the implications of low latency errors and how they should be reported.
Additional Feedback and Suggestions
- Rob suggests adding error codes for low latency issues and flagging when the player jumps away from the live edge.
- The team discusses the importance of distinguishing between terminal and non-terminal errors and how they should be reported.
- Rob raises the issue of stalls and whether the error codes should differentiate between audio and video stalls.
- The team agrees to add guidance on how to handle stalls and other non-terminal errors in the document.
Conclusion and Next Steps
- Tony summarizes the feedback and agrees to update the error code proposal based on the discussions.
- Tony mentions the upcoming meeting in Los Angeles and encourages participants to attend and provide further input.
- The meeting concludes with thanks from Tony and the participants, and a commitment to continue working on the error code proposal.
Next Meeting: Wednesday, March 11, 2026 8am PDT