2019 European dash.js Face to face meeting Berlin, May 20th
If you company has JavaScript developers working on MSE/EME players, please encourage them to attend this one-day meeting in Berlin on May 20th.
This meeting is the European face-to-face meeting of our dash.js project. This meeting is open to all dash.js community members, contributors, committers and other interested parties to present/discuss architectural, feature, scope and planning input for the project. The meeting is free to attend. Lunch will be provided as well as a dinner in the evening.
May 14th Agenda:
- 09:00 - 09:30 – REGISTRATION, WELCOME COFFEE
- 09:30 - 12:30 – MORNING SESSION
- 12:30 - 13:30 – LUNCH, NETWORKING
- 13:30 - 17:00 – AFTERNOON SESSION
- 18:00 – 21:00 - GROUP DINNER
This meeting is being hosted by Fraunhofer FOKUS in Berlin, in the same facility as the Media Web Symposium https://www.fokus.fraunhofer.de/go/mws which is held the two days following this dash.js meeting. The DASH IF face-to-face meeting will be held the last 2 days of that week, making for a packed week of the latest in OTT/Media technology. This is a fantastic opportunity to meet industry experts around media and explore the industry context in which dash.js resides.
Registration is open. This event is strictly registration-only and first-come, first served. You must pre-register in order to attend. Once we reach the capacity limit of 30 attendees, we will close registration. Please be respectful and if you do register, you must attend. If you register and are then unable to attend, please cancel your registration to enable a fellow community member to take your place.
Register here: https://dashjs-berlin-2019.eventbrite.com
Our agenda for the meeting is community-driven. After registering, we need you to contribute with some agenda items to the list below. Please, dedicate some time to think on 2-3 issues or 1 architecture topic you would like to have discussed, or demos that you would like to show. We have around 6 hours meeting so let's make it useful and interesting for everyone. Closer to the date I will create the final agenda. In case there are too many items I will prioritize the items that are relevant/interesting for most of the attendees.
We look forward to meeting and working with you in Berlin.
Cheers,
Jesús and Will
--------------------- Edit this page to add your desired agenda items below ---------------------
- Version 3 - changes, architectural walk-through, demos
- Moving from Version 2 to version 3. Documentation requirements.
- Functional testing
- Multi-period support - how to make robust (+1)
- Offline playback support. Status & Demo
- Build system changes. Migration to webpack
- Settings configuration - Any phase of retro-compatibility / deprecation before v3 ?
- Error recovery mechanisms added to dash.js
- Documentation changes. Proposal
- Promotion of dash.js
- Dynamic Ads Insertion demo (MediaTailor + MediaPackage + dash.js)
- Roadmap
- Dash.js extension capabilities. Network request filters.
- Switch-down logic for MBR ULL, how it works today, anticipated problems, how can we solve?
- ULL Join time - how to minimize
- Low-Latency DASH updates to guidelines - player recommendations and requirements (Thomas, 10min)
- Player APIs - do we need something consistent? (Thomas, 10min)
- Event Processing Model - how to get this into dash.js? (Thomas, 10min)
- CTA WAVE Device Playback specification tests - what is missing? (Thomas, 10min)
- DASH-IF version 5 - how much player requirements should we add? (Thomas, 10min)
- Fast start optimizations, including preloading manifests, downloading init segs and media segments in parallel, loading first A/V segments and then pausing or holding in memory, API to adjust starting buffer before playback begins.
- Better type management. This could be done improving Typescript or using Flow.js. Types would allow for errors to be caught on compile.
- Error checking/reporting with regards to gaps in the media stream, where currently the player will just stall go into an infinite download loop until the user seeks again.
- New W3C Media Capabilities API