W3C home > Mailing lists > Public > public-web-and-tv@w3.org > June 2018

RE: [me-media-timed-events] ISO BMFF Byte Stream Format spec does not mention emsg

From: <stockhammer@gmx.org>
Date: Wed, 6 Jun 2018 16:50:23 +0200
To: "'John Simmons via GitHub'" <sysbot+gh@w3.org>, <public-web-and-tv@w3.org>
Message-ID: <005101d3fda5$b356aeb0$1a040c10$@gmx.org>
DASH-IF has an ongoing work to define consistent event processing by defining an API between the DASH client and the application.

Dash.js already implements an event processing model and we are currently reviewing if this is sufficient or if we need a second option for which the timing is handled in the application rather than in the DASH client.

More details can be shared, but we need some time to consolidate the details.

Thomas

-----Original Message-----
From: John Simmons via GitHub <sysbot+gh@w3.org> 
Sent: Mittwoch, 6. Juni 2018 16:44
To: public-web-and-tv@w3.org
Subject: Re: [me-media-timed-events] ISO BMFF Byte Stream Format spec does not mention emsg

My understanding - the scope of the ISO BMFF Byte Stream Format spec is to be used by the Media Source Extensions spec, and that the scope of the Media Source Extensions [https://www.w3.org/TR/media-source](url) spec is the dynamic construction of media streams for <audio> and <video>. Exposing emsg events to JavaScript Apps is out of scope for the Media Source Extensions (DataCue? Other?). And based because it is scoped to use by the MSE spec, emsg is also out of scope for the Byte Stream spec. Thoughts?

--
GitHub Notification of comment by johnsim Please view or discuss this issue at https://github.com/w3c/me-media-timed-events/issues/1#issuecomment-395094001 using your GitHub account
Received on Thursday, 7 June 2018 00:09:06 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 7 June 2018 00:09:07 UTC