Players and Playback WG Meeting Minutes – Monday, July 20, 2026, 8am PDT
Players and Playback WG Meeting Minutes – Monday, July 20, 2026, 8am PDT 1
SVTA Anti–Trust Statement 2
Working Group Links 2
Attendance: 2
Notes / Topics for upcoming calls 2
Accessibility WG 3
SDOs / Meeting / Workshops / Presentations / Promotion / Organization 3
Joint Developer Exchange 3
Face to face meeting in Rennes 3
Standardized Error Codes 3
LL-WG Request 3
Multi-CDN Switching 4
Common Media Library 5
Topics for 2026 5
Best practices for MSE/EME 5
Multiview – Best practices 5
WASM Performance Evaluations 5
Open Streaming Evaluation and Benchmarking Platform 5
Common QUIC/MOQ playback library 6
Media Players & Tools & others 6
General 6
dash.js 6
video.js 6
hls.js 6
Shaka 6
Exoplayer 6
Livesim2 7
MoQ 7
General 7
MOQtail 7
OpenMoQ 7
Others 7
SVTA Anti–Trust Statement
Working Group Links
Attendance:
Andrej Doubek, Casey Occhialini, Yasser Syed, Lindsey Richardson, Mathias Lacaud, Nedimar Turatti, Daniel Silhavy
Notes / Topics for upcoming calls
Accessibility WG
SDOs / Meeting / Workshops / Presentations / Promotion / Organization
Joint Developer Exchange
- Idea: Dedicated focus on media players every 4-6 weeks
- Goal: Use the call to get player developers together and discuss problems, roadmaps, standardization issues, Discuss Interop issues
- Exoplayer/Media3: Toni Heidenreich
- AV Foundation: Casey knows some people they talk to occassionally, do an HLS Interest meeting every year
- js: Rob Walch
- Shaka: Alvaro
- CML : Casey
- js: Daniel
- js: Christian Pilsbury
- Casey and Daniel talked to Toni Heidenreich (leading the Android Playback team (Media3, ExoPlayer))
- Reached out to the developers listed above and asked if they would be interested. Suggested to do the first call in August 3rd
Face to face meeting in Rennes
Standardized Error Codes
LL-WG Request
- Request by LL group: Hi Daniel and group, from discussions in the low latency streaming group we are asking for advice from your group on if it is theoretically possible to generate a metric(s) on total player induced latency for a live use case reported by the player itself.Simply stated that is the actual player latency PLUS the latency caused by the player (inadvertently or deliberately) requesting older segments from the CDN that may be seconds or even tens of seconds behind the most recently published (“live”) segment. This might be due to conservative or overly safe design by trading the risk of requesting a segment that somehow got slightly delayed by network congestion or contention for a little extra latency. Or looking at this another way – a player development or deployment team can get into trouble a lot more quickly by tuning tightly to “live edge” potentially resulting in occasional but highly visible stumbles than if they added a safety margin by requesting older segments resulting in slightly increased latency that few if any folks care about. Since the player has access to the manifest with all of its timing information, an accurate clock reference and decoder PTS etc., could this latency information be calculated and reported by the player or app itself? It would only need to be updated very occasionally. We appreciate any insights on this.
- DASH MPD specific settings to control latency
- CDN 404s might be cached so if player very aggressive it might run into frequent 404s
- HLS partial and full segments: Minimum latency, probably 3x segment duration
- Typically every player provides an API. Example:
- Native type 1 players might be a problem. They might not provide the required information
- CMCD v2 metrics can provide the target latency
- But fundamentally this brings a good question: do we need low-latency or we rather need a consistent latency.
- Depends on the use case. For instance for playback in a bar the streams shall be synchronized
Multi-CDN Switching
- SVTA Technical Report
- Open for review / comments now
- Approval goes through the board
- Should latest be published by IBC
- Reference demo page is up again hosted by 5G Emerge
Common Media Library
- https://github.com/streaming-video-technology-alliance/common-media-library
- Last CML call on 14.07
- Next Call on 11.08
- CMCD v2 live in js and hls.js and Shaka Player
- CMAF HAM
- Part of the CMAF spec
- Common format to describe both DASH and HLS
- Related to CTA-WAVE 5005/SVTA HLS/DASH Interop Spec
- Qualabs submitted changes to the C2PA implementation
- Castlabs working on async SourceBuffer contribution
- Open for suggestions what to work on next based on real use cases / real demand
Topics for 2026
- Project Descriptions:
- Working Group Poll
- @Daniel: To send email, Slack message to the group asking for potential contributors
Best practices for MSE/EME
Multiview – Best practices
- Potential participants
- Rob Koenen
- Daniel Silhavy
WASM Performance Evaluations
- Potential participants
- Daniel Silhavy
- Casey Occhialini
Open Streaming Evaluation and Benchmarking Platform
Common QUIC/MOQ playback library
Media Players & Tools & others
General
- V10 (Beta) releases
- https://github.com/videojs/v10/releases
- Trying to get something polished in the month. Next Demuxed would be a good deadline
- Building also a composable playback engine based on CMAF HAM
- js as top level engine and then replace the playback engine, for instance use SPF, hls.js or dash.js.
hls.js
Shaka Player
Exoplayer
- Working on content steering?
- Statement from Demuxed: Burak and Thasso introduced the SVTA P&P WG to Exoplayer developers
- Added support for content steering for HLS, DASH is next
- https://developer.android.com/media/media3/exoplayer/cmcd?hl=fr
- https://github.com/androidx/media/issues/2732
- Casey to add notes to ticket
Livesim2
MoQ
General
- Should we maintain a list of all the open-source implementations?
- Should we bring anything to this group?
- Interop testing
- Interop/Interim meeting
MOQtail
OpenMoQ
CMCD Validator
Others
- SCTE/SVTA Joint event
- Latest edition of SCTE35 / SCTE 224
- What should be the audience for this
- Planning ongoing, improving relations between groups
- Yasser organzing the speakers right now
- Working with OTT.x to carry their information of feeds
- Figuring out a date