-
Notifications
You must be signed in to change notification settings - Fork 1.7k
2016 Munich Face to face meeting
Will Law edited this page Apr 21, 2016
·
31 revisions
The 2016 European face-to-face meeting of the dash.js project on GitHub. 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.
Thanks to Maxdome for hosting this event.
Registration: Please register your attendance at Eventbrite.
Where: Medienallee 4 - 85774 Unterföhring, Germany - View Map
When: May 19, 2016
- 08:30 - 09:00 – REGISTRATION, WELCOME COFFEE
- 09:00 - 12:30 – MORNING SESSION
- 12:30 - 13:30 – LUNCH, NETWORKING
- 13:30 - 17:00 – AFTERNOON SESSION
- 19:00 – 21:00 - GROUP DINNER
Please add your proposed agenda items to the list below. The actual order will be adjusted prior to the meeting.
- APIS for playing back from live - time vs segment. Discuss minimum APIs necessary and default values.
- baseURL - discuss segment retry APIs and priorities. Establish consensus around which fail-over schemes should be offered and the APIs necessary to sustain those.
- Demo by Technische Universitaet Berlin, who have developed a low delay live streaming adaptation algorithm.
- Competitive discussion - dash.js vs Shaka vs Bitmovin. Where is dash.js behind? Where does it need to improve?
- Support for webM via webm.js - not compatible with current dash.js (#1301). Should we continue support? Who is interested in working on this initiative?
- VirtualBuffer - proposal for removal. Why? What benefits? Can it be replaced with a mapping class that maps time ranges/bitrates/resolutions.
- Allow fast bitrate switching - fetch next segment ahead of playhead rather than front of buffer. Rules for doing this.
- Under what conditions when switching periods can we re-use the SourceBuffers and thereby achieve a seamless switch? How to add this feature to existign workflow? Use of AVC3 in particular is of interest here.
- Set minimum requirements for anyone saying "dash.js doesn't work" on github or slack. Example's: provide a public mpd and clear steps to problem reproduction, provide the mpd (even if its not public), provide the relevant portions of the console log, provide the exact code branch/build/fork you are referencing etc.