Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mapping of emsg boxes to the media timeline #26

Open
chrisn opened this issue Nov 2, 2020 · 1 comment
Open

Mapping of emsg boxes to the media timeline #26

chrisn opened this issue Nov 2, 2020 · 1 comment

Comments

@chrisn
Copy link
Collaborator

chrisn commented Nov 2, 2020

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 w3c/media-source#189 for discussion.

One specific question raised was:

  • At what point do we know interoperably that we don't need to parse an emsg box because the time is already past?
@chrisn
Copy link
Collaborator Author

chrisn commented Mar 24, 2021

The DASH events timing model is described here (section 3).

The timeline mapping differs between emsg version 0 and version 1:

version 0:

startTime = PeriodStart - SegmentBase@presentationTimeOffset / SegmentBase@timescale + LAT + emsg@presentation_time_delta / emsg@timescale

LAT is the earliest presentation time of the Segment containing the Event Message box

version 1:

startTime = PeriodStart - InbandEventStream@presentationTimeOffset / InbandEventStream@timescale + emsg@presentation_time / emsg@timescale

How to these values relate to the MSE SourceBuffer.timestampOffset?

See discussion from 22/3/2021

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant