Skip to content

European 2017 face to face meeting Berlin, May 16th

Torbjörn Einarsson edited this page May 12, 2017 · 23 revisions

The dash.js project is holding its annual European face-to-face meeting on Tuesday May 16th in Berlin. This meeting is open to all dash.js contributors, committers and interested parties to present/discuss architectural, feature, scope and planning input for the project. The meeting is free to attend. Lunch will be provided and there will also be a dinner in the evening.

This meeting is being held at the Fraunhofer Fokus campus at Kaiserin-Augusta-Allee 31, 10589, Berlin. It is co-located with the 6th Annual Media Web Symposium. These two events are part of the "Media Web Week" - 5 days of the latest insights in internet delivered media such as 360°/VR Streaming, multiscreen interaction, media sync, SmartTV/HbbTV, protected adaptive streaming, related standardization and market development, with a strong focus on MPEG DASH. All events are free to attend. This is a fantastic opportunity to meet industry experts around media and explore the industry context in which dash.js resides.

Registration is open. You can register for all events at https://mws17.eventbrite.de , although it is possible to only register for and attend the dash.js meeting. We have a limit of 30 attendees for the dash.js meeting, so please register early.

Our agenda for the meeting is community-driven. After registering, please add the items you would like to have discussed to the list below. Also include any demos that you would like to show. Closer to the date I will then create the finalized agenda for the day.

  • 09:00 – 9:30: Welcome and introductions
  • 09:30 – 12:00: Morning session
  • 12:00 – 13:00: Lunch
  • 13:00 – 15:00: Afternoon session
  • 15:00 – 15:30: Coffee break
  • 15:30 – 17:00: Late afternoon session
  • 17:00 – 18:00: Reception
  • 18:00 – 21:00: Dinner at http://www.markthalleberlin.com

Hope to see you in Berlin in May!

Cheers Will

--------------------- Edit this page to add your desired agenda items below ---------------------

  1. DRM support - status, polyfills, workflow, key rotation
  2. CMAF low latency chunks and fetch() support
  3. Documentation and developer resources
  4. Captioning and IMSC1 - https://github.com/Dash-Industry-Forum/dash.js/pull/1693
  5. SANDLibrary and SANDServer
  6. Support for MPD chaining https://github.com/Dash-Industry-Forum/dash.js/issues/1770
  7. More European-friendly bi-weekly call time
  8. Project Admin list review and nominations for new admins additions.
  9. PR - Code review process.
  10. RC/testing cycle review process ([bbert] add automatic functional testing?)
  11. Budget from Dash IF to hire dev.
  12. Architecture - Adding unit tests and removal of singleton pattern
  13. Implementing of Dash Events
  14. Implementing offline playback
  15. Hiring a developer for DASH IF
  16. Live stream segment request timing - see http://24x7dash-i.akamaihd.net/dash/live/900080/dash-demo/dash.mpd and https://msl32test2-i.akamaihd.net/dash/live/257940/bostonlab/dash.mpd
  17. Better and clearer APIs to control buffer
  18. SegmentTimeline, dash.js deliberately does not look at UTCTiming at all.Some other players, notably shaka-player, uses UTCTiming also for SegmentTimeline.See https://github.com/Dash-Industry-Forum/dash.js/issues/1916#issuecomment-300471402.
  19. [Jani] Roadmap items, like CMAF, EME’s setServiceCertificate API support (Chrome 59 - Verified Media Path feature), [bbert] trick play (FFWD, FRWD), etc…
  20. [Jani] Keyrotation: - 1) would it be possible to use this feature if only the init segment carries PSSH and that does not get updated when keys rotate, however, the ‘sgpd’ box in segments are updated with the corresponding KID upon key change? 2) According to my latest information root-leaf keyrotation is the default method in Edge (PlayReady) environment. Would it be possible to enforce the basic crypto-period key rotation feature instead of the default one?
  21. Akamai MAE 2.0 demo
  22. Buglist - it's large. How do we encourage people to work through it? Triage process ?
  23. Live MSS support (incl. timestamp overflow)
  24. Multiperiod Live Use Cases and signaling:
    • KeyRotation (connected to point 1)
    • Ad Insertion
    • Black Out
Clone this wiki locally