Multi-period DASH playback fails at period junctions

[wilaw]

[Filed on behalf of bruce Roberts at Ericsson]

• [x] The MPD passes the DASH-IF Conformance Tool on https://conformance.dashif.org/
• [x] The stream has correct Access-Control-Allow-Origin headers (CORS)
• [x] There are no network errors such as 404s in the browser console when trying to play the stream
• [x] The issue observed is not mentioned on https://github.com/Dash-Industry-Forum/dash.js/wiki/FAQ
• [x] The issue occurs in the latest reference client on http://reference.dashif.org/dash.js/ and not just on my page
• Link to playable MPD file:
• Dash.js version: 2.9.2
• Browser name/version:
• OS name/version:

Steps to reproduce

1. Play the provided manifest in the 2.9.2 release player

Observed behaviour

One of our customers currently uses the dash.js player in their production solution for HTML5/Chrome. One of the requirements of our current project is to change from single-period to multi-period DASH in order to enable dynamic ad insertion. We have found however that when we test playback of our multi-period streams using the dash.js player, playback stalls the period boundaries with “Error Dash.js :32 Cannot read property ‘type’ of nullnostreamscomposed”. We have tested with several versions of the dash.js player, most recently with the newest version 2.9.2.

Our multi-period streams do not fail at period boundaries when we play them in the Bitmovin HTML5 and Android players, Shaka Player, or Exoplayer.

[oldmtn]

@wilaw The link can't visit now. And couldn't do a further debug of this issue.