-
Notifications
You must be signed in to change notification settings - Fork 0
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
New Playback Requirement: Event Message Processing #53
Comments
(19/11/06 DPCTF)
For making the tests complete, we need
|
An initial proposal is provided here, but needs more work: |
#76 makes the point that some of the streams should have events in them as a matter of principle. |
dash.js uses the IsoBoxer library to check for EMSG boxes: https://github.com/madebyhiro/codem-isoboxer Workflow is as simple as we check for EMSG after segments have been downloaded. Event handling is done in a separate class (EventController). We support version 1 and 2 events. This logic could be reused if required, although decoupling of other dash.js parts is required. |
As far as I can tell. MSE implementations and browsers don't do anything with emsg boxes & should ignore them. If this is correct then there's nothing for WAVE to test here. |
I think Iraj and DASH-IF are working on this in the context of MSE v2. I agree that currently nothing can be tested here with MSE v1 |
At this stage this is implemented as a javascript library. No test are needed. It would be reasonable to refer to
Propose to add the above informative description. |
@jpiesing noted that we decided to test to confirm event messaging does not break anything. |
Included in latest contract. Close. |
8.20 Event Message Processing
CTA WAVE content may contain event messages of relevance for the application.
The first version of this specification does not define a test for this.
The text was updated successfully, but these errors were encountered: