Chris Needham
Chris Needham
The [DASH standard](https://www.iso.org/standard/75485.html) section 5.10.3.3.4 says: > `event_duration` provides the duration of the event in media presentation time. [...] The value 0xFFFF indicates an unknown duration. The DASH-IF "DASH Player's...
MSE [`SourceBuffer.remove(start, end)`](https://w3c.github.io/media-source/#dom-sourcebuffer-remove) allows the web application to remove media for a given time range. What should happen to event message boxes that are on the media timeline? * Event...
For DataCue to expose in-band emsg boxes to web applications, the spec would need to define a mapping to the HTML media timeline. See https://github.com/w3c/media-source/issues/189 for discussion. One specific question...
Question from @wolenetz at the [TPAC 2020 meeting on DataCue][1]: Does there need to be feature detection so that web applications can discover which types of UA-generated events are exposed...
The explainer should describe how DASH emsg values are mapped to `DataCue` objects. Consistent with the existing Webkit implementation, this could be something like: | DataCue field | emsg value...
Is there a need to be a need to be able to feature detect the DataCue API, for browsers that have implemented DataCue with possibly differing capabilities and API shape?
The [DASH-IF event processing model](https://dashif-documents.azurewebsites.net/Events/master/event.html) describes two dispatch modes for timed metadata events: * on-receive: provide the event/timed metadata sample data to the Application as soon as it is detected...
Scheme `urn:dvb:iptv:cpm:2014`, see [ETSI TS 103 285 v1.3.1](https://www.etsi.org/deliver/etsi_ts/103200_103299/103285/01.03.01_60/ts_103285v010301p.pdf) section 9.1.2.
Following #11, a question arises as to how a web application should identify the schema of timed metadata cues. This is needed to allow the application to subscribe to receive...
See https://aomediacodec.github.io/id3-emsg/