W3C
Media & Entertainment IG
Monthly Meeting
1 February 2022
MEIG Meeting, 1 February 2022
Logistics and Agenda
Date and time�1 February, 15:00 UTC
IRC�https://irc.w3.org/?channels=#me
IRC Guide�https://www.w3.org/wiki/IRC
Code of Conduct https://www.w3.org/Consortium/cepc/
Agenda
DataCue and video SEI event messages
Picture in Picture API for arbitrary content
Media Source Extensions v2:�Chrome Origin Trials
“MSE requires applications to provide fragments of containerized media (such as fragmented MP4, WebM, or MP3) to be able to buffer and play that media. If the application already has the media in a parsed and structured form, it can cost extra latency and code complexity to package that media into a container and feed it to MSE.
As the web platform is evolving to give applications lower-level abstractions for efficiently encoding and decoding media via the WebCodecs API, MSE can use WebCodecs media structures to let applications more efficiently feed their media to MSE.
Use cases include simplifying and improving performance of transmuxing HLS-TS into fMP4 for buffering with MSE, and low-latency streaming with a seekable buffer.”
Media Source Extensions v2:�Chrome Origin Trials
“Enable Media Source Extensions (MSE) API usage from DedicatedWorker contexts to enable improved performance of buffering media for playback by an HTMLMediaElement on the main Window context. By creating a MediaSource object on a DedicatedWorker context, an application may then create an ObjectURL for it and postMessage that URL to the main thread for use in attaching to an HTMLMediaElement. The context that created the MediaSource object may then use it to buffer media.
When the main context is busy servicing other application logic, restricting MSE to the main Window context can significantly impair the user experience due to delayed media playback start or stalled playback”
Web application UI performance on TVs
W3C/SMPTE Media Production Workshop
Next meeting
Resources
Thank you!