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

New Playback Requirement: Event Message Processing #53

Closed
haudiobe opened this issue Feb 13, 2019 · 9 comments
Closed

New Playback Requirement: Event Message Processing #53

haudiobe opened this issue Feb 13, 2019 · 9 comments
Assignees
Labels
resolved-implementation Issue is resolved and needs implementation

Comments

@haudiobe
Copy link
Member

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.

@haudiobe
Copy link
Member Author

haudiobe commented Nov 6, 2019

(19/11/06 DPCTF)

  • W3C work does some work on this
  • DASH-IF (see published information) + MPEG developed (see CDAM.1) an Event Processing Model as well (more or less completed)
  • dash.js has a polyfill that will do the work (preferably make this polyfill library independent of dash.js)
    We start from the DASH-IF/MPEG model for playback requirements (Thomas)

For making the tests complete, we need

  • Content Requirements for Event messages in CTA WAVE Content Specification - at this stage no difference CMAF, only guidelines and recommendations. Would be good to have a specific normative section in Content Specification (augmented with recommendations and guidelines) => 2020 spec.
  • Need Test cases and test material for this purpose
    (John)

@haudiobe haudiobe added this to the DPC Specification 2019 milestone Nov 6, 2019
@haudiobe haudiobe added the resolved-implementation Issue is resolved and needs implementation label Nov 6, 2019
@haudiobe
Copy link
Member Author

An initial proposal is provided here, but needs more work:
https://1drv.ms/w/s!AiNJEPgowJnWgos-u32ftrH96QvscQ?e=vPuxHh

@jpiesing
Copy link

jpiesing commented Jul 3, 2020

#76 makes the point that some of the streams should have events in them as a matter of principle.

@dsilhavy
Copy link

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.

@jpiesing
Copy link

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.

@dsilhavy
Copy link

dsilhavy commented Apr 1, 2021

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

@haudiobe
Copy link
Member Author

haudiobe commented Dec 8, 2021

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.

@haudiobe haudiobe added last-call-for-comments Issue will be changed to resolved/closed if no comment until next DPC call and removed resolved-implementation Issue is resolved and needs implementation labels Dec 8, 2021
@haudiobe haudiobe added resolved-implementation Issue is resolved and needs implementation and removed last-call-for-comments Issue will be changed to resolved/closed if no comment until next DPC call labels Dec 15, 2021
@gitwjr
Copy link

gitwjr commented Nov 22, 2022

@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.

@gitwjr
Copy link

gitwjr commented Feb 28, 2023

Included in latest contract. Close.

@gitwjr gitwjr closed this as completed Feb 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
resolved-implementation Issue is resolved and needs implementation
Projects
None yet
Development

No branches or pull requests

5 participants