Closed haudiobe closed 1 year ago
(19/11/06 DPCTF)
For making the tests complete, we need
An initial proposal is provided here, but needs more work: https://1drv.ms/w/s!AiNJEPgowJnWgos-u32ftrH96QvscQ?e=vPuxHh
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 1) processing model 2) Javascript library that can be used as a reference that includes a) IsoBoxer library to check for EMSG boxes: https://github.com/madebyhiro/codem-isoboxer b) https://github.com/Dash-Industry-Forum/dash.js/blob/development/src/streaming/controllers/EventController.js
Propose to add the above informative description.
@jpiesing noted that we decided to test to confirm event messaging does not break anything.
Part of RFP: Change to test content generation scripts. Need to add event message to some content and do simple tests to see if anything breaks.
11/22/2022: No resolution.
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.