European 2022 face to face meeting, June 20th
Daniel Silhavy edited this page Jun 27, 2022
·
4 revisions
Björn Altmann, Vinay Rosenberg, Aswin Pyakurel, Babak Taraghi, Torbjörn Einarson, Wolfgang Schildbach, Will Law, Bernd Czelhan, David Eisenbacher, Moritz Fuchs, Görkem Güclü, Stefan Pham, Stephan Schreiner, Guillaume Bichot, Ali Begen, Cise Midoglu, Andreas Tai, Daniel Silhavy
- Introductions (all)
- Agenda/Prioritization (Daniel)
- Status and numbers
- The latest features and additions
- Related projects & activities
- HbbTV dependency on preload feature
- NPM warning to be triggered to make ppl migrate to the latest version
- ARI track might be a future topic
- Shaka player might be better on SmartTV devices. If we improve here people might be encouraged to use dash.js
- Idea: Ask Dan to give a presentation on where CBS is using dash.js and why they might be using Shaka
- Recent changes to the low latency catchup logic
- Support for ProducerReferenceTime
- Latency calculation in respect to wall clock time should be calculated each time (due to possible different time / live sources)
- Discussion on how to deal with seeks
- See https://github.com/Dash-Industry-Forum/dash.js/pull/3831
- Check for other devices than Desktop browser if constant catchup causes problems
- How to handle manual seek backs behind dvr window
- How should catchup handle after a seek or unpause
- Decided to use Option 3 (see slides) for seek and unpause behaviour
- See https://dsilhavy.github.io/dashjs-jekyll-documentation/
- Add
- Headless Chrome, Multi Client
- Network emulation
- Migration from a previous version
- Make sample page more prominent
- Highlight
- Sample Page
- Add hashtag to select specific tabs on the sample page
- https://github.com/Dash-Industry-Forum/dash.js/issues/3961
- Same content usually coming in different languages, accessibility, channels
- Difficult to match user preferences to what is available in the manifest
- Some recommendations in DASH-IF IOP, not implemented in dash.js today
- Background
- ATSC reference implementation
- Test vectors are available
- Different language codes are used three letter codes vs. two letter codes
- Any benchmarks to compare performance of different players against each other
- Changes to the ABR and throughput implementation
- See: https://github.com/Dash-Industry-Forum/dash.js/pull/3776
- Validate whether the attribute values like duration, timescale and the number of segments tally with the actual total duration given
- In case of multiple periods, we can check whether the periods are divided properly
- Start times and Durations match between Periods
- Period duration matches with the SegmentList duration attribute and the number of Segments involved in that Period
- Server Side ABR logic
- Synergy to CMSD?
- Can we establish a semi-open community testbed for benchmarking various players on performance wrt:
- Asset and encoding (bitrate ladder, codec, …)
- CDN
- Browser (e.g., Firefox vs. Chrome)
- Transport (TCP vs. QUIC, also different congestion control flavours for TCP)
- Network bandwidth traces:
- https://dl.acm.org/doi/10.1145/2483977.2483991
- https://users.ugent.be/~jvdrhoof/dataset-4g/
- https://www.ucc.ie/en/misl/research/datasets/ivid_4g_lte_dataset/
- https://zenodo.org/record/1300512#.YrFdOC8RpbU
- https://www.kaggle.com/datasets/dhruvildave/ookla-internet-speed-dataset/version/2
- https://zenodo.org/record/3459164#.YrFdGS8RpbU
- https://www.kaggle.com/datasets/aeryss/lte-dataset
Notes on funding: might be possible to get an externally funded project to build and maintain such a testbed
- https://www.eurekanetwork.org/
- https://www.forskningsradet.no/en/call-for-proposals/2022/intpart-international-partnerships/ (next round)
- Which tools are you using for development
- https://bitmovin.com/mp4inspector/
- https://github.com/sannies/isoviewer
- https://github.com/bitmovin/vvDecPlayer
- https://github.com/edgeware/mp4ff - mp4parsing/generation and tools in Go
- https://validator.unified-streaming.com/
- ARI track
- Parse track information and dispatch them via event
- PRFT box parsing
- Content Steering
- Server needed, but could easily be added
- Support for adaptation-set-switching
- MSE in webworkers
- Improve developer documentation
- New reference UI
- Improved XML parsing
- Preload support
- Use metrics to compare dash.js success other than npm downloads
- Surveys (consider bias)
- Consider the usage of dash.js in the industry
- How many dash.js players have been embedded
- dash.js challenge
- Yearly challenge co-located with a scientific conference to attract more developers and researchers
- Examples: https://2020.acmmmsys.org/lll_challenge.php
- Funding for the awards can be discussed during the DASH-IF meeting
- Workshop / Webinar
- Combine with challenges
- No dedicated workshop, maybe special session
- Writing a paper to introduce how the player works
- Introduction to ppl. not much aware of DASH/dash.js
- Level of detail that also attracts people familiar with the topic
- Introduction videos
- Adding company logos to the Github page?
- Put ics file for monthly meeting on Wiki
- Send a message via Google Groups
- https://groups.google.com/g/dashjs
- Planning of the next face to face meeting
- Propose to have it in Berlin co-located with MWS 23