Matt: (give explanation about the
background)
... discussion new features
... please go to the issue tracker and file issues
<wolenetz> https://github.com/WICG/media-source
Mark: (shares his screen to share that resource)
Matt: (explains wicg work)
Matt: this particular issue has been incubated
Matt: current incubation at:
https://github.com/WICG/media-source/tree/mse-in-workers-using-handle
issue 175 MediaSource in Worker
Matt: one solution would be
parallel processing
... api extension for MSE
... how to attach media source URL
... working on demo
... looking for folks interested
... would love to have more people
... a lot of work to happen there
... e.g., what is blocking in iOS
... also garbage collection
... technical blockers for MSE
... MSE spec doesn't state concrete way for
implementations
... so several options for implementations
... trying to get better implementation experience
... continue discussions
... better ability for interoperability
... interested to hear your opinions
Mark: tx
... how would you best like people to participate?
... what's the best way to participate in the discussion?
Matt: please comment and keep
commenting
... if you feel like narrower communication, you can directly
contact me or Mark Watson
... John Simmons as well
... would love to have comments
Mark: any questions?
Nigel: thinking about
object-based
... switch between streams
Matt: maybe a couple of
contexts
... brief example?
Nigel: if we got different
audio/video content
... potential make them together
... in a simple case, just switching between those
channels
... but need without gaps
Matt: a couple ways
... buffering beforehand
... another way migh tbe multiple tracks
... more than video/audio tracks
Nigel: another question about
content
... looks more like data such as subtitles or captions
Matt: historically implementations
are slow
... may need intervening time
... out of and use
Nigel: thinking about inband
data
... an example is dash.js
... subtitle on the side and synchronization
... different ways to get media
Matt: can think of several
ways
... players use JS library
... something to discuss for new features
Nigel: didn't necessarily mean need
for native player implementations
... possibly JS layer
Matt: something very specific for some byte stream
Mark: sounds like an issue for some specific case
Matt: something to think about
<Barbara_Intel> Roadmap - Is there a MSE roadmap (MVP and post-MVP) of issues/bugs versus enhancements? For example AV1 or uses 360 or immersive or live is an enhancement.
Matt: would like to understand the scenario
Mark: any other questions?
John: is there an issue tracking for content validation?
Matt: not a MSE issue
... but if you go back to the previous session
... there was some discussion
... someone interested in byte stream handling
... dash, cmaf validations
Will: if there is similar code base, we might want to look into that
John: we intend to create test
content
... many contents we've already implemented
Matt: there are several issues we have not resolved
John: bridging those two things interesting
Barbara: good time to ask a
question?
... hearing a couple of things connected to roadmap
... also hearing usage
... pipeline for 360
... what we trying to fix
... streaming and alive richer enhancement
Matt: much of work
... fixing up some of the issues
... buffered media
... what to do the gap
... clearer definition to understand what's happening
... please file an issue
... are you seeing a gap?
Barbara: more interested in higher
roadmap for standardization
... what is the minimum product
Matt: tx for your feedback
Will: change type
specifically?
... what are the other browser doing?
... other than chrome
... mozilla, ms, chromium, safari
Matt: not sure about the other implementations, but...
John: MS is moving to chromium-based
Mark: any other questions?
Matt: would like to mention wpt work
Mark: would like to thank Matt for
giving talk
... also thank all for participation
[adjourned]